Those of you using Windows Mobile, have you been receiving messages from 2016 after you entered 2010? According to reports, many folks have been receiving messages from 2016, and it seems to be limited to Windows Mobile devices. Details aren’t concrete yet, but it seems that folks from T-Mobile’s network might be unaffected. A .CAB file fix has been reported to solve the problem, but that’s not an official solution, so you’ll want to keep an eye on the situation. There is some speculation that it might be related to “10” being “16” in HEX, but it’s not confirmed if that’s the reason yet. If you’re experiencing something similar, do drop us a comment and let us know if you’ve discovered anything.