Advertisement
Australia markets closed
  • ALL ORDS

    7,937.50
    -0.40 (-0.01%)
     
  • ASX 200

    7,683.00
    -0.50 (-0.01%)
     
  • AUD/USD

    0.6504
    +0.0004 (+0.06%)
     
  • OIL

    82.89
    +0.08 (+0.10%)
     
  • GOLD

    2,325.30
    -13.10 (-0.56%)
     
  • Bitcoin AUD

    98,674.42
    -3,779.96 (-3.69%)
     
  • CMC Crypto 200

    1,390.09
    -34.01 (-2.39%)
     
  • AUD/EUR

    0.6073
    +0.0003 (+0.04%)
     
  • AUD/NZD

    1.0949
    +0.0007 (+0.06%)
     
  • NZX 50

    11,946.43
    +143.15 (+1.21%)
     
  • NASDAQ

    17,526.80
    +55.33 (+0.32%)
     
  • FTSE

    8,040.38
    -4.43 (-0.06%)
     
  • Dow Jones

    38,460.92
    -42.77 (-0.11%)
     
  • DAX

    18,088.70
    -48.95 (-0.27%)
     
  • Hang Seng

    17,290.05
    +88.78 (+0.52%)
     
  • NIKKEI 225

    37,705.37
    -754.71 (-1.96%)
     
Engadget
Why you can trust us

Engadget has been testing and reviewing consumer tech since 2004. Our stories may include affiliate links; if you buy something through a link, we may earn a commission. Read more about how we evaluate products.

Microsoft fixed a Y2K-style bug that broke Exchange email

Microsoft learned a valuable lesson about the limits of integers.

Thomas Trutschel/Photothek via Getty Images

Microsoft is starting 2022 with a flashback to Y2K bugs. Bleeping Computer reports the company has released a temporary fix for a bug that broke email delivery for on-premises Exchange 2016 and 2019 servers on New Year's Day. As users discovered, Exchange was trying to store version date checks for its antivirus scanning engine in a 32-bit integer variable — a big problem when any date from January 1st, 2022 onward was too large. Any new checks made the malware engine crash and left email stuck in a queue.

The emergency fix uses a PowerShell script to pause two services, replace the older antivirus engine files with newer ones that use a new number sequence, and restart operations. The fix requires manual input and could take a long time to implement for larger companies, but an automatic solution is in development.

This shouldn't affect other Exchange customers. The timing is also 'ideal' as a holiday weekend likely limited the demand for email. Company IT managers probably didn't want to start 2022 patching servers, though, and it's unclear why Microsoft didn't foresee a date issue with software released just a few years ago. Whatever the reasoning, this serves as a clear lesson about anticipating date bugs.