According to WMExperts here is the official statement from a Microsoft spokesperson in regards to the SMS 2016 Bug in WM :
“Microsoft is aware of reports that phone messages received after 1/1/2010 may be dated 2016. These reports have not yet resulted in widespread customer inquiries; however, we are working closely with our manufacturing and mobile operator partners to investigate the cause and correct the issue as appropriate.”
Here is a NEW Quick Fix for the issue by AuriGroup.com
It looks like the bug is not limited to just WindowsMobile. There are news about ATM card Service being affected by this bug in Australia. Read about the Eftpos glitch in Australia
Why is this happening ? There are many theories floating around. I came across a theory which pointed out that all this started on 01/01/2010 >> 010110 >> which is Binary for 16 ( Hex ). Personally I blame all this on Skynet.
What is your theory ? Share it with us via the comments



























{ 5 comments… read them below or add one }
Doesn't work. Says I need a newer version of .NET framework…
try updating your .Net to the latest version
Follow this guide if you run in to any issue with updating it :
http://www.saijogeorge.com/2008/11/24/delete-ol…
doesnt work used it on my touch pro 2 .tied it today did nothing still 2016 messages.
Try this : http://www.1800pocketpc.com/2010/01/02/sms-date…
My guess is that the decimal number 10 is the same as the hexadecimal number 16 (0×10 = 16 decimal). Still it doesn't make sense why the programmers wouldn't use base 10…simple negligence it seems…if this theory is correct.