DateTime and DST - by vkornienko

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 767046 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/11/2012 6:12:11 AM
Access Restriction Public


Guys you have problem with DST in Moscow.
It was UTC+3/UTC+4 before 2011.
It became UTC+4/UTC+4 in 2011 till now.

But DateTime (aftter applying KB2756822 update) thinks that before 2012 it was UTC+4/UTC+5!!! It's absolutely wrong! Please fix it or suggest a workaround.
Sign in to post a comment.
Posted by Microsoft on 11/2/2012 at 4:15 PM

Thanks for bringing up this interesting issue. We are always grateful when customers point towards potential concerns - this helps us ensuring the quality of the .NET Framework and driving the product into the right direction.

Indeed, you have discovered a genuine problem, however it is not related to the .Net Framework. In this case our classes consume time zone information from the Windows OS. This information is updated through patches as you already have discovered. If you need to, patches can be uninstalled through the control panel. But keep in mind this will also affect other time zones. Here are the details of all the information contained in the patch that seems to affect you

If you need more help with this specific issue, please refer it to the appropriate channel through

I thank you for your time and your contribution.

(Software Engineer on the .NET Base Class Libraries team)
Posted by Microsoft on 10/11/2012 at 10:35 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 10/11/2012 at 6:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(