Master article for reinstalling the VXIO driver

book

Article ID: 100031075

calendar_today

Updated On:

Description

Error Message

On Windows Server 2003, the vxio driver installation is logged to the <Drive_Letter>\Windows\setupapi.log file. Below is an excerpt showing a successful installation. Note the last line of the driver install which indicates the device install was successful.

[2012/10/22 11:13:28 388.197]
#-199 Executing "C:\Windows\Temp\instpnp.exe" with command line:  i vxio.inf root\vxio
#I060 Set selected driver.
#-019 Searching for hardware ID(s): root\vxio
#I022 Found "Root\VXIO" in c:\docume~1\admini~1\locals~1\temp\vxio.inf; Device: "Veritas Storage Foundation 5.1 for Windows"; Driver: "Veritas Storage Foundation 5.1 for Windows"; Provider: "Veritas Software Corporation"; Mfg: "Veritas Software Corporation"; Section name: "VXIO_INST".
#I023 Actual install section: [VXIO_INST]. Rank: 0x00000000. Driver date: 06/17/2008. Version: 5.1.0.388.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [VXIO_INST] in "c:\docume~1\admini~1\locals~1\temp\vxio.inf".
#I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\VXIO\0000".
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem2.CAT" were found that validated file "c:\docume~1\admini~1\locals~1\temp\vxio.inf" (key "vxio.inf"). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [VXIO_INST.Interfaces] from "c:\docume~1\admini~1\locals~1\temp\vxio.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\VXIO\0000".
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem2.CAT" were found that validated file "c:\docume~1\admini~1\locals~1\temp\vxio.inf" (key "vxio.inf"). Error 1168: Element not found.
#I121 Device install of "ROOT\VXIO\0000" finished successfully.


On Windows Server 2008, the vxio driver installation is logged to <Drive_Letter>\Windows\inf\setupapi.dev.log file. Below is an excerpt showing a successful installation. Note the last line of the driver install which indicates the device install was successful.

>>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - root\vxio]
>>>  Section start 2011/12/28 12:00:37.986
      cmd:  i vxio.inf root\vxio
     dvi: Set selected driver complete.
     dvi: {Build Driver List} 12:00:38.001
     dvi:      Searching for hardware ID(s):
     dvi:           root\vxio
     cpy:      Policy is set to make all digital signatures equal.
     dvi:      Processing a single INF: 'c:\users\admini~1.sam\appdata\local\temp\vxio.inf'
     inf:      Opened INF: 'c:\users\admini~1.sam\appdata\local\temp\vxio.inf' ([strings])
     ........
     ........
     ........
     dvi:      Default installer: Enter 12:00:40.341
     dvi:           {Select Best Driver}
     dvi:                Selected driver installs from section [VXIO_INST] in 'c:\users\admini~1.sam\appdata\local\temp\vxio.inf'.
     dvi:                Class GUID of device remains: {4d36e97d-e325-11ce-bfc1-08002be10318}.
     dvi:                Set selected driver complete.
     dvi:                Selected:
     dvi:                     Description - [Veritas Storage Foundation 5.1 for Windows]
     dvi:                     InfFile     - [c:\users\admini~1.sam\appdata\local\temp\vxio.inf]
     dvi:                     Section     - [VXIO_INST]
     dvi:                     Signer      - [Microsoft Windows Hardware Compatibility Publisher]
     dvi:                     Rank        - [0x00ff0000]
     dvi:           {Select Best Driver - exit(0x00000000)}
     dvi:      Default installer: Exit
     dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 12:00:40.357
     dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL.EN_US} 12:00:40.357
     dvi:      No class installer for 'Veritas Storage Foundation 5.1 for Windows'
     dvi:      CoInstaller 1: Enter 12:00:40.357
     dvi:      CoInstaller 1: Exit
     dvi:      Default installer: Enter 12:00:40.373
     dvi:      Default installer: Exit
     dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 12:00:40.373
     dvi: {DIF_DESTROYPRIVATEDATA.EN_US} 12:00:40.373
     dvi:      CoInstaller 1: Enter 12:00:40.373
     dvi:      CoInstaller 1: Exit
     dvi:      Default installer: Enter 12:00:40.373
     dvi:      Default installer: Exit
     dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 12:00:40.388
<<<  Section end 2011/12/28 12:00:40.388
<<<  [Exit status: SUCCESS]

In both examples of successful vxio installations, we see that the last line of the device install reports success. If this is not logged, then the log should be reviewed further to determine the error which resulted in the failure and this should be followed by a reinstall of the vxio driver (steps provided in the 'Solution' section below)

Resolution

Reinstalling VXIO driver:

**All reboots are necessary**

Collect the following files into a folder on the problem computer. 

Note: All files except vxio.inf are platform architecture specific. Verify there are no hotfixes for vxio.sys before proceeding with the file listed below. Use the most recent vxio.sys from the hotfix location if one exists.

Hotfix location:

32-bit
\Program Files\Common Files\Veritas Shared\wxrtprivates

64-bit
\Program Files(x86)\Common Files\Veritas Shared\wxrtprivates

It's best to search the above directories (including subdirectories) for 'vxio.sys' and if more than 1 is found, compare versions to ensure the latest version of vxio.sys is used for the below procedure. If no vxio.sys hotfix files are found, then use the vxio.sys version in the location specified below.


Vxio reinstall files:
Create a temporary folder (i.e. c:\vxio), and copy the files listed below into this location. Make sure to use the list of files for the proper OS architecture and product version as provided.

32-bit SFW 5.x
Vxio.sys --> C:\Windows\System32\drivers
Vxio.inf --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\VM5INF
Vxiolog.dll --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\ENU
Vxio.cat --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\VM5INF  

  • Use vxio.cat from C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} <...> if the above path does not exist
  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf<...> if the above path does not exist

Instpnp.exe --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\VM5INF
Instsat.exe --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\VM5INF


64-bit SFW 5.x
Vxio.sys --> C:\Windows\System32\drivers
Vxio.inf --> C:\Program Files (x86)\VERITAS\Veritas Volume Manager 5.1\VM5INF
Vxiolog.dll --> C:\Program Files (x86)\VERITAS\Veritas Volume Manager 5.1\ENU
Vxio.cat --> C:\Program Files\Veritas\Veritas Volume Manager 5.1\VM5INF

  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf_amd64_neutral_95af27167927c522<...> if the above path does not exist
  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf<...> if the above path does not exist

Instpnp.exe --> C:\Program Files (x86)\VERITAS\Veritas Volume Manager 5.1\VM5INF
Instsat.exe --> C:\Program Files (x86)\VERITAS\Veritas Volume Manager 5.1\VM5INF  


64-bit SFW 6.x
Vxio.sys --> C:\Windows\System32\drivers
Vxio.inf --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF
Vxio_msgs.dll --> C:\Program Files\Veritas\Veritas Volume Manager\ENU
Vxio.cat --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF

  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf_amd64_neutral_95af27167927c522<...> if the above path does not exist
  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf<...> if the above path does not exist

Instpnp.exe --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF
Instsat.exe --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF


64-bit Infoscale 7.x
Vxio.sys --> C:\Windows\System32\drivers
Vxio.inf --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF
Vxio_msgs.dll --> C:\Program Files\Veritas\Veritas Volume Manager\ENU
Vxio.cat --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF

  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf_amd64_neutral_95af27167927c522<...> if the above path does not exist
  • Use vxio.cat from C:\Windows\System32\DriverStore\FileRepository\vxio.inf<...> if the above path does not exist

Instpnp.exe --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF
Instsat.exe --> C:\Program Files\Veritas\Veritas Volume Manager\VM5INF

 
Cleanup and re-install the vxio driver as follows.

Note: All commands need to be run from the temporary folder created above (i.e. c:\vxio). In addition, ensure that the command prompt is run as Administrator.

1. Unload the vxio driver so Windows will allow it to be deleted:

     instsat r .\vxio.inf
     reboot

Successful output for instsat r .\vxio.inf:

Opened .\vxio.inf file succesfully
Opened file queue
Deleting service ...
Uninstalled successfully.


2. Unregister the vxio driver from Windows. The following command may be issued multiple times until Windows complains the vxio driver is not installed.  The two iterations of “instpnp R” are intentional.

     instpnp R root\vxio
     instpnp R root\vxio

Successful output for instpnp R root\vxio:

First run:

    

Second run:

    

Note: In some instances, the above error may not be seen on second run. If message is not seen, try running the 'instpnp R root\vxio' command again just to be sure.
 

3. Cleanup INF file store:

  • Run command: instpnp d vxio.inf
​- Run multiple times in cases where vxio is showing multiple copies under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\VXIO\)
  • Verify that Storage Foundation for Windows is not listed (Device Manager > System Devices > Veritas Storage Foundation for Windows)
- If yes, then right click and select uninstall in Device Manager before reboot
  • Reboot


4. Install vxio driver.

     instsat i .\vxio.inf
     instpnp I vxio.inf root\vxio

     reboot

Successful output for instsat i .\vxio.inf:

     Opened .\vxio.inf file succesfully
     Opened file queue
     Adding Service ...
     Installed successfully.

Successful output for instpnp I vxio.inf root\vxio:

    

    

Check the setupapi.log (Windows 2003) or the setupapi.dev.log (Windows 2008) to confirm successful installation or to investigate errors.

Windows 2003: Setupapi.log = <drive_letter>\Windows\
Windows 2008/2012: Setupapi.dev.log = <drive_letter>\Windows\inf\

5. Once it has been confirmed that the vxio driver has been installed successfully, the temporary directory created (i.e. c:\vxio) can be removed.


Other troubleshooting tips:

- Devcon can be used to verify driver is not installed after removal:

Download and extract devcon from here:
- https://support.microsoft.com/kb/311272

Run the following command:

     devcon driverfiles root\vxio


- Refer to 000100818 if you see the following error during vxio install:

     VERITAS: Instpnp.exe Error
     _tmain()!UpdateDriverForPlugAndPlayDevices FAILURE: The system cannot find the file specified



- Refer to 000095021 if you see the following error during vxio install:

     InstallRootEnumeratedDriver()!UpdateDriverForPlugAndPlayDevices FAILURE: (0xe0000234)
     Error 0xe0000234: Driver is not intended for this platform.

 

Issue/Introduction

There are multiple issues seen with VXIO not being installed correctly, below are some examples:
  • Windows Device Manager shows Vxio as Unknown Device under Other Devices, or with yellow ! under System Drivers.
  • No Volumes arrive from PnP during Diskgroup import (volumes report offline and if a rescan is performed, the volumes will then report 'missing')
  • Basic disks cannot be upgraded to SFW dynamic disks
  • Backups fail
  • Snapshot errors
Issues with the vxio driver install are generally seen following a fresh install or an upgrade of the Storage Foundation for Windows (SFW) or Infoscale products. The solution is to perform a manual reinstall of the vxio driver.

Note: An uninstall/reinstall of the product may not result in a solution to this issue, so it is always recommended to following the manual reinstall steps as outlined in this article.