VMWare 6.5 issue.

By normhaga ·
I loaded up VMWare 6.5 workstation and lost the the ability to automatically open files when a CD/DVD or USB drive was opened. I also found out the hard way that VMW 6.5 corrupted my backups made in XP (not a VM) when used with Paragon Drive Backup 8.51. When I restored a backup from both the restore partition I created with drive backup on the local HD and also the remote backup on a USB drive I would either be unable to make Outlook function, loose my wireless, or else be unable to get the OS to recognize my cellphone, Also my printer would function erratically. These occurred across three seperate BK ups made after bare metal installations to test for VM issues.

The machine this occurred on is an HP DV9225US, has 4 gigs of ram (while 1 gig over what XP will recognize and two over what HP says the machine maxes at, it is there to allow symmetric dual channel functionality), The OS is XP SP3 with all current updates at the time that VMW 6.5 was installed. There is no problem with the ram, it is recognized by the bios and 3 gigs are recognized by XP (expected) plus a little for the discrete graphics.

I checked the VMW forums and could find no reference to the issues. This did not occur with VMW Workstation ACE 6.05. I could not locate the registry keys to check for misconfigurations.

Does anyone have any suggestions?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Automatically open files whith a CD/DVD or USB drive

This will give you extra code to put into the Autorun.ini file of both drives.

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Collapse -

While informative...

by normhaga In reply to Automatically open files ...

The information that you provided does not address the issues I am inquiring about.

Those issues are:
1. While not active - meaning only the background processes the start at boot are running, no VM's active - I lose all ability to automatically open any USB device or CD/DVD. Even after uninstalling the program I am unable to restore this ability without reloading the OS.

2. While not active, backups are corrupted. The corruption is unusual in that it destroys the functionality of connecting to certain web based email repositories such as hotmail (paid account) and Yahoo mail (also paid), as well as the mail handlers on my own website via Outlook 2003 when such accounts were functioning properly at the time the backup was taken. Nothing allows me to reconnect to these mail handlers short of a complete OS rebuild.

3. When restoring from a known good backup with VMW 6.5 I lose the ability to connect with my cell phone via USB cable.

4. After a restore from a known good backup when VMW 6.5 is present, I lose my wireless connectivity capability.

To me, this sound like registry entries are modified. I can not find them though. These bugs (?) features are new to VMW 6.5 and do not occur in VMW 6.05. Because the machine in which VMW for Windows resides is a trouble shooting machine, a VM is mandantory. On my Linux boxes - five of them, this problem does not occur.

Collapse -

Try this out for your issue, it might help with your USB devices.

Solution to USB or FireWire drive not showing.
However, the disconnect conflicted storage device to free up the drive letter fix may not be practicable or usable by some, such as computers which are on a network or system running data transfer activity to all its drive assignments continuously flow without stopping, and thus disconnect or reassigning any mapped drives, networked drives, removable drives or other storage drives is not an option.

In this situation, there is another workaround hack to fix the no USB or FireWire drive issue. The workaround fix relies on the registry tweak below to change the drive letter that has been previously assigned to the mounted USB or FireWire portable mobile flash or hard disk drive. Or if users wish, can opt to delete any reference to the detected drives by the device so that when the storage device is plugged in again, the whole drive letter assignment will be start from fresh, and clean.

1.Login to Windows as an Administrator.

2.Open Registry Editor by typing regedit (or regedt32.exe in older Windows prior to XP) in Run command of Start Menu and then press Enter.

3.Navigate to the following registry key:

4.Optional step which not required in Windows XP or later, right click on MountedDevices, then select Permissions. You can also click Permissions from the Security menu.

5.Optional step which not required in Windows XP or later, check the option to make sure that Administrators have full control to the registry key. Change and revert back this setting when you are finished with the reset of the steps.

6.If you run above 2 steps in OS earlier than Windows XP, quit regedt32.exe and run regedit.exe.

7.Also in the HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices registry branch selected, in the right pane, find and locate a registry value which represents the troubled USB or FireWire drive. The registry key should have the name that resembles the format of \DosDevice\X: where X can be any alphabet letter which corresponding to your physical system drive letter.

Here?s a guidelines that you can follow to quickly determine which registry key is linked to your conflicted drive letter:
Exclude \DosDevice\A: and \DosDevice\B: which normally reserved for floppy disk drives.

Exclude \DosDevice\C: which normally is the system root drive.

If you have more than one fixed hard disk drives, then any drive letters that are using by them is not possible linked again, UNLESS the additional hard disk drive is added AFTER you first use the USB or FireWire device that now unable to show.
Same case with CD-ROM or DVD-ROM optical drive as above reasoning.

If you have inserted and mounted a lot of thumbdrives, USB flask drive, or external hard disks before, you will likely still see a lot of remaining registry values that you won?t know which is which. In this case, double click on each remaining registry key values to view its binary data. Inside the binary data, there will be trace of the name of the device that this registry key represents.

With this information, search for a registry value that contains name of your USB or FireWire drive brand and model that having problem showing up in Explorer.

8.Once the correct registry value is determined (for example, \DosDevices\F:), right click on the registry value name, and the select Rename.

9.Change the drive letter (example F) to another unused drive letter that hasn?t been used by another other drives, then press Enter.

10.Now insert and plug in the USB or FireWire device into the port again (if it?s already inserted, take it out and re-insert again). The drive letter for the USB and FireWire should now appear and you can use the drive normally and properly again.

11.For OS earlier than Windows XP which you have previously change the permissions for the registry key, quit Regedit.exe and start Regedt32.exe, and change the permissions back to the previous setting for Administrators (which should be Read Only).
It?s also possible to simply delete the devices registry keys instead of renaming it. Deletion is helpful as users really can?t find the the registry value for the drive letter that having problem. But make sure that you do a backup for the registry branch by exporting MountedDevices key, as mistakes may cause your system to become unbootable. The delete all possible USB drives, FireWire drives and external drives which have drive letter temporarily only when inserted in the system, and DO NOT delete any of the fixed hard disk drives or CD/DVD optical drives registry values.

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Collapse -


by normhaga In reply to VMWare 6.5 issue.

Related Discussions

Related Forums