New Fix for WM 2016 SMS Bug y2k16

ppcfreakk · #1 (**permalink**) 01-09-2010, 04:39 PM

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.”

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 http://www.smh.com.au/business/welco...0105-lqus.html

but in the mean time here is the cab for the y2k16 fix

bkrodgers · #2 (**permalink**) 01-09-2010, 05:39 PM

Read the sticky -- the workaround was found by a developer here a week ago...

Not sure what yours does differently.

**willysp** · #3 (**permalink**) 01-09-2010, 06:41 PM

Quote:

Originally Posted by ppcfreakk

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.”

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 http://www.smh.com.au/business/welco...0105-lqus.html

but in the mean time here is the cab for the y2k16 fix

What's new about either your post or cab?

**p-slim** · #4 (**permalink**) 01-09-2010, 07:08 PM

Quote:

Originally Posted by willysp

What's new about either your post or cab?

there is nothing new about his at all nor did he say there was. Whats new about it is the fact that it comes from microsoft directly and not from a member of ppcgeeks.

**w7excursion** · #5 (**permalink**) 01-09-2010, 08:50 PM

Quote:

Originally Posted by p-slim

there is nothing new about his at all nor did he say there was. Whats new about it is the fact that it comes from microsoft directly and not from a member of ppcgeeks.

It doesnt come from microsoft and is from this site. http://wmpoweruser.com/?p=11880

digiblur · #6 (**permalink**) 01-09-2010, 07:32 PM

Looking at the CAB it is more than just a registry entries. Curious if it actually fixes the issue or is the stupid workaround that puts the time from the phone instead of the time the message was sent on the text.

Anyone else break this one down yet?

**BlackDynamite** · #7 (**permalink**) 01-09-2010, 09:41 PM

"These reports have not yet resulted in widespread customer inquiries..."

Wow, nice lie there Microsoft. maybe the "fix" for this should be a phone number and email address where we can let them know it IS widespread. Either they have their heads in the sand or they are flat out lieing.

**strra** · #8 (**permalink**) 01-09-2010, 09:56 PM

the cab includes a file called "Y2K16 Bug Fixer.exe". i haven't tried this because i'm content with the previous fix (in fact, i like it better than it used to be because i'm in roaming quite often and now i actually get correct timestamps!)

Quote:

Originally Posted by SaltyDawg

"These reports have not yet resulted in widespread customer inquiries..."

Wow, nice lie there Microsoft. maybe the "fix" for this should be a phone number and email address where we can let them know it IS widespread. Either they have their heads in the sand or they are flat out lieing.

i think what it means is that not a whole lot of people have actually contacted microsoft about the issue, not that the issue itself isn't widespread

**BlackDynamite** · #9 (**permalink**) 01-09-2010, 09:59 PM

Quote:

Originally Posted by strra

i think what it means is that not a whole lot of people have actually contacted microsoft about the issue, not that the issue itself isn't widespread

So how do you contact them? We need an email address or something. Nobody has contacted them yet because it's kind of difficult, and we expected them to already be on top of it anyway...

dredd8 · #10 (**permalink**) 01-10-2010, 06:04 PM

Quote:

Originally Posted by strra

the cab includes a file called "Y2K16 Bug Fixer.exe". i haven't tried this because i'm content with the previous fix (in fact, i like it better than it used to be because i'm in roaming quite often and now i actually get correct timestamps!)

i think what it means is that not a whole lot of people have actually contacted microsoft about the issue, not that the issue itself isn't widespread

Just curious strra, the one that worked for you was it the ziggy.cab? I tried the 2016.cab on the top of this post and it didn't work for me.