Time zone updates for Brazil are available
Published Jul 16 2019 02:30 PM 37.8K Views
Microsoft

The July 2019 update provides below changes for Brazil Daylight Savings Time (DST).

Brazil has decided to no longer follow DST. DST won’t start on the first Sunday of November 2019 as previously scheduled.
More details about latest DST changes for Brazil 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.

39 Comments
Copper Contributor
Hi, Found KB (https://www.catalog.update.microsoft.com/search.aspx?q=kb4507704) for update in some versions of Windows, except Windows 10. Which exactly KB for update in Win10? Note: Enterprise enviroment.
Microsoft

@kbruno89 , the DST updates for Win10 are available as part of the cumulative update which was released on 7/16 for all versions of Win10 except 1809. For Win 10 version 1809, the update was released on 7/22. Thanks!

Copper Contributor

Hi, i´m having trouble in install cumulative update 7/16 Windows 10 1607 by WSUS in my company.

 

I´m checking this trouble, but there is some specific KB for updates daylight in Brazil ?

 

Thanks.

 

 

 

 

 

Copper Contributor

Hi guys and @Nakul_Bhagat !!

 

I'm doing some tests here, looking for possible issues due to the DST change this year and I noticed the following behavior on Windows 10 machines.

After install the latest updates, when I go to "Windows Settings >> Turn daylight Saving Time on or off", the option "adjust for dayllight saving time automatically" is disabled and greyed out....So given this info, I suppose that it was everything fine.

 

However I see 1 hour time difference when using calendar in some programs...then I used the TZEdit tool to check and using this program, the DST is still option is still checked...no matter if using the regular or the dynamic option...follow some screenshots showing what I'm talking about:

 

I thought that by updating the OS, these settings I can see still marked using TZEdit would also be unchecked...Because when I uncheck them using TZEdit tool, the 1 hour time difference is solved on calendar from other programs installed on the machine...

- regular setting is marked when using TZEdit tool:

BrazilianDST-OS-TZEDIT-01.png

- dynamic setting is also marked when using TZEdit tool:

BrazilianDST-OS-TZEDIT-02.png

anybody else noticed similar behavior/problem?

 

 

Microsoft

@Yuri_Costa , we don't release an update that includes only DST changes for Win10.

Microsoft

@wdias-hcl, I don't know what and how the third-party tool (TZEdit) is reading datetime settings. However, can you confirm if you are able to see the proper value of DST offset for Brazil under datetime settings? Or are you suggesting it is off by 1 hour? If so, it is off by +1 hr. or -1 hr. ?

Copper Contributor

 @Win_DST,

I have same problem as our friend @wdias-hcl. I identified the problem with the script below:

Function DSTInformation
{
	Try
    {	
		$ComputerName="$env:COMPUTERNAME"
		$TimeZone = Get-WmiObject -Class Win32_TimeZone -ComputerName $ComputerName

		  write-host("Caption = " + $TimeZone.Caption                        )
		  write-host("Deion = " + $TimeZone.Deion                               )
		  write-host("SettingID = " + $TimeZone.SettingID                       )
		  write-host("Bias = " + $TimeZone.Bias                                 )
		  write-host("DaylightBias = " + $TimeZone.DaylightBias                 )
		  write-host("DaylightDay = " + $TimeZone.DaylightDay                   )
		  write-host("DaylightDayOfWeek = " + $TimeZone.DaylightDayOfWeek       )
		  write-host("DaylightHour = " + $TimeZone.DaylightHour                 )
		  write-host("DaylightMillisecond = " + $TimeZone.DaylightMillisecond   )
		  write-host("DaylightMinute = " + $TimeZone.DaylightMinute            )
		  write-host("DaylightMonth = " + $TimeZone.DaylightMonth               )
		  write-host("DaylightName = " + $TimeZone.DaylightName                 )
		  write-host("DaylightSecond = " + $TimeZone.DaylightSecond             )
		  write-host("DaylightYear = " + $TimeZone.DaylightYear                 )
		  write-host("StandardBias = " + $TimeZone.StandardBias                 )
		  write-host("StandardDay = " + $TimeZone.StandardDay                   )
		  write-host("StandardDayOfWeek = " + $TimeZone.StandardDayOfWeek       )
		  write-host("StandardHour = " + $TimeZone.StandardHour                 )
		  write-host("StandardMillisecond = " + $TimeZone.StandardMillisecond   )
		  write-host("StandardMinute = " + $TimeZone.StandardMinute             )
		  write-host("StandardMonth = " + $TimeZone.StandardMonth               )
		  write-host("StandardName = " + $TimeZone.StandardName                 )
		  write-host("StandardSecond = " + $TimeZone.StandardSecond             )
		  write-host("StandardYear = " + $TimeZone.StandardYear                 )
	}
   Catch
    {
     Write-Warning "$Computer threw an exception"
     $Error[0].Exception.Message
    }
	
}

DSTInformation

clipboard_image_0.png

As there is no daylight saving time in Brazil this year, I believe that DaylightBias, DaylightDay, DaylightDayOfWeek and DaylightMonth should be 0.

Copper Contributor
Hi @Nakul_Bhagat and sorry for the delay to respond...
I have created a script here using the code provided by @wellersonnascimento and I can see the same results...I also believe that the values for DaylightBias, DaylightDay, DaylightDayOfWeek and DaylightMonth should be 0.
 
As a test, I used the TZEdit tool and unchecked the "Automatically set Daylight Saving Time" option which is still checked when using the tool....
ScriptCHeck.jpg
Then running the script again, I noticed that the values for that variables were changed to 0...
Script-AfterUncheckingDST.jpg
Copper Contributor

Hello, @Nakul_Bhagat.

Same issues here. Like @wdias-hcl and @wellersonnascimento, the registry on Windows 10 computers has not changed after installing the latest cumulative updates.

After patching a Windows Server 2008 R2 SP1 with the KB 4507704 I can see the registry changes, unlike Windows 10.

Is that correct? Is there another way to validate the DST change?

 

 

DST2019_W10.JPGDST2019_WS2008R2.JPGusing

Microsoft

@tzacchello , what version of Windows 10 are you using? If you have Win 10 version 1507, then you will need to install the security updates from August 2019. For all other Win 10 versions, preview update from July 2019, should install the DST changes. 

 

@wdias-hcl@wellersonnascimento, the Bias looks correct since the DST for Brazil ended this year in February. However, can you confirm if you are able to see the message as seen in the screenshot after you installed the July preview or August security updates?

 

BrazilDST.png

 

 

 

 

 

 

 

 

 

 
 
Copper Contributor

Hello, @Nakul_Bhagat 

I tried W10 versions 1803, 1809 and 1903. All of them with the latest cumulative updates installed and none had the DST changed. The clock still shows the DST starting date.

 

Copper Contributor

Hi @Nakul_Bhagat 

checking this setting from your last screenshot, I see the same as you...

    (UTC-03:00) Brasilia
    There are no upcoming Daylight Saving Time Changes

 

However when doing tests in programs which uses calendar, we still see 1 hour time difference when using calendar in some programs during the period on which DST was supposed to be active this year.

 

Then once more I opened the TZEdit tool, to check and again using the tool we still see the DST enabled.

 

Technically I don't know from where in the OS settings, both the calendar programs and TZEdit tool are taking this info...

But since there are 2 different programs bringing the same DST information (that DST will start) and which is different from what the OS is showing, I believe that this is stored in some common place in the OS.

 

And as I've already informed before, If I use the TZEdit tool to inform that DST is not observed and save the change, the problem is fixed.

 

I know that this is not a Microsoft tool, however I think that yous guys can download and use it also, in order to confirm this behavior and to get more details about what could be happening.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Copper Contributor

Hi @Nakul_Bhagat 


I can see same behavior. After install the latest updates, if I use one program to create one meeting I can see 1 hour off starting January/07 until February/14.

 

1.jpg2.jpg

 

 

- I can confirm using Tzedit tool that 2019 still observe the DST. If I edit manually and disable the DST to 2019 and restart the OS, the issue is fixed.

3.jpg4.jpg5.jpg

 
 
 

 

 

 

 

 

 

 
 
 
Copper Contributor

Hi @Win_DST 

 

I have to apply pacth on Windows Server 2016, this also came out in the August 2019 cumulative update?

Microsoft

@Papalardo, yes that came out in July's cumulative update. I have added the link above in the blog to our DST KB article.

Copper Contributor

Some are saying you need to update Microsoft Exchange in addition of applying the KB on Windows. Is that true or just the KB on Windows should take effect and solve the problem?

Microsoft

@zavalik , depending on the version of your Exchange Server, please take a look at the relevant cumulative update KB articles for Exchange Server. For example, the September KB article for Exchange Server 2016, mentions that these cumulative updates will include DST updates as well.

Copper Contributor

Hi I'm a trouble with DST in Brazil timezone. I update all suggested versions include the last 1809 to windows 10, but the problem remain. I checked doing download the tzedit tools where I saw that the DST is checked causing a less one hour from UTC. 

clipboard_image_0.png

Is there a way to update it from windows? I ask it because a lot of customers are presenting the same problem. 

 

Tks

Edson

Copper Contributor

The only way to solve this (that i found) is:

 

tzutil /s "E. South America Standard Time_dstoff"

Put this in a batch file and execute on all workstations with DST issue.

Copper Contributor

Thank you @brunok89! Almost solve. When I execute the command works well, but when I restart windows the DST flag come back to checked. 

 

tks

Edson 

Copper Contributor

Here, the setting has remained.  @saviski 

 

Do you have GPO?

Can be GPO overwriting?

Copper Contributor

@brunok89 I think I have GPO privilegy! I execute the "tzutil" command with administrator profile. 

Copper Contributor

Hello everybody,

For those who have issues regarding out DST changes in Brazil, I've a workaround until you/we all manage to get the right updates in our Windows 10 machines.

First, lets talk about checking our DST settings:

 

w32tm /tz

 

Running W32Time with the parameter /tz give us an outpout showing the Standard Name for the Time Zone settings current in use, as well as the Month, Day and Day of the Week for the Standard time settings. It also shows the Daylight Name and its Month, Day and Day of the Week.

 

For us, brazilian users, our machines should show (M:1 D:1 DoW:2) for the Brazilian DST as in the image below:

 

clipboard_image_1.png

 

*The PowerShell script from @wellersonnascimento provide us more details for this settings if you run it.

 

In a machine without the proper updates regarding our DST settings, the line about the Brazilian DST will show values like (M:11 D:1 DoW:6).

Now, about the workaround:

In the Windows registry, look for the entry [ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\E. South America Standard Time\Dynamic DST ].

 

There we should see something like this:

clipboard_image_2.png

 

And for one key up in the tree:

clipboard_image_0.png

 

Both images were taken from a computer running Windows 10 with the proper DST settings. Any software that depends on the W10 DST settings and its registry entries should be fine with its time calculations, like Outlook for instance. *Check this link for a more detailed view of how Outlook handles it:
https://support.microsoft.com/en-us/help/2642044/how-time-zone-normalization-works-in-microsoft-outl...


Exporting the key E. South America Standard Time and importing it in a computer with the wrong settings is halfway there. After importing the key we should run w32tm /resync to "resync" the Time Zone settings, as the command suggests.

 

This workaround will work well until the affected machine receives any Windows Update containing the old DST settings. What did happen in some 1803 builds in my company... and I had to reapply the workaround until we properly updated every single machine.

 

* In the Outlook link that I gave you, there is no mention about how it reacts regarding the DST settings on our Exchange servers.

 

If anyone needs it, here goes a .reg file with all key/values we need:

 

Spoiler

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\E. South America Standard Time]
"Display"="(UTC-03:00) Brasília"
"Dlt"="Horário brasileiro de verão"
"MUI_Display"="@tzres.dll,-40"
"MUI_Dlt"="@tzres.dll,-41"
"MUI_Std"="@tzres.dll,-42"
"Std"="Hora oficial do Brasil"
"TZI"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,00,00,03,00,00,00,00,\
00,00,00,00,00,00,00,01,00,02,00,01,00,00,00,00,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\E. South America Standard Time\Dynamic DST]
"2004"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,02,00,17,00,\
3b,00,3b,00,e7,03,00,00,0b,00,02,00,01,00,00,00,00,00,00,00,00,00
"2005"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,00,00,03,00,00,00,00,00,00,00,00,00
"2006"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0b,00,00,00,01,00,00,00,00,00,00,00,00,00
"2007"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,05,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,00,00,02,00,00,00,00,00,00,00,00,00
"2008"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,00,00,03,00,00,00,00,00,00,00,00,00
"2009"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,02,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2010"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2011"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2012"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,04,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2013"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2014"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2015"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2016"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,03,00,17,00,3b,00,3b,00,e7,03
"2017"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0a,00,06,00,02,00,17,00,3b,00,3b,00,e7,03
"2018"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,06,00,03,00,17,00,\
3b,00,3b,00,e7,03,00,00,0b,00,06,00,01,00,17,00,3b,00,3b,00,e7,03
"2019"=hex:b4,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,02,00,00,00,03,00,00,00,\
00,00,00,00,00,00,00,00,01,00,02,00,01,00,00,00,00,00,00,00,00,00
"2020"=hex:b4,00,00,00,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
"FirstEntry"=dword:000007d4
"LastEntry"=dword:000007e4

 

 

I hope to be of help!

 

Best Regards,
Daniel Lima

Copper Contributor

Hi Daniel, thank you so much for the workaround. Do you know there is a new patch from Microsoft to resolve this for both Windows 7 and Windows 10 ? 

Copper Contributor

I didn't hear anything about it and I'm thinking why MS does not inform us here??

 

@Robby_Chedie 

And do you have the KB number from this new fix?

Copper Contributor

Hi sorry I do not have the KB for the new fix but we need an new fix from Microsoft urgently.

This issue is causing chaos for our Brazil users especially when sending out Outlook meeting invites.

 

Robby

Copper Contributor
hi
Copper Contributor
привет всем
Copper Contributor

@Robby_Chedie, for Windows 7 and so on, except by W10, we have the KB4507704 as stated in the first link from @Nakul_Bhagat original post. For Windows 10 we have some cumulative updates from July that should solve the issue. Since I couldn't find a better way to identify if those updates where installed or not in my users PCs, I cannot help you with that...

@wdias-hcl, I'm not sure about what you didn't hear... my workaround perharps? If so, I didn't heard about it before, I just made it happen by trial and error after reading about how Outlook calculates the time for its calendar events.

Copper Contributor

@DanielLima 

I think I was not clear, but I was referring to this question from Robby:

    "...Do you know there is a new patch from Microsoft to resolve this for both Windows 7 and Windows 10 ? "

 

I think that Microsoft didn't provide a new fix so far.

Copper Contributor

@wdias-hcl 

I get it. I have this feeling too... but lets give them the benefit of the doubt.


When, and if, I confirm that all cumulative updates where installed on some of my machines, I'll put some effort to identify if any issues would happen with DST after it.

So far, the machines that I applied my workaround, most of them on 1803, had issues with DST after new updates got installed. Basically the updates reverted the changes I did on those registry entries. For my surprise, some of those machines got to 1903 and yet, had the changes I made reverted.

 

Copper Contributor

Thanks Daniel ! as said with the patches Microsoft provided until now we have issues with both Windows 7 and Windows 10 workstations.

Today we will try to test your Windows 10 workaround.

Would this work for Windows 7 as well ?

Also interesting to read that new Windows updates, reverts back your workaround changes

Copper Contributor

@Robby_Chedie 

 

I couldn't test on W7 machines, but I think it should work. DST registry entries should look the same on both versions.

Take your time to compare W7 entries with the images I provided on my workaround.

Copper Contributor

Thanks will do Daniel.

 

Also an update I want to provide to you and everyone else;

 

We reached out to Microsoft Support directly and this was their response; seems Microsoft will not provide a new patch until or after 1st January 2020.

 

As explained on the phone, as soon as it is the year of the time zone definition change, your meetings will display at the correct time in Outlook.
As a workaround, you can use Outlook on the web (OWA) to view the Outlook calendar items.
Thank you for choosing Microsoft.
 
Copper Contributor

@Robby_Chedie 

Did you saw any changes in your machine since your last message? Some cases here have been solved from the past 2 (two) weeks, like Outlook for Android adding 1h to any event scheduled or accepted. Suddenly it just began to work properly.

Copper Contributor

Will check Daniel, but indeed I have not heard any new complaints from our Brazil business, will let you know shortly.

Copper Contributor

@DanielLima 

for issues related when using mobile devices, you need to remember that the mobile OS (Android or iOS) also need to be updated with the last DST definition...otherwise the user will continue see 1h time difference causing a big confusion..

 

In my cellphone for example, 1 day before the day when the DST change would occurs, I receive an update via OTA (Over-The-Air) informing that my DST settings were updated on the device and I had to restart it to have effect.

 

But I'm not sure how this DST settings are released....I don't know whether this update was sent by the cellphone manufacturer or the Cellphone company?

Anyway, this is something to have in mind also.

 

Brass Contributor

Hi there,

sorry for the very late reply, but I'm a Windows Embedded POSReady customer and I didn't receive the update through Windows Update when it was released. 

I noticed that on this page Link in the "July 2019 update" it says "this update was revised on August 13, 2019, to apply to Windows Embedded POSReady 2009" so it should be publicly available for people to download, however it isn't: letting the OS search for it within Windows Update doesn't show any new update and there's no sign of it in the Microsoft Update Catalog: KB4507704 I mean, it's there for pretty much every OS but not for Windows Embedded POSReady 2009. Is there a way we can get the update on our tills?

 

Thank you in advance,

Frank.

Copper Contributor

Hi @francebb 

 

according to the first post here, Microsoft released the updates containing the new DST rule for the OS's in July/2019...But as you can see in this article below, the OS version you mentioned is not supported anymore since April/2019...So I believe that you must not expect for updates for it....

Check this out:
     End of support for Windows Embedded 2009 (published: January 29, 2019)
     https://support.microsoft.com/en-us/help/4489209/end-of-support-for-windows-embedded-2009

 

Regards.

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