Microsoft confirms Exchange Year 2022 problem

Re:Microsoft confirms Exchange Year 2022 problem by ocdtrekkie on Sunday January 02, 2022 @02:10PM (#29772388)

I love the solution: They changed their antimalware definition files to December 33rd, 2021, until they have a more substantial patch ready. The instructions are just to basically clear out the existing files and re-download to get rid of that pesky 2022 year.

[ Parent | on HN ]

Re:Microsoft confirms Exchange Year 2022 problem by axjmc on Sunday January 02, 2022 @03:05PM (#29773162)

Perhaps switch to unsigned int until a sane solution is implemented. Should give them a couple thousand years to work with.

[ Parent | on HN ]

Re:Microsoft confirms Exchange Year 2022 problem by Fatnino on Sunday January 02, 2022 @03:07PM (#29773192)

No, it just kicks the can down the road another 22 years.

[ Parent | on HN ]

Re:Microsoft confirms Exchange Year 2022 problem by axjmc on Sunday January 02, 2022 @03:11PM (#29773238)

At first glance thought they were using yyyy format, it's actually only yy. You are correct.

[ Parent | on HN ]

Re:Microsoft confirms Exchange Year 2022 problem by ocdtrekkie on Sunday January 02, 2022 @05:27PM (#29774730)

It's pretty likely they'll change the data type somehow, but I guess the question is how fast they can test how that interacts with everywhere that might encounter that variable. Presumably the hack they implemented here buys them at least a month or two to test a real code change.

[ Parent | on HN ]