January 15, 2007

Daylight Saving Time – Windows Mobile Fix

Daylight Saving TimeAs discussed here, the Daylight Saving Time change for 2007 is going to cause problems for unpatched technologies. Most vendors, including Microsoft, have released patches. One big area that is lacking is Windows Mobile smartphones & PDAs. Microsoft release a registry fix and instructed the carriers to push out a patch. Most of the carriers, in their infinite wisdom, have neglected to do so. If you rely on your Windows smartphone, you need this fix. Microsoft published the registry fix here. This fix requires you to build a CAB file and then install it. To save you the trouble, I have bundled the CAB file for you:

Microsoft Windows Mobile Daylight Saving Time Patch

You can either download the CAB file directly to your cell phone, or download to your PC, copy it via activesync to your phone, and then run it.

Since I never recommend just trusting an executable you find online, you may want to check the contents of this file. If you save it with a .txt extension, you can open it with notepad. There will be some extra characters, but the bulk of the file should match the patch from Microsoft. If you want to create your own CAB file, you need the cabwiz.exe executable with is part of Visual Studio. Save the code below as a .INF file and then run cabwiz.exe against it.

Signature=”$Windows NT$”
CESignature=”$Windows CE$”[DefaultInstall]
AddReg = RegSettings.All

1 = ,”Common Files”, , C:\My_Cabs\DST2007WM5

readme.htm = 1

Files.Common = 0, %CE3%
DefaultDestDir = 0,%InstallDir%

AppName = “Update for 2007 Daylight Saving Time”
InstallDir = %CE3%

NEW = “SOFTWARE\Microsoft\Timezones\60”
ATL = “SOFTWARE\Microsoft\Timezones\50”
EST = “SOFTWARE\Microsoft\Timezones\35”
CTL = “SOFTWARE\Microsoft\Timezones\20”
MNT = “SOFTWARE\Microsoft\Timezones\10”
PAC = “SOFTWARE\Microsoft\Timezones\4”
ALS = “SOFTWARE\Microsoft\Timezones\3”
CHI = “SOFTWARE\Microsoft\Timezones\13”
MXC = “SOFTWARE\Microsoft\Timezones\30”
TJA = “SOFTWARE\Microsoft\Timezones\5”


;GMT-3:30 Newfoundland
HKLM,%NEW%, TZI, 0x00000001,d2,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-4 Atlantic
HKLM,%ATL%, TZI, 0x00000001,f0,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,

;GMT-5 Eastern US
HKLM,%EST%, TZI, 0x00000001,2c,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-6 Central US
HKLM,%CTL%, TZI, 0x00000001,68,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-7 Mountain US
HKLM,%MNT%, TZI, 0x00000001,a4,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-8 Pacific US
HKLM,%PAC%, TZI, 0x00000001,e0,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-9 Alaska
HKLM,%ALS%, TZI, 0x00000001,1c,02,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,

;GMT-7 Chihuahua, La Paz
HKLM,%CHI%, TZI, 0x00000001,a4,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0a,

;GMT-6 Mexico City, Monterrey
HKLM,%MXC%, TZI, 0x00000001,68,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0a,

;GMT-8 Tijuana, Baja California
HKLM,%TJA%, TZI, 0x00000001,e0,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0a,
HKLM,%TJA%, Display, 0x00000000, “GMT-8 Tijuana, Baja California”

I confirmed using Mobile Registry Editor from http://www.breaksoft.com/ that the keys did not exist before the patch, and now exist after the patch, on my Samsung Blackjack. The only way I know to test that the patch works is to change the date/time on your phone to March 11, 2007 01:59:00AM and see what happens. Since I am lazy, I plan to wait until March 11 & just see what happens. If you test this patch before then, please leave a comment and let me know if it works.


UPDATE – 01/29/2007

Thanks to Eric for figuring this out: Once you apply the patch, you must manually change your timezone to something else and click apply. After that, change it back to your correct time zone. This forces the phone to re-read the registry file. I tested this on my Blackjack and it worked perfect. The phone changed the time correctly at 03/11/2007 2:00AM to 3:00AM and gave me a dialog box telling me it had adjusted for DST.

UPDATE – 02/06/2007

David found the following link to a similar fix for Australian time zone changes: http://www.pocketpcthoughts.com/articles.php?action=expand,53751. I have not tested these CABs so use at your own risk.

UPDATE – 03/07/2007

Mike found an updated patch released by Microsoft. Details can be found here:Â http://www.microsoft.com/windowsmobile/daylightsaving/default.msp. I recommend everyone install this patch instead of my unsupported CAB file.

Thanks for stopping by.
If you found this article useful, please leave a tip.


  1. Jeff said,

    February 14, 2007 @ 2:37 pm

    I successfully applied the patch to the following devices:
    Verizon Q
    Cingular 8125
    T-Mobile MDA

    However, I have not been able to get it to work with a Blackjack. I have tried this on two different Blackjack devices and on both devices I receive an error message stating “Installtion was unsuccessful”. Is there some trick to install on the Blackjack?

  2. bill said,

    February 14, 2007 @ 2:43 pm


    It worked fine on my BlackJack. I synched it via ActiveSynch to my storage
    card and then ran it from the file system.


  3. Scott said,

    February 14, 2007 @ 3:22 pm

    Thanks for all the help. Microsoft finally created a CAB. Smartphones and Pocket PCs have different files. They can be found here:


    I installed and tested on a Motorola Q (Verizon) and Cingular 8525.


  4. Mikki said,

    February 16, 2007 @ 2:51 pm

    I tried installing the update on my Blackjack and I got the following error message:

    “The program you have installed may not display properly because it was designed for a previous versions of Windows Mobile software.

    Has anyone received this error message and know how to troubleshoot this?

  5. Vince said,

    February 19, 2007 @ 7:06 am

    Dewey, Try installing it using the activesync loader.

    I am a similar problem but mine is because I need to be able to copy the cab to the handheld and then click on it/run it and have it install automatically without it being connected to a pc. It gives me that error when I click on the cab. When I use the cab on the this site it installs but the cab does not delete itself once installed. I find this to be a problem because I put the cabs in the startup folder on a Hard reboot so they will reload and this will cause the cab to reload every time a soft reboot occurs. I tried to create a cab from Microsofts site but am getting TZI error everytime (see comment above). So, Does anyone know how to create a cab that cab be loaded from the handheld that will self delete?

  6. Vince said,

    February 19, 2007 @ 2:14 pm

    Forget it. I got both of my questions. The TZI error is because the text “0Ă—00000001,” “e0……” were on seperate lines on microsofts site causing an error. And the self deleting cab was because the there was no file being copied in the file.

  7. e805er said,

    February 21, 2007 @ 12:38 pm

    i installed the patch…thank you….

    but only rec’d a message that my timezone changed when i changed it something else and back to eastern…

    no message of “dst” at all….

    did the patch still work?


  8. The Merg said,

    February 27, 2007 @ 3:37 pm

    Does anyone know if this fix would work on an IPAQ 1910 (PocketPC 2002)?


  9. Kev said,

    March 3, 2007 @ 7:32 am

    I just tesed my 1910 with this and it seams to work great. But you do have to change the time zone, save, and then change it back again to your time zone like the update on 1/29/07 tells you to or it does not work.

  10. bill said,

    March 6, 2007 @ 11:37 am

    Palm has released their patches here:


  11. mike conley said,

    March 7, 2007 @ 9:31 am

    “Alert: Microsoft Replaces Defective DST Software Patch

    By James Alan Miller
    March 6, 2007

    Microsoft has issued a patch for the Windows Mobile software patch it issued a few weeks back to address changes in Daylight Saving Time (DST) . That first version, as it turns out, was defective.

    Those who installed the original DST patch discovered their appointments were off by an hour between March 11th and April 1st, when DST would have began if the old rules were still in effect. The new version of Microsoft’s DST software update corrects this problem.

    Beginning this year, DST start three weeks earlier (2:00 a.m. on the second Sunday in March, the 11th for 2007) and ends one week later (2:00 a.m. on the first Sunday in November, the 4th for 2007) than in the past. Previously, it started the first Sunday in April and ended on the last Sunday in October.

    Microsoft latest version of its DST software update promises to enable your handheld or smartphone to alter the time correctly when March 11th rolls around next week. So your Pocket PC, Pocket PC Phone or Windows Smartphone’s appointments will reflect the correct hour you set them to occur.

    Click here for Microsoft’s DST patch and directions.”

    Does anyone know if this is going to be an issue for people who used the patch from this board instead of the one microsoft issued?

  12. bill said,

    March 7, 2007 @ 9:41 am


    Thansk for finding this. I am recommending anyone who used my patch to run the Microsoft update, found HERE!!!

  13. mike conley said,

    March 7, 2007 @ 9:58 am

    bill, do you have any idea what they may have changed? I’m servicing about 15 executives carrying treo 700w’s and there calendars seem to be right with your patch.

  14. Kris said,

    March 7, 2007 @ 4:51 pm

    Do we need to uninstall the “old” patch first or can the new one simply be installed on top of it?


  15. bill said,

    March 7, 2007 @ 4:57 pm

    I installed the new patch without removing the old one, with no adverse effects. I have a Cingular BlackJack. Your mileage may vary.


  16. Mike said,

    March 7, 2007 @ 10:10 pm

    OK – I complained above that this did not work (for my device it seems – a T-Mobile MDA running Win Mobile 5 Rom version WWE – it looks like others are having better results.) I tried the original patch – as stated above this really threw the device/outlook sync for a loop to the point I had to delete calendars and start over.

    So I tried this weeks patch. The good news is that the fix is better, but completely WRONG still. Recurring calendar entries that I enter on the phone appear to be correct (I am Mountain Time BTW) on the phone and in outlook. Entries made in Outlook however appear to be off 1 hour today, and 2 hours next week (earlier). What a mess.

  17. Mike said,

    March 7, 2007 @ 10:15 pm

    Oh, by the way – the entries appear off by 1 or 2 hours as viewed in the Mobile device.

    We have 2 of these devices – one syncs with Win XP and the other with Vista Ultimate. Both are now nothing better than expensive phones. Oh, and don’t even bother calling T-Mobile – they have no clue (though they finally did refer me to the DST link on the MS site.)

  18. alasdair said,

    March 8, 2007 @ 4:54 am

    I’ve tested the easy patch on a patched and unpatched system without removing the original patch and it works there’s a link to a page that gives you all the details of how to and the order in which you update all your desktop apps over on my blog at http://blog.commsconsulting.co.uk/2007/03/08/daylight-saving-time-changes-on-windows-mobile-devices/

    not in the US so it doesn’t really affect me :)


  19. Brook said,

    March 10, 2007 @ 6:45 am

    I’ve run the patch (a few times) on my T-Mobile MDA (which is actually an HTC-Wizard) running Win Mobile 5 Rom version WWE…

    The patch works fine and my appointments are updated… except that when I soft reset the phone all of the appoints change back to the way there before I ran the patch… then if I run the patch again, it fixes it… but only unil I do another soft-reset.

    What the !@#$ ?


  20. Mike said,

    March 10, 2007 @ 11:56 am

    Brook – I noticed that too, only it’s worse than you state – the patch works for a while but then will actually revert itself after a certain amount of time – without a reset. T-Mobile has responded stating that they have escalated the issue, are aware of the problem, and are “early in test” on the fix. Hoping for something sooner rather than later here, as the thing is pretty much useless at this point as a calendar. Maybe their plan is to issue an update that uses Windows Mobile 6, as I have read that they are planning a release on some devices early this year…

  21. Kathy said,

    March 11, 2007 @ 10:46 am

    I have a problem I’m hoping someone can help me resolve. I installed the DST patch to Windows XP Home., SP2. I did not apply the patch to Outlook 2002 which is part of my MS Office pkg. At 2:00 a.m. 3/11 I manually adjusted the time on my PC to the new DST time. I have an IPAQ 5450 with Windows CE 3.0 operating system. There is no patch for this operating system which is older. Therefore I manually changed the time on the pocket pc by one hour to the correct new time. When I put the IPAQ in the cradle and sync with my computer, the time now reverts back to the pre-DST time (one hour behind what the time really is.) I am so frustrated – can anyone help?

  22. cyrus ghahremani said,

    March 11, 2007 @ 6:08 pm


    i managed to update my samsung blackjack’s times, but am having the same calendar problem.

    i even went to edit my forthcoming appointments to correct the hour shift but the time is CORRECT in the edit dialogue, just incorrect on the calendar…

    what am i supposed to do about this? go and give everything an incorrect time?

  23. cyrus ghahremani said,

    March 11, 2007 @ 6:52 pm

    hello again,

    i’d like to note that the changes are fixed come April 1 and there are no issues again except for March 2008. no issues in 2009…

    this is very weird and irritating.

  24. Bram said,

    March 13, 2007 @ 6:42 am

    It Worked! Awesome. I couldn’t get the Microsoft patch to work at all. My mobile device kept giving an error message that the install was unsuccessful. Your patch work exactly as advertised. Thanks.

  25. Don said,

    March 14, 2007 @ 12:55 pm


    I was able to update my Jornada 520, which is also a Windows CE 3.0 device. These are the steps that worked for me:
    1. Download and install the patch for XP SP2.
    2. Download and install the patch for Outlook.
    3. Download the CAB file for Windows Mobile 2003 Pocket PCs.
    4. Copy the WM2003 CAB to your IPAQ and run it. Reset the device. You will probably get the following message: “settimezoneinfo” is not a valid Windows CE application. Just tap the OK button.
    5. Open File Explorer and navigate to Windows/StartUp.
    6. Delete the file SetTimeZoneInfo.
    7. Open the application for setting the system clock. On my Jornada it is called Clock.
    8. Change the Time Zone and hit OK. Note: when changing the Time Zone, use one that has a different GMT than your current one. Example, I live on the East Coast (GMT-5) so when selecting a different Time Zone I would not use Indiana or Bogota.
    9. Open the Clock application and change the Time Zone back to the correct one and tap OK.
    10. If you want to verify if the patch worked, set the date and time on the IPAQ to before 2am March 11, 2007 and wait for the clock to hit 2am. Hopefully, the clock will jump ahead 1 hour, which is what happened with my Jornada.
    11. Finally, appointments in the calendar will be ahead by 1 hour for the period of March 11 to April 1. These appointments can be adjusted manually.

    Hope this helps. Sorry I didn’t respond sooner but I just figured this all out today.

  26. Ron said,

    March 15, 2007 @ 7:36 pm

    I have a Cingular 8525 and installed the Microsoft DST Patch last week. I noticed on Monday AM when I had set my alarm, that there was no audible alarm. I have also found that connecting by USB to my PC, faisl to be recognized for Activesync. Otherwise the phone still rings, other action audible alerts, vibration alerts all work, and I can Activesync to my PC by Bluetooth. So clearly this is something changed on the device. Any thoughts or help? Registry setting? I really don’t want to do a hard reset unless no other option. Appreciate any help.

  27. Oliver said,

    April 4, 2007 @ 3:59 pm

    thanks for the fix!

  28. Rene said,

    May 11, 2007 @ 9:57 am

    Hi Don,

    thanks for posting your solution. I ran across this very same issue today and was happy to see your solution. Great job!

  29. sram said,

    October 3, 2007 @ 12:25 am

    Is there any mechanism to update the time automatically without changing the time zone location to another zone and revert back to updat the DST patch???

  30. Jimbo said,

    October 28, 2007 @ 11:22 pm

    That last update (“UPDATE – 03/07/2007) is for a USA time zone patch, NOT for Western Australia.

  31. Jimbo said,

    October 28, 2007 @ 11:24 pm

    Here’s the correct address for the patch: http://www.microsoft.com/downloads/details.aspx?FamilyID=A3CC98C4-AB57-49B7-BD1D-E24013AB16CF&displaylang=en#QuickInfoContainer

  32. Jimbo said,

    October 28, 2007 @ 11:25 pm

    Here’s the correct address for the patch

  33. Karen said,

    November 13, 2007 @ 8:37 am

    I got the patch and still my alarm clock goes off when it was not programed to. Two times this morning the house was woken up at 4:30 and 5:30 AM!! This is not good.

  34. Dan said,

    April 3, 2008 @ 12:40 pm

    Can you please reinstate your .cab file? The one currently provided by Microsoft does not support Windows CE 3.0 and I’ve read posts that your patch does work with CE 3.0. If I can’t get this, I’m up the creek without a paddle!


  35. bill said,

    April 3, 2008 @ 1:43 pm

    Dan, The cab file is still here:


  36. Daylight saving changes - 3rd party cab now available | Jason Langridge's Mr Mobile Blog said,

    January 9, 2009 @ 4:49 pm

    […] http://www.edgeblog.net/2007/daylight-saving-time-windows-mobile-fix/ Share and Enjoy: […]

  37. New PocketPC 2002 and DST Issue | keyongtech said,

    January 18, 2009 @ 10:28 am

    […] MS came out with their fix for the DST problem, some rolled his own version. You can find it at http://www.edgeblog.net/2007/dayligh…ws-mobile-fix/ Despite the fact that the download is called DST2007WM5.cab, I installed it on my PPC 2002 (a […]

RSS feed for comments on this post · TrackBack URI

Leave a Comment