The information in this article applies to:
SYMPTOMSInstalling Visual C++ may cause the Setup program to display the following in a message box: This happens when the Setup program tries to copy files from the Visual C++ CD-ROM to a hard drive, and those files are hidden or read-only. In later versions of Visual C++ you are more likely to receive a dialog box containing one of the messages below. You should only encounter the 'Internal Error' message if the destination file is corrupted. For the 32-bit edition of Visual C++ version 2.0 and later: For the 16-bit version of Visual C++ for Windows, version 1.51 or later: The dialog boxes have three options, Abort, Retry and Ignore.
CAUSEThe Visual C++ Setup program copies the majority of files to its own directory (by default, C:\MSVC). It also copies some of the files to the Windows directory and its subdirectories. Any hidden, read-only, or corrupted files with the same names in these directories may cause the Setup program to fail. These files have been installed by the previous installations of the Visual C++ or by other software packages. The Visual C++ Setup program can return the "Internal Error" message when its attempt to overwrite a corrupted, hidden, read-only or share-locked file fails. RESOLUTION
When the "Internal Error" message occurs, the VC++ Setup program displays a
filename associated with its source directory and target directory in the
VC++ Setup dialog box. In the case of a hidden or read-only file in the
target directory, the Setup program displays the name of the file that
causes the problem. To resolve the problem of a hidden or read-only file,
follow the procedure below:
STATUSMicrosoft has confirmed this to be a bug in the products listed at the beginning of this article. The problem was fixed in Visual C++ for Windows 1.51 and Visual C++ 2.0 32-bit edition. MORE INFORMATION
Some of the files copied to the Windows subdirectory by the VC++ Setup
program are related to OLE (Object Linking and Embedding) 2.0 retail
dynamic-link libraries (DLLs) and symbol files. Any system with OLE 2.0
applications installed may already have some of these DLLs installed by the
applications. For some reason, one or more of these DLLs may have hidden or
read-only attributes, or have been corrupted. The OLE 2.0 files typically
cause an "Internal Error" during the installation of Visual C++.
These files are copied from \MSVC\NODEBUG on the Visual C++ CD-ROM into the
\WINDOWS\SYSTEM directory if the option of installing OLE 2.0 retail DLLs
is selected. The option of installing OLE 2.0 retail DLLs is automatically
selected if a user selects the "Typical Installation" option during setup.
This option can also be enabled by selecting the "Custom Installation" and
having the "MFC OLE" check box selected. Notice that selecting the "MFC
OLE" check box in the "Custom Installation" dialog box will not stop the
Setup program from installing OLE 2.0 retail DLLs. The "OLE SDK" button,
located next to the "MFC OLE" check box, needs to be chosen to enable or
disable this option.In the case of a corrupted file in the \WINDOWS\SYSTEM directory, deleting all the files listed above and then reinstalling Visual C++ should resolve the problem in most cases. If not, please contact Microsoft Product Support Services at (425) 635-7007. It is also possible that some of the files from the previous installation of the VC++ may be corrupted for some reason. The following files are copied to the Windows directory by the VC++ Setup program. Delete them to reinstall Visual C++ if necessary. \WINDOWS\SYSTEM Directory
\WINDOWS Directory
\WINDOWS\MSAPPS\MSQUERY Directory
Additional query words: 1.00 1.50
Keywords : kbsetup vc10setup vc15setup vc20setup |
Last Reviewed: August 5, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |