Microsoft has released a remedy for the Exchange Y2K22 problem

In its blog post, Microsoft details the problem’s remedy, which requires administrators to either manually execute the change or use an automated script. The document also includes a comprehensive FAQ, indicating that administrators would need “some time” to apply the remedy. It may take some time for the messages to reach their target recipients’ inboxes, depending on how many emails are delayed in the queue.

At 12 a.m. on January 1st, problems began to appear, prompting one Exchange administrator on Reddit to raise the matter. Administrators began seeing problem messages in the Exchange Server’s Event Log, such as “The FIP-FS Scan Process failed startup,” according to Bleeping Computer. 0x8004005 is the error code. “Unspecified Error” or “Error Code: 0x80004005” are examples of error messages. Error description: “2201010001” cannot be converted to a long.”

During the time it took Microsoft to correct the problem, administrators were compelled to come up with different solutions, but now that Microsoft has provided an official patch, the Y2K22 crisis appears to be gone.

In Other News

While there are numerous SMS backup and transfer applications available on smartphones, the hassle of saving your messages on your Windows is honestly a bit much. We hope that tech giants such as Microsoft come up with a more efficient way to transfer and backup messages across various platforms.