Applies ToVisual Studio Premium 2010 Visual Studio Professional 2010 Visual Studio Ultimate 2010

Symptoms

Consider the following scenario:

  • You have a folder named "folder1" on drive D. For example, you have the following folder: d:\folder1.

  • You run the mklink command to create a directory symbolic link to the folder. For example, you run the following command to create a directory symbolic link folder on drive C.

    mklink /d c:\linkfolder d:\folder1  
  • You run a Microsoft Visual C++ 2010 application that is developed by Microsoft Visual Studio 2010 Service Pack 1 (SP1).

  • The application calls the _stat or _wstat function, and passes the path of the directory symbolic link "c:\linkfolder" to the path parameter.

In this scenario, the called function does not work, and returns an ERROR_FILE_NOT_FOUND error.Note The returned value of the _stat or _wstat function is -1. The error code is "2," which stands for "ENOENT: No such file or directory."

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Microsoft Visual Studio 2010 SP1 installed.

Restart requirement

You do not have to restart the computer after you install the hotfix if the affected files are not being used at the time of installation. We recommend that you close all Visual Studio 2010-related components before you install the hotfix.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name

File version

File size

Date

Time

Platform

Atl100.dll

10.0.40219.455

138,896

8-Oct-2013

13:34

x86

Atl100.dll

10.0.40219.455

386,192

8-Oct-2013

13:44

IA-64

Atl100.dll

10.0.40219.455

159,376

8-Oct-2013

14:27

x64

Mfc100.dll

10.0.40219.455

5,579,920

8-Oct-2013

14:27

x64

Mfc100.dll

10.0.40219.455

4,400,784

8-Oct-2013

14:59

x86

Mfc100chs.dll

10.0.40219.455

37,016

8-Oct-2013

14:27

x64

Mfc100chs.dll

10.0.40219.455

37,016

8-Oct-2013

14:59

x86

Mfc100cht.dll

10.0.40219.455

37,016

8-Oct-2013

14:27

x64

Mfc100cht.dll

10.0.40219.455

37,016

8-Oct-2013

14:59

x86

Mfc100d.dll

10.0.40219.455

9,144,464

8-Oct-2013

15:47

x64

Mfc100d.dll

10.0.40219.455

7,064,208

8-Oct-2013

16:14

x86

Mfc100deu.dll

10.0.40219.455

65,176

8-Oct-2013

14:27

x64

Mfc100deu.dll

10.0.40219.455

65,176

8-Oct-2013

14:59

x86

Mfc100enu.dll

10.0.40219.455

55,960

8-Oct-2013

14:27

x64

Mfc100enu.dll

10.0.40219.455

55,960

8-Oct-2013

14:59

x86

Mfc100esn.dll

10.0.40219.455

64,664

8-Oct-2013

14:27

x64

Mfc100esn.dll

10.0.40219.455

64,664

8-Oct-2013

14:59

x86

Mfc100fra.dll

10.0.40219.455

65,176

8-Oct-2013

14:27

x64

Mfc100fra.dll

10.0.40219.455

65,176

8-Oct-2013

14:59

x86

Mfc100ita.dll

10.0.40219.455

63,128

8-Oct-2013

14:27

x64

Mfc100ita.dll

10.0.40219.455

63,128

8-Oct-2013

14:59

x86

Mfc100jpn.dll

10.0.40219.455

44,696

8-Oct-2013

14:27

x64

Mfc100jpn.dll

10.0.40219.455

44,696

8-Oct-2013

14:59

x86

Mfc100kor.dll

10.0.40219.455

44,184

8-Oct-2013

14:27

x64

Mfc100kor.dll

10.0.40219.455

44,184

8-Oct-2013

14:59

x86

Mfc100rus.dll

10.0.40219.455

61,592

8-Oct-2013

14:27

x64

Mfc100rus.dll

10.0.40219.455

61,592

8-Oct-2013

14:59

x86

Mfc100u.dll

10.0.40219.455

5,606,032

8-Oct-2013

14:27

x64

Mfc100u.dll

10.0.40219.455

4,425,872

8-Oct-2013

14:59

x86

Mfc100ud.dll

10.0.40219.455

9,220,760

8-Oct-2013

15:47

x64

Mfc100ud.dll

10.0.40219.455

7,132,824

8-Oct-2013

16:14

x86

Mfcm100.dll

10.0.40219.455

93,840

8-Oct-2013

14:27

x64

Mfcm100.dll

10.0.40219.455

82,576

8-Oct-2013

14:59

x86

Mfcm100d.dll

10.0.40219.455

120,472

8-Oct-2013

15:47

x64

Mfcm100d.dll

10.0.40219.455

104,600

8-Oct-2013

16:14

x86

Mfcm100u.dll

10.0.40219.455

93,848

8-Oct-2013

14:27

x64

Mfcm100u.dll

10.0.40219.455

82,584

8-Oct-2013

14:59

x86

Mfcm100ud.dll

10.0.40219.455

122,008

8-Oct-2013

15:47

x64

Mfcm100ud.dll

10.0.40219.455

106,136

8-Oct-2013

16:14

x86

Mfcmifc80u.dll

10.0.40219.455

13,976

9-Oct-2013

12:02

x86

Msvcp100.dll

10.0.40219.455

422,040

8-Oct-2013

13:34

x86

Msvcp100.dll

10.0.40219.455

967,320

8-Oct-2013

13:44

IA-64

Msvcp100.dll

10.0.40219.455

608,920

8-Oct-2013

14:27

x64

Msvcp100d.dll

10.0.40219.455

1,980,056

8-Oct-2013

15:26

IA-64

Msvcp100d.dll

10.0.40219.455

1,015,448

8-Oct-2013

15:53

x64

Msvcp100d.dll

10.0.40219.455

744,600

8-Oct-2013

16:19

x86

Msvcr100_clr0400.dll

10.0.40219.455

774,808

8-Oct-2013

13:34

x86

Msvcr100_clr0400.dll

10.0.40219.455

1,500,824

8-Oct-2013

13:44

IA-64

Msvcr100_clr0400.dll

10.0.40219.455

830,616

8-Oct-2013

14:27

x64

Msvcr100d_clr0400.dll

10.0.40219.455

3,765,912

8-Oct-2013

15:26

IA-64

Msvcr100d_clr0400.dll

10.0.40219.455

1,874,584

8-Oct-2013

15:53

x64

Msvcr100d_clr0400.dll

10.0.40219.455

1,506,456

8-Oct-2013

16:19

x86

Vcomp100.dll

10.0.40219.455

144,536

8-Oct-2013

13:44

IA-64

Vcomp100.dll

10.0.40219.455

59,032

8-Oct-2013

14:27

x64

Vcomp100.dll

10.0.40219.455

52,376

8-Oct-2013

14:59

x86

Vcomp100d.dll

10.0.40219.455

318,616

8-Oct-2013

15:21

IA-64

Vcomp100d.dll

10.0.40219.455

108,696

8-Oct-2013

15:42

x64

Vcomp100d.dll

10.0.40219.455

89,752

8-Oct-2013

16:10

x86

Vcomp100ui.dll

10.0.40219.455

10,392

9-Oct-2013

12:02

x86

Vcomp100ui.dll

10.0.40219.455

10,904

9-Oct-2013

12:02

x86

Vcomp100ui.dll

10.0.40219.455

11,928

9-Oct-2013

12:02

x86

Vcomp100ui.dll

10.0.40219.455

12,440

9-Oct-2013

12:02

x86

Vcredist_ia64.exe

10.0.40219.455

3,045,048

8-Oct-2013

17:34

x86

Vcredist_x64.exe

10.0.40219.455

10,292,912

8-Oct-2013

17:44

x86

Vcredist_x86.exe

10.0.40219.455

9,009,328

8-Oct-2013

17:47

x86

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.