Regression calling _wstat64i32 on symlink directory with KB2467174 installed - by Jason R. Coombs

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 669601 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/20/2011 6:19:11 AM
Access Restriction Public


Originally reported here [], it appears there is a regression in msvcr90 when calling wstat on symbolic links. Before SP1 and before KB2467174, calling wstat on a symbolic link directory would return the stat result for the target. After, it results with an error (the code for "does not exist").

I've tested this only with Visual Studio 2008, because this is a bug with the VS9 CLR.

It's possible that the new behavior is correct. If so, how does one stat a symlink directory in the patched code?
Sign in to post a comment.
Posted by Microsoft on 1/4/2013 at 3:57 PM
Since this is fixed in VS 2012 RTM, we have decided not to service this in previous releases in absence of a strong case. Please try with the Visual Studio 2012 RTM and let us know if the issue persists.

Best Regards,
Visual C++ Team
Posted by Jason R. Coombs on 1/22/2012 at 5:46 AM
I contacted Microsoft Support. The support technician helped me reach the Development team. The support technician relayed to me that the bug has been fixed in the main line of development and will be released with the next release of Visual Studio. This means the fix is not being back-ported to Visual Studio 2008, 2010, or their runtime libraries. In other words, this bug is going to remain around for a very long time.

The workaround is to use the Windows APIs and not wstat for acquiring file and directory information.

They did indicate that they would consider backporting the fix if there was demonstrable business impact. As they currently see it, there is very little business impact, so this issue is very low priority.
Posted by Jason R. Coombs on 11/17/2011 at 6:55 AM
This bug results in a bug in Python [] where updated Windows systems can't import packages (a fundamental operation) if they're present via symbolic links. This unexpected behavior helps contribute to the negative sentiment about Windows and the lack of response reinforces the sentiment in the community that Microsoft doesn't really care about quality.

Although I don't really consider this issue urgent, I will contact support directly to see if I can push this forward.
Posted by MS-Moderator07 [Feedback Moderator] on 5/22/2011 at 8:40 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 MS-Moderator07 on 5/22/2011 at 7:11 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly (