VMware Communities: Bridging Failing to Install

Up to Discussions in VMware Workstation Archives

This discussion is archived

9,686 Views 6 Replies Last post: Sep 5, 2004 12:41 PM by frolix

MrSecurity411

3 posts since
Nov 3, 2003

Currently Being Moderated

Nov 3, 2003 10:46 AM

Bridging Failing to Install

I have been trying to install VMware Workstation 4.05 build 6030 on a Dell Laptop with Broadcom 10/100/1000 integrated nic and integrated dell mobility wireless card. The host OS is Windows XP Professional SP1 with all of the patches applied, and the guest OS is Windows 2000 Professional... (I don't want to load the Novell Client into my host os... so I opted for a guest OS with it). The install posts the following error to the install log:

VMInstUtil: 11/03/03 13:26:54 Begin Logging

VMInstUtil: 11/03/03 13:26:54 Installing network bridge

VMInstUtil: 11/03/03 13:26:54 Getting Property INSTALLDIR =

VMInstUtil: 11/03/03 13:26:54 Returning InstallPath=C:\Program Files\VMware\VMware WorkstationVMInstUtil: 11/03/03 13:26:54 Loaded library C:\Program Files\VMware\VMware Workstation\vnetlib.dll(10027008)

vnetlib : 11/03/03 13:26:54 I1:Begin Logging 'VNL_InstallNetworkBridge: ' (LogLevel 0x00000003)

vnetlib : 11/03/03 13:26:54 I1:LogTokenPermissions: number of privileges: 23

vnetlib : 11/03/03 13:26:54 I1:VNLWaitForPendingInstallEvents: No install events are pending

vnetlib : 11/03/03 13:26:54 I1:VNLInstallNetworkBridgeW2K: bridge doesn't appear to be already installed

vnetlib : 11/03/03 13:26:55 I1:VNLInstallNetworkBridgeW2K: installing network bridge

vnetlib : 11/03/03 13:26:56 E1:VNLInstallNetworkBridgeW2K: bridge install failed: 0x800f0203 0x000003f0

vnetlib : 11/03/03 13:26:56 I1:VNL_InstallNetworkBridge: bridge install result FALSE needreboot FALSE

vnetlib : 11/03/03 13:26:56 I1:End Logging

VMInstUtil: 11/03/03 13:26:56 Failed to install network bridge

I MUST have bridging working in order for it to authenticate me to Novell correctly in the guest OS. Any suggestions on installing the bridging components?

TIA,

Daryll

2,343 posts since
Jul 10, 2003

Currently Being Moderated

1. Nov 5, 2003 1:17 PM

in response to: MrSecurity411

Re: Bridging Failing to Install

Hey there,

This is the most specific information I have yet seen with regards to the bridged networking not installing when a wireless network card is involved. I will show this to our product managers.

For those of you who also have this complaint, could I see the text of your VM install log as well?

I will let you know what I find out about this error in the install log.

-Daryll

Report Abuse

404 posts since
Oct 24, 2003

Currently Being Moderated

2. Nov 5, 2003 11:46 PM

in response to: MrSecurity411

Re: Bridging Failing to Install

I would have posted this yesterday, but by the time I got around to clicking "Post" the forums were down. Anyway, the file setupapi.log (typically in c:\windows) might have more information about why the failure occured.

The error code 0x800f0203 ("SPAPI_E_NO_DRIVER_SELECTED") is likely from Windows, reporting "There is no driver selected for the device information set or element." The other error value 0x3f0, if also from Windows, can be interpreted as "An attempt was made to reference a token that does not exist", and this either either unrelated or an inproper interpretation of the value.

There are various options to try to resolve the issue. One option is to reinstall the product and see if that resolves the issue. A more light-weight option is to open the network properties for a physical adapter (where things like "Internet Protocol (TCP/IP)" are listed), and click on the "Install..." button. From there, choose service, click on "Have Disk...". You want to pick the netbridge.inf file that's stored in the directory where the product was installed. If the install was successful, then you should now see "VMware Bridge Protocol" listed in the network properties (along with TCP/IP, etc).

If one or neither of the above work, then your INF cache might be corrupted (this cache was a "feature" added in Windows beginning with XP). This cache can cause Windows to look in the wrong INF file to install a driver.

Try the following at your own risk:

One workaround is to cause Windows to regenerate the inf cache. Search in c:\windows\inf\oemXX.inf (where XX represents a two-digit number), and look for the file that corresponds to the vmware bridge. Delete this inf file and delete the corresponding PNF file (e.g., if the bridge was in oem23.inf then delete oem23.inf and oem23.pnf), then delete the INFCACHE.1 file (which is the actual inf cache file -- you can also rename this file rather than delete it).

Reboot for good measure, then try to re-install the bridge (using the "light-weight option" described above). Windows will ideally regenerate the INFCACHE.1 file (expect some disk activity at this point), and install the bridge.

If this doesn't help then an alternate (perhaps simpler and/or more complete?) approach is to uninstall the product, delete the INFCACHE.1 file, reboot, then reinstall.

---

To explain how the inf cache and the error code 0x800f0203 are related, Windows uses the cache to quickly determine what inf file to use to install a driver. If the cache isn't kept up-to-date, then the cache might tell windows to look in the wrong oemXX.inf file. Windows realizes, upon inspecting the file, that the inf file isn't the correct type of driver, and fails. Unfortunately, Windows doesn't seem to have a fallback to handle this situation in a more graceful manner.

Report Abuse

MrSecurity411

3 posts since
Nov 3, 2003

Currently Being Moderated

3. Nov 14, 2003 7:55 AM

in response to: Daryll

Re: Bridging Failing to Install

Here is some additional information from the setupapi.log from the C:\Windows directory (two sections to this - the initial install, and the later reinstall):

\[2003/10/12 13:40:06 3496.1]

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding F312D0F5B2BAAA4C598CDFAA2753A443 M Global\MSI0000

#E361 An unsigned or incorrectly signed file "C:\Program Files\VMware\VMware Workstation\netbridge.inf" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.

\[2003/10/12 13:40:07 3496.28 Driver Install]

#-019 Searching for hardware ID(s): vmware_bridge

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding F312D0F5B2BAAA4C598CDFAA2753A443 M Global\MSI0000

#I022 Found "vmware_bridge" in C:\WINDOWS\inf\oem20.inf; Device: "VMware Bridge Protocol"; Driver: "VMware Bridge Protocol"; Provider: "VMware, Inc."; Mfg: "VMware, Inc."; Section name: "VMnetBridge.Install".

#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.

#I023 Actual install section: \[VMnetBridge.Install]. Rank: 0x0000c000. Effective driver date: 02/10/2002.

#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".

#I063 Selected driver installs from section \[VMnetBridge.Install] in "c:\windows\inf\oem20.inf".

#I320 Class GUID of device remains: \{4D36E974-E325-11CE-BFC1-08002BE10318}.

#I060 Set selected driver.

#I058 Selected best compatible driver.

\[2003/10/12 13:40:09 3496.31]

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding F312D0F5B2BAAA4C598CDFAA2753A443 M Global\MSI0000

#E412 Per-machine codesigning policy settings appear to have been tampered with. Error 13: The data is invalid.

#E414 Default of 1 could not be restored to "Policy" value under HKEY_LOCAL_MACHINE\Software\Microsoft\Driver Signing. Error 5: Access is denied.

\[2003/10/12 13:40:09 3496.34]

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding F312D0F5B2BAAA4C598CDFAA2753A443 M Global\MSI0000

#E412 Per-machine codesigning policy settings appear to have been tampered with. Error 13: The data is invalid.

#E414 Default of 1 could not be restored to "Policy" value under HKEY_LOCAL_MACHINE\Software\Microsoft\Driver Signing. Error 5: Access is denied.

\[2003/10/12 13:40:09 3496.30]

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding F312D0F5B2BAAA4C598CDFAA2753A443 M Global\MSI0000

#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.

#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem20.inf" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.

#-024 Copying file "C:\Program Files\VMware\VMware Workstation\vmnetbridge.dll" to "C:\WINDOWS\System32\vmnetbridge.dll".

#E360 An unsigned or incorrectly signed file "C:\Program Files\VMware\VMware Workstation\vmnetbridge.dll" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.

#-336 Copying file "C:\Program Files\VMware\VMware Workstation\vmnet.sys" to "C:\WINDOWS\System32\DRIVERS\vmnet.sys" via temporary file "C:\WINDOWS\System32\DRIVERS\SET3A.tmp".

#E360 An unsigned or incorrectly signed file "C:\Program Files\VMware\VMware Workstation\vmnet.sys" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.

#-336 Copying file "C:\Program Files\VMware\VMware Workstation\vmnetbridge.sys" to "C:\WINDOWS\System32\DRIVERS\vmnetbridge.sys" via temporary file "C:\WINDOWS\System32\DRIVERS\SET3B.tmp".

#E360 An unsigned or incorrectly signed file "C:\Program Files\VMware\VMware Workstation\vmnetbridge.sys" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.

After uninstalling and reinstalling further into the same file the following lines were identified:

\[2003/10/31 13:13:09 3408.1]

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding A7995CF1DD51B23DFD8117BA53FDD87C M Global\MSI0000

\[2003/10/31 13:13:10 3408.27 Driver Install]

#-019 Searching for hardware ID(s): vmware_bridge

#-198 Command line processed: C:\WINDOWS\System32\MsiExec.exe -Embedding A7995CF1DD51B23DFD8117BA53FDD87C M Global\MSI0000

#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.

Report Abuse

MrSecurity411

3 posts since
Nov 3, 2003

Currently Being Moderated

4. Nov 14, 2003 7:59 AM

in response to: md

Re: Bridging Failing to Install

I posted the additional log information to the previous message. Additionally, I have tried manually adding the bridging protocol through the "Install..." and providing the .inf that resides in the application directory for the bridging protocol but it specifies an error that there isn't any information related to my system located in the .inf.

Note: What I did the install then uninstall then install, I deleted the installation directory to make sure it was completely cleaned up.

It is more than likely the .inf cache has become corrupt, but until I have time to try to recreate the issue on another machine or rebuild this one I can't verify that.

Report Abuse

404 posts since
Oct 24, 2003

Currently Being Moderated

5. Nov 15, 2003 12:20 PM

in response to: MrSecurity411

Re: Bridging Failing to Install

The additional information you posted has "There are no compatible drivers for this device", which is consistent with the infcache file not being up-to-date (since the cache is, or might, be causing Windows to look in the wrong inf file).

The issue likely would, or should, have gone away if the infcache.1 file was deleted after the uninstall and before the install.

Another potential option is to modify the netbridge.inf file in a harmless way (e.g., add a few words to the comment at the top of the file), and try to install again via the "Install..." option. I realize this sounds weird, but Windows compares inf files to see if it already has a copy in c:\windows\inf. By modifying the file you'll cause them to not match exactly, so Windows might re-copy the file and react differently to the install.