FIX: VB Setup Files Modified or Corrupted, Using \WINDOWS Path (106496)


The information in this article applies to:

  • Microsoft Visual Basic Standard Edition for Windows 3.0
  • Microsoft Visual Basic Professional Edition for Windows 3.0
This article was previously published under Q106496

SYMPTOMS

When you run SETUP.EXE to install Visual Basic version 3.0, you may receive the following error message:
Setup Files Have Been Modified or Corrupted.
This message is misleading and incorrect.

CAUSE

This behavior will occur if your PATH statement contains

\WINDOWS

If you modify the path to read C:\WINDOWS, SETUP.EXE works correctly. You can confirm your current PATH by running the PATH command at the MS-DOS prompt.

This problem occurs in Visual Basic version 3.0 SETUP, but does not occur in SETUP for earlier versions.

RESOLUTION

Here are several ideas to help you solve this problem. If one doesn't work, then move on to the next item in the list:

  1. Modify the PATH statement in your AUTOEXEC.BAT file to be C:\WINDOWS instead of \WINDOWS.
  2. Check for viruses.
  3. Try it on a different computer.
  4. Close all your applications, and temporarily disable the Startup group in Windows. In Program Manager, click the Startup group. Then choose Properties from the File menu, and change the name to Xstartup. Then turn the computer off and on in order to clear memory.
  5. Copy the files to a \VBSETUP directory, for example:

    Disk #1 --> \VBSETUP\DISK1
    Disk #2 --> \VBSETUP\DISK2
    Disk #3 --> \VBSETUP\DISK3

    Then run setup from the DISK1 directory.

    NOTE: This takes quite a bit of space on the hard drive, so it is a last resort.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem has been corrected in Visual Basic version 4.0.
Modification Type:MajorLast Reviewed:10/29/2003
Keywords:kbbug kbfix kbsetup KB106496
©2003 Microsoft Corporation. All rights reserved.