Blocking ads removes funding from us!
Researching and writing articles takes a lot of time. Operating our infrastructure costs money.
All of this is funded with advertising revenue.
We don't like advertising either - that's why we avoid annoying banners and pop-ups.
Please give us a chance and deactivate your adblocker!
Alternatively, you can support us here voluntarily.
Language:  Deutsch English (Beta)

Follow us:

Microsoft PowerShell: Error 'Get-EngineUpdateInformation' is not recognized as the name of a cmdlet

Microsoft PowerShell logo
Image: Microsoft
(Post picture: © 2022 Microsoft)

Admins all over the world are currently restoring Exchange servers (our guide is there here ). Some might encounter an error message from Microsoft PowerShell: "The term 'Get-EngineUpdateInformation' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling [...] ". It's easy to fix - we'll figure out what to do.

Microsoft did not make it easy for operators of self-hosted Exchange servers at the turn of the year. Due to a bug in the mail filtering service, many companies have not received or sent e-mails since the beginning of the year. Microsoft already had it in the past year 2021 numerous security holes already made it to the top of the update charts.

Fix the error "'Get-EngineUpdateInformation' is not recognized as the name of a cmdlet" - this is how it works!

Microsoft PowerShell Get-EngineUpdateInformation Error

Picture: TechnikNews/Screenshot

In our instructions To solve the "Y2K22" bug in Exchange servers, we already refer to the error message. This command is run as part of the troubleshooting process to check the version of the filtering engine. This command can also be useful in other cases - only it doesn't work by default. The following error message is displayed:

Get-EngineUpdateInformation : The term 'Get-EngineUpdateInformation' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

To do this, a corresponding snap-in must be added to the PowerShell beforehand. This works with this simple command, while opening PowerShell as administrator:

Add-PSSnapin Microsoft.Forefront.Filtering.Management.Powershell

Execution should then work again. It is important to note that this command is not executed in the Exchange Management Shell, as it is not recognized there. These commands only work in PowerShell, executed as administrator. Successful execution of the command should produce this similar output:

Engine : Microsoft
LastChecked : 01.02.2022 05:45:11 +01:00
LastUpdated : 01.02.2022 05:40:18 +01:00
EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1227.0
SignatureDateTime : 01.01.2022 12:29:06 +01:00
UpdateVersion : 2112330001
UpdateStatus : UpdateAttemptNoUpdate

Recommendations for you

>> Support us by purchasing from Amazon <

David Wurm

Do that TechnikNews-Ding together with a great team for several years. Works in the background on the server infrastructure and is also responsible for everything editorial. Is fascinated by current technology and likes to blog about everything digital. In his free time, he can often be found developing websites, taking photos or making radio.

David has already written 865 articles and left 348 comments.

Web | Facebook | Twitter | Insta | YouTube
Mail: david.wurm | at | | please NOT for general inquiries, cooperations! This way: Contact
Your name, which will be shown publicly.
We will not publish your email address.
Inline feedback
View all comments
Cookie Consent with Real Cookie Banner