Time zone updates for Norfolk Islands, Australia and Fiji Island are available
Published Oct 15 2019 11:37 AM 9,966 Views
Microsoft

The September 2019 update provides below Daylight Savings Time (DST) changes.

 

  • DST in Norfolk Island, Australia will start at 2:00 am on the first Sunday in October current year, that is October 6th, 2019 and end at 3:00 am on the first Sunday in the April, that is April 5th, 2020. It will continue to follow the same time interval each calendar year thereafter.

 

  • DST in Fiji Island will start at 2:00 am on Sunday November 10, 2019 and end at 3:00 am on Sunday January 12, 2020.


More details about latest DST changes can be found here.

To reflect these changes automatically, Windows 10 customers should ensure they have the latest updates installed. Windows 10 Update history can be found here.

19 Comments
Copper Contributor

Please note that DST in Norfolk Island & Australia will end on Sunday 5th April (not the 3rd as noted in the bullet point). 

Also the legislation is not specific about the hour when the DST will end in Norfolk Island. Currently the setting for Sydney is: at 3am the clocks will reset to 2am. For Lord Howe, the current setting is: at 2am the clocks reset to 1am. Norfolk Council IT have used the 2am reset to 1am in current setup but could change prior to April 5th. 

Microsoft

@Peter_Hughson , thanks for pointing out the typo. We have corrected it. Thanks.

Copper Contributor

This page says that the latest CU for 1809 updates the Fiji DST start date

https://support.microsoft.com/en-us/help/4520062/windows-10-update-kb4520062

 

We have installed it a number of times and this is not the case. DST still starts on the 3rd.  Your urgent advice please.

Copper Contributor

Hi Kitionel,

After installing the update, go to your time in the bottom right hand corner and right click the time, and on the menu, select change date/time option. Then in the screen shown (window#1) what does that show for timezone? If the daylight is switched on it will show the time when it will click over. Usually you have to then select the timezone button, (a new window #2 shows), change the timezone to something else and then back again. Close the window #2 and check what it now says. My fix prior to windows update was to change some parameters in the registry using regedit program. I can tell you what but lets leave that for first time as registry changes can be risky.

I noticed that sometimes I had to reboot the computer twice as the old value is read prior to the change applying. The second reboot will read the new value.

Regards, Peter

Copper Contributor

Peter, after I installed kb4520062 and rebooted I looked at [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Fiji Standard Time\Dynamic DST] and it had not changed.

Copper Contributor

Hi Kitonel,

I've tried the changes I would have done on the registry key you mention. (Manual changes) and I agree that it doesn't work. I had this same issue with our DST. In the end, I created a NEW entry in the registry called 'Norfolk Island DST' which worked fine. Another colleague deleted his 'Norfolk Standard Time' entry and put in a new one with the correct time parameters and it worked. So I think that the issue is that it doesn't work unless you delete the existing record and make a new one. I haven't used the 'Dynamic DST' part so I am not sure how that will affect you as you have listings for each year there. I created a 2019 record in my registry but it didn't make any difference from 3/Nov.

Suggestion from me is:

Export the registry key from 'Fiji Standard Time', then see if you can edit it.

Change the line for the 'Display' to: (UTC+12:00) Fiji Standard DST

Change the TZI line so that instead of the '0b 00 00 00 01' you have '0b 00 00 00 02'  - i.e. 2nd Sunday in November(0b=Nov) rather than 1st Sunday

Change the registry path [HKEY etc...] from .....Fiji Standard Time...   to ...Fiji Standard DST... [Note there are TWO places to change this]

You may want to add a line for the Dynamic DST folder as well. Copy the 2018 line, change the date to 2019 and the 1st Sunday to the 2nd Sunday as above

Import it back.

This way you'll have a duplicate rather than deleting the current one.

Try to select the new option, or reboot and try. I guess that if it works you can be safe to remove the existing one but I just left ours in there for additional safety. Of course, you could delete the current one and just load the new one without changing any names - just the Sunday parameter - but that is up to you.

There is a free download program tzedit.exe which is useful for editing timezones too.

Let me know how you go.

I am just trying this first and will let you know.

Peter

.

Copper Contributor

Yes, I can do all of those things but that's what I want to avoid. Anyway we've checked with the latest CUs on 1809 and 1903 and they don't update Fiji DST, and we've done double restarts as well, so tzedit and GPO it is.

Copper Contributor

One more change was that in the Dynamic DST, the 'Last Entry' value has to change from 2018 (7e2) to 2019 (7e3)

If you would like my Regedit upload file for comparison email me on peter.hughson@nirc.gov.nf

I used a GPO registry update to do all our computers, and important to change the 'Action' value to 'Create'. ('update' didn't work if the record does not exist)

Copper Contributor

Here's what our new TZ looks like:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Fiji Standard Time\Dynamic DST]
"2008"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"2009"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,04,00,01,00,00,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,05,00,02,00,00,00,00,00,00,00
"2010"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,03,00,00,00,05,00,03,00,\
  00,00,00,00,00,00,00,00,0a,00,00,00,04,00,02,00,00,00,00,00,00,00
"2011"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,03,00,00,00,01,00,03,00,\
  00,00,00,00,00,00,00,00,0a,00,00,00,04,00,02,00,00,00,00,00,00,00
"2012"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,04,00,03,00,\
  00,00,00,00,00,00,00,00,0a,00,00,00,03,00,02,00,00,00,00,00,00,00
"2013"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,03,00,03,00,\
  00,00,00,00,00,00,00,00,0a,00,00,00,04,00,02,00,00,00,00,00,00,00
"2014"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,03,00,02,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"2015"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,03,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"2016"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,03,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"2017"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,03,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"2018"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,02,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"FirstEntry"=dword:000007d8
"LastEntry"=dword:000007e4
"2020"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,02,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00
"2019"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,01,00,00,00,02,00,03,00,\
  00,00,00,00,00,00,00,00,0b,00,00,00,02,00,02,00,00,00,00,00,00,00

we had to put 2020 in as well as our end date was off.

Copper Contributor

Can you try a shorter method perhaps....in the registry under 'Dynamic DST' add a new Binary record the same as 2018, only that you change the '0b 00 00 00 01' to '0b 00 00 00 02', and also change the 'Last Entry' value from 2018 to 2019. And then try this.

I think that the Last Entry value was stopping the system from reading the 2019 record. I did just try this on the standard Fiji and it worked OK.

 

Copper Contributor

Looks good. Did that work for you?

 

Copper Contributor

yup, rolling out in GPO now.

Copper Contributor

Beautiful. Thanks for your query - I enjoyed trying it out. It took a lot of effort to get our timezone changed as we have never had daylight saving before and Microsoft were unable to help in the short notice period. GPO is the way to go for updates.

Peter

Copper Contributor

I'm not rolling out everything in GPO, only 2019, 2020, and LastEntry - as these are the only three values that need changing.

Copper Contributor

Yes, of course. The least changes the better!

Microsoft

 @kitionel , did you make sure the tzsync.exe ran ? You’ll find it in the task scheduler, under Microsoft/Windows/TimeZone. The job is called SynchronizeTimeZone. Can you try running it and check if the registry settings got updated properly ? @Peter_Hughson , it would be great if you try that too. Thanks.

Copper Contributor

yes that works, however it seems it only runs every 8 days or so, and there is only 1 working day between now and Sunday, thus most of our users won't get the update. Can we trigger this en-masse?

Microsoft

@kitionel , if you have access to the remote machines as an admin then you should be able to work it out using a wmi or a PowerShell script. 

Copper Contributor

you can use: gpupdate /force

also ask users to reboot, and check their time/Timezone info. 

Co-Authors
Version history
Last update:
‎Mar 31 2023 10:40 AM
Updated by: