FIX: SETUP.EXE Cannot Start via a UNC Connection

 Last reviewed: September 18, 1997
Article ID: Q115327
1.00 1.50 1.51 1.52 1.52b | 1.00 2.00 2.10 
WINDOWS                   | WINDOWS NT
kbsetup kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft Visual C++ for Windows, versions 1.0, 1.5, 1.51, 1.52 and 1.52b
  • Microsoft Visual C++ 32-bit Edition, versions 1.0, 2.0, and 2.1

SYMPTOMS

Start SETUP.EXE through a universal naming convention (UNC) connection (for example, type "\\netroot\share\subdir\msvc\SETUP.EXE"). Installation fails and the following message box is displayed: 

   Setup cannot initialize the file list

RESOLUTION

Assign a drive letter to the network share and run the SETUP.EXE file (for example, use "x:\subdir\msvc\SETUP.EXE").

STATUS

Microsoft has confirmed this to be a bug in the products listed at the beginning of this article. This problem was fixed in Visual C++ 2.2, but has not been fixed in the 16-bit version of our compiler. We will post new information here in the Knowledge Base as it becomes available.

Additional reference words: 1.00 1.50 1.51 1.52 2.00 2.10
KBCategory: kbsetup
KBSubCategory: vc10setup vc15setup vc20setup
Keywords : kbsetup
Version : 1.00 1.50 1.51 1.52 1.52b | 1.00
Platform : NT WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.