File Details |
|
| File Size | 0.5 MB |
|---|---|
| License | Freeware |
| Operating System | Windows XP |
| Date Added | July 7, 2008 |
| Total Downloads | 7,261 |
| Publisher | Microsoft Corp. |
| Homepage | Microsoft Time Zone Update |
Publisher's Description
Microsoft Time Zone Update enables your computer to automatically adjust the computer clock on the correct date in 2008 due to revised Daylight Saving Time laws in many countries.
Latest Reviews
Reverb reviewed vDecember 2007 Preview Release on Nov 29, 2007
I read about the Daylight Savings Time changes back Dec 2006 and downloaded then applied the patches MS had available. I rebooted, went into system BIOS and set date for March 12, the day after the DST change was to take place. Nothing.
I did a search and found a way to do it manually:
http://support.microsoft.com
I followed the steps using TZEdit, rebooted and my time was set properly! I reset the date/time in my BIOS, followed the instructions in the knowledgebase article to export the appropriate registry keys and imported that registry file to all my PCs. I emailed it to all my friends, they applied the registry info and all their PCs auto-corrected the time in March 11, 2007 and November 4, 2007. I know many times an MS patch will fix one thing while breaking something else or in the above case, do nothing noticeable which is why for such things the manual method is more effective. If you're a noob call a friend to do this for you.
anomoly reviewed vDecember 2007 Preview Release on Nov 28, 2007
Validation Required?
To check the time?
Just move to HI. f MS
BB88 reviewed vDecember 2007 Preview Release on Nov 28, 2007
beta?!! Yes, we need to complain about M$. They charged so much for everything and couldn't get this simple thing done properly. The new daylight saving time has been effective for such a long time, and this thing is still in beta? My system clock has been wrong when the time changed...and you know this could be critical to many people.
why hello there reviewed vDecember 2007 Preview Release on Nov 28, 2007
Ah, medlir, who doth tryeth so hard to impress. Any sysadmin worthy of the title will weigh the ease of issuing self-created hacks with the security of knowing that if something goes wrong--and it always can--you're much safer if you can say you at least used an official patch, rather than something you whipped up in Notepad.
wookietv reviewed vDecember 2007 Preview Release on Nov 28, 2007
giving this a 1 star because it doesn't work on 2000 is like giving Photoshop for Windows a 1 star because it doesn't work on a mac.
if you bother to read, it says that it's for XP. There's other versions too, are you going to give all of them a 1 because it's not for 2000?! don't falsely manipulate the ratings for something that it's not.
"i gave it a 1 because it didn't cure cancer"...
belthurgp reviewed v2.1 on Nov 28, 2006
I cannot understand why people complain about anything when it comes to Microsoft. They complain if it does a good job, they complain if it screws up trying to please all...
These are people who still use Windows but don't have the balls to switch over to something else and still crib about Microsoft.
Well, if you are already on Mac/Linux/Unix or whatever, you have no business cribbing about MS.
medlir reviewed v2.1 on Nov 27, 2006
For those commenting below, MS doesn't really need to release a patch for 2000 because you can make the changes manually. Any sysadmin worth the title can easily roll out their own tiny registry patch, logon script, etc which is *much* smaller than this glorified packaged exe, as per the info in the KB article.
http://support.microsoft.com/kb/914387
Dreimanis reviewed v2.1 on Nov 27, 2006
good.
JEdwardP reviewed v2.1 on Nov 27, 2006
I too think this is an important enough fix that they should extend it to Win2k, but I'm pleasantly surprised to see this update so soon. Knowing MS, I wouldn't have been stunned if we hadn't seen this until March 1st.
some guy reviewed v2.1 on Nov 27, 2006
This is a total waste to have my computer use a resource to tell time - disabled in services,,,
fix the dam movie maker instead MS !!!!!!!!!!
crash orver encode of 30 megs or more they know this.....
Reverb reviewed vDecember 2007 Preview Release on Nov 29, 2007
I read about the Daylight Savings Time changes back Dec 2006 and downloaded then applied the patches MS had available. I rebooted, went into system BIOS and set date for March 12, the day after the DST change was to take place. Nothing.
I did a search and found a way to do it manually:
http://support.microsoft.com
I followed the steps using TZEdit, rebooted and my time was set properly! I reset the date/time in my BIOS, followed the instructions in the knowledgebase article to export the appropriate registry keys and imported that registry file to all my PCs. I emailed it to all my friends, they applied the registry info and all their PCs auto-corrected the time in March 11, 2007 and November 4, 2007. I know many times an MS patch will fix one thing while breaking something else or in the above case, do nothing noticeable which is why for such things the manual method is more effective. If you're a noob call a friend to do this for you.
anomoly reviewed vDecember 2007 Preview Release on Nov 28, 2007
Validation Required?
To check the time?
Just move to HI. f MS
BB88 reviewed vDecember 2007 Preview Release on Nov 28, 2007
beta?!! Yes, we need to complain about M$. They charged so much for everything and couldn't get this simple thing done properly. The new daylight saving time has been effective for such a long time, and this thing is still in beta? My system clock has been wrong when the time changed...and you know this could be critical to many people.
why hello there reviewed vDecember 2007 Preview Release on Nov 28, 2007
Ah, medlir, who doth tryeth so hard to impress. Any sysadmin worthy of the title will weigh the ease of issuing self-created hacks with the security of knowing that if something goes wrong--and it always can--you're much safer if you can say you at least used an official patch, rather than something you whipped up in Notepad.
wookietv reviewed vDecember 2007 Preview Release on Nov 28, 2007
giving this a 1 star because it doesn't work on 2000 is like giving Photoshop for Windows a 1 star because it doesn't work on a mac.
if you bother to read, it says that it's for XP. There's other versions too, are you going to give all of them a 1 because it's not for 2000?! don't falsely manipulate the ratings for something that it's not.
"i gave it a 1 because it didn't cure cancer"...
belthurgp reviewed v2.1 on Nov 28, 2006
I cannot understand why people complain about anything when it comes to Microsoft. They complain if it does a good job, they complain if it screws up trying to please all...
These are people who still use Windows but don't have the balls to switch over to something else and still crib about Microsoft.
Well, if you are already on Mac/Linux/Unix or whatever, you have no business cribbing about MS.
medlir reviewed v2.1 on Nov 27, 2006
For those commenting below, MS doesn't really need to release a patch for 2000 because you can make the changes manually. Any sysadmin worth the title can easily roll out their own tiny registry patch, logon script, etc which is *much* smaller than this glorified packaged exe, as per the info in the KB article.
http://support.microsoft.com/kb/914387
Dreimanis reviewed v2.1 on Nov 27, 2006
good.
JEdwardP reviewed v2.1 on Nov 27, 2006
I too think this is an important enough fix that they should extend it to Win2k, but I'm pleasantly surprised to see this update so soon. Knowing MS, I wouldn't have been stunned if we hadn't seen this until March 1st.
some guy reviewed v2.1 on Nov 27, 2006
This is a total waste to have my computer use a resource to tell time - disabled in services,,,
fix the dam movie maker instead MS !!!!!!!!!!
crash orver encode of 30 megs or more they know this.....
mjm01010101 reviewed v2.1 on Nov 27, 2006
Wow... I can't believe MS is not doing this for W2K. I think almost certainly they will reverse their stance with this.
constust reviewed v2.1 on Nov 27, 2006
System admins are gonna love this. So many Win2K networks out there and no patch.