Win 7 summer time update. Windows updates for daylight saving time

In accordance with recently adopted laws, on March 27 at 02:00 local time, time zones will change in a number of regions of Russia. Microsoft is working on an urgent update for Windows that will reflect these changes.

Interim solution

An update for Windows is currently in development. It will take certain time required to test, distribute, and install the update. At the same time, the clock change in these regions will take place in a short time. Therefore, we are now offering an interim solution that will allow you to adjust the time on your devices before the update is released.

Official statement from the company this issue you can read it on the website http://microsoft.com/time.

The update will be available on Tuesday, April 12, 2016.

Transbaikal region

Users can temporarily switch to the next time zone on the day of the clock change. After exiting and installing the update, you will need to change your time zone again.

Planned changes to Windows regarding time zones

We plan to include the following changes in the upcoming update. Users in the mentioned regions will be able to change time zones to new ones immediately after installing the update.

New time zones

Astrakhan and Ulyanovsk regions

Altai Republic and Altai Territory

Transbaikal region

Sakhalin region

Changes to existing time zones

These changes concern only the display of time zone names; the time itself has not been changed.

FAQ

How can I schedule meetings and events in Outlook and other programs based on these changes?

After installing the update, you will be able to schedule meetings using the new time zones. However, if you use an interim solution, be careful about your appointment time. If the meeting takes place before the change to the new time, the scheduler uses the old time zone. If the meeting is scheduled for a date after the clock has changed, plan it based on the temporary time zone.

For example, let's take a meeting that will take place in the Sakhalin region.

• The time of the meeting scheduled for March 26 is indicated taking into account the current time zone, “(UTC+10:00) Magadan”, since Magadan time is in effect in Sakhalin.
• The time of the meeting scheduled for April 1 is indicated taking into account the temporarily established time zone, “(UTC+11:00) Chokurdakh (RTZ 10)”.
• The time of a meeting scheduled for April 13, but scheduled before the update was installed, is also indicated taking into account the temporarily set time zone, “(UTC+11:00) Chokurdakh (RTZ 10)”.
• The time of the meeting scheduled for May 1, when the update has long been installed, is indicated taking into account the new time zone, “(UTC+11:00) Sakhalin”.

Recurring meetings that take place both before and after regions switch to new times may need to be rescheduled. After updating your data and switching to a new time zone, you can do this at any time. However, if you use an interim solution, be careful about what time zone was used when scheduling each of these meetings.

If you need to change times for a large number of appointments, use the instructions and tools provided at: KB931667.

Why switch to new time zones?

Time zone data is used in many different situations. Showing the correct time on the command line is just one of them. Many applications require a change to local time, and this applies to past, current, and future operations.

When all time zone changes clocks in spring and fall or changes to new time, quite easy to update existing entry in the registry containing time zone data, adjusting the data and indicating the moment when the new data comes into force. However, if the clocks are changed only to parts time zone, you have to split the existing record into two parts. IN new entry All old data is transferred without changes until the transition to a new time, and after that the new data is used. As a result, entries in the designated regions indicate the correct time both before and after the clock change.

Updated March 28, 2016 1:40 pm

Let us recall that on June 21 of this year it was adopted Federal law Russian Federation No. 248-FZ “On the calculation of time” on the territory of the Russian Federation from October 26, 2014. According to this law, which comes into force October 26, 2014 at 02:00 the country is returning from summer to permanent winter time. In addition, the law provides for the creation of eleven time zones, taking into account the maximum approximation to UTC time zones. Conversion to summer and winter time (seasonal time change) will still not be implemented.

In addition to, in fact, moving the clock hands back 1 hour, the law involves the introduction of a number of new time zones and the removal of one old one, in particular, 3 new time zones will be created, 2 existing time zones will be combined into one new one, and some regions will move to neighboring or new ones zones.

Note. In the Magadan Region and Trans-Baikal Territory, the hands will be moved back two hours. In the Samara and Kemerovo regions, the Udmurt Republic, the Kamchatka Territory and the Chukotka Autonomous Okrug, the clock hands will not be moved.

Microsoft Corporation released a cumulative update for Russian users on September 23, 2014 KV2998527(http://support.microsoft.com/kb/2998527), designed for the correct transition to winter time and taking into account other changes in the order of calculating time on Russian computers with OS Windows family. This update should help the system determine the current time zone and correctly change the time to October 26, 2014.

In the knowledge base article KV2998527 contains links to download updates for all supported Microsoft operating systems: Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows RT, Windows RT 8.1, Windows Server 2003 / 2003 R2, Windows Server 2008 / 2008 R2, Windows Windows Server 2012 / 2008 R2 and embedded ( Embedded) versions of Windows. You can download updates starting September 24th.

As you know, on October 26, 2014, time zones changed, as a result of which Moscow again became GMT+3 (more precisely, UTC+3). In order to solve this Microsoft problems released several fixes for Windows Vista/7/8/8.1 and for Windows 2003/2008/2008R2/2012/2012R2. However:

1. The update was not released for Windows XP due to deadline Windows support XP expired on April 8, 2014. (Update released for Windows XP Embedded and Windows 2003)
2. There are also Windows devices (eg GPS navigators, on which Windows CE is installed), where I also wanted to update the time zone.
3. For Windows 2003 (and perhaps also for Windows XP Embedded), the update was done in a “cunning” way: as you know, on October 26, 2014, the clocks are moved back 1 hour and will no longer be moved forward 1 hour. However, on January 7, 2015 at 00:00 in Windows 2003, the clock will move forward 1 hour again. And then - again 1 hour ago at the end of October 2015. Those. This update actually involves installing one more (or perhaps more than one) Windows 2003 update.
   There is no such problem for Windows Vista/2008 and higher.

Time update for Windows XP/2003

In order to update the time zone in Windows XP and Windows 2003, you do not need to install patches - just change the time zone. For example, put the time zone "(GMT+3:00) Kuwait, Riyadh". If you need to change the time zone of more than 2-3 computers, this can be automated using batch file by running the following command in it:

RunDLL32.exe shell32.dll,Control_RunDLL timedate.cpl,/Z Arab Standard Time

or this command:

tzchange /C "Arab standard time"

You can execute any of the commands (you can do both - they do the same thing: change the time zone to Arab time - Kuwait).

Moreover, this command can be executed in any other operating room. Windows system: in versions of Windows Vista and higher, the first command will simply open a window with setting the time (without changing anything), and the second command will give an error that there is no such program - tzchange.

Time update in Windows Vista / 2008, 7 / 2008 R2, 8 / 2012, 8.1 / 2012 R2

For these operating systems, Microsoft has released updates KB2998527, and the updates for all languages ​​are the same:

For Windows Vista / 2008: Windows6.0-KB2998527-x86.msu and Windows6.0-KB2998527-x64.msu

For Windows 7 / 2008 R2: Windows6.1-KB2998527-x86.msu and Windows6.1-KB2998527-x64.msu

To perform these updates from command line do:

start /MIN /WAIT wusa.exe<ИМЯ-MSU-ФАЙЛА>/quiet /norestart

For example:

start /MIN /WAIT wusa.exe Windows6.1-KB2998527-x86.msu /quiet /norestart

Why is there a wait option? The fact is that if you do not want to determine the bitness of the operating system each time, you can simply run 2 updates on each computer: for 32-bit and for 64-bit Windows. In this case, one of the updates will give an error (in the logs) that they say Windows version does not fit, but the second one will be installed. However, if you run these updates simultaneously, the second one will always fail with an error like “the update is already being installed.” And so - they can be executed in one batch file.

Update time zones in Russia October 25th, 2014

On the night from Saturday to Sunday in Russia, many will set their clocks back one hour, thereby returning Russia to winter time.

Many Windows users have the corresponding update installed automatically. If the time zone displayed does not contain the letters RTZ in its name, the update is likely not installed and the time on your computer may not display correctly on Sunday.

To download and install the update, open the article A September 2014 time zone update for Russia is available (in Russian), in the section More information expand Update information, find yours operating system in the list and click the appropriate link to go to the Download Center to download the update.

The most common systems:

Summary

Russia will change existing time zones on October 26, 2014. To accommodate this change, Microsoft released an update to Windows on September 23, 2014. Users should install this update before October 26, 2014 to avoid having their time zone set incorrectly after that date.

Changes in this update

Changed seven existing time zones

Impact on users

Users in these time zones will have their settings automatically updated on October 26, 2014, except in the following situations:

• In the Republic of Udmurtia and the Samara region, users should manually change the time zone to "3rd time zone" (instead of automatically selecting RTZ 2 after the update).
• In the Kemerovo region, users should manually change the time zone to "6th time zone" (instead of the automatically selected RTZ 5).
• In the Trans-Baikal Territory, users should manually change the time zone to "7th time zone" (instead of automatically selecting RTZ 8).

Three new time zones added

Impact on users

Users in these time zones should manually select a new time zone. Otherwise, time zone settings will be incorrect after October 26, 2014.

Merged two time zones into one new one

Impact on users

For the current Vladivostok time, Windows will update all time zone settings. For Magadan time, Windows will only update the time. The display name will not change. Therefore, users in Vladivostok time do not need to change anything manually. However, users in Magadan Time must manually change their time zone to "9th Time Zone" after October 26, 2014. The old "Magadan" time zone will be removed from the list of time zones with an update released in December 2014.

Exceptions for users located in Magadan time:

• Users in the Magadan region must manually select the "8th time zone".
• Users in the Chukotka Autonomous Okrug and Kamchatka Territory must manually select the "11th time zone".

A time zone for Belarus has been created

Belarus currently uses time zone settings with Kaliningrad. Therefore, this Windows update has created a new time zone for Belarus. The new time zone has the following characteristics:

• Time zone name: Belarusian time
• Display name:(UTC+03:00) Minsk
• The remaining values ​​coincide with the current time zone Kaliningrad time

Impact on users

Users located in Belarus during Kaliningrad time must manually change the time zone to "Belarusian time". Otherwise, the time zone "1st time zone" will be automatically selected.