Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
Microsoft released a fix for the Exchange Y2K22 bug
3 min. read
Published onJanuary 3, 2022
published onJanuary 3, 2022
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
A lot of users woke up on January 1st, 2022, and found that your their work email’s inbox was unusually empty. This massive date processing failure issue exceeded what the Servers are capable of processing under the current Int32 data type.
As a result, the malware checking engine is crashing, and consequently, emails and messages have been stuck in transport queues across Exchange Servers 2016 and 2019.
But you can now breathe a sigh of relief because the Redmond tech giant has released a fix patch for this bug.
Manual and automated solutions provided by Microsoft
Just as the company promised on the first day of 2022, it has finallydelivereda fix for this nasty problem.
In order to get the fix, IT admins can change the execution policy for PowerShell scripts by running Set-ExecutionPolicy -ExecutionPolicy RemoteSigned.
Afterward, the script can bedownloaded with a simple click.and ran on each Exchange mailbox server that downloads antimalware updates.
There is also a manual solution available, which according to Microsoft, is currently automated because it might take some time to make changes, download updated files, and clear transport queues.
The tech giant makes it clear that any manual or automated solution must be performed on every on-premises Exchange 2016 and Exchange 2019 server, and the script can even be run simultaneously on multiple servers.
In all cases, using Microsoft’s emergency script might take some time to run. The script might also take some time to clean up any missed messages in the transport queue.
Public reaction to the fix has been mixed, with some saying it works, while others are claiming it doesn’t do anything.
Other users report that running the script multiple times could help fix the issue, indicating that Microsoft could have done a better job.
Have you managed to sort it out using the solution provided by Microsoft? Let us know in the comments section below.
More about the topics:Microsoft Exchange
Alexandru Poloboc
Tech Journalist
With an overpowering desire to always get to the bottom of things and uncover the truth, Alex spent most of his time working as a news reporter, anchor, as well as TV and radio entertainment show host.
A certified gadget freak, he always feels the need to surround himself with next-generation electronics.
When he is not working, he splits his free time between making music, gaming, playing football, basketball and taking his dogs on adventures.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Alexandru Poloboc
Tech Journalist
With a desire to always get to the bottom of things and uncover the truth, Alex spent most of his time working as a news reporter.
