Saturday, April 04, 2009

Error 1327 Invalid Drive when installing VMware Server

When I try to install WMware Server in Windows 7 (also happened on Vista and XP), I get the message Error 1327 Invalid Drive S:\ and the installation aborts.

For some reason, the VMware installer does not like when you change the default location of your shell folders. I have my Windows shell folders (My Documents, My Music, My Video, My Pictures) mapped to a network drive S:.

The workaround is to temporary change your shell folders back to the default location. An easy way to do it, it is by changing the User Shell Folders registry key. Be careful when editing your Windows registry, so use the following steps at your own risk.

1. Run regedit.exe

2. Locate the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

3. Click on File, Export and save this key to your desktop.

4. Change all entries that uses your mapped drive (S: in my case) to the default one (%USERPROFILE%).

5. Now, Install VMware Server.

6. After installation completes, restore your User Shell Folders registry info by double clicking on the file saved on step #3.

That is, you were able to install VMware server and also keep your shell folders at you custom location. I hope VMware folks fix this issue on their installer. Other people were also having this same issue when installing VMware tools.

21 comments:

Anonymous said...

This was helpful in installing software on Windows 7.

Thank you very much.

Unknown said...

I had solve this problem simply.
Just one click needed.
You can find usb connect logo in bottom of vmware windows. (right side.)
Just click for active USB external hard drive.

And then you can install virtual machine without this error(1327).

It's simple.

Unknown said...

I had solve this problem simply.

Needed just one click.
You can find usb icon in bottom of vmware windows.(right side)

Just click for activate external hdd.
You can have to connect external hdd as same as Windows environment.

If you can access external hdd like drive(like h:), then try install virtual machine.
You can do that without any error.

Very simple.

From Young in Korea

Shnuggle said...

Worked for me to remove an old F:/ drive - thanks!

Anonymous said...

Just a thought, but the USB connect solution isn't going to work in every instance. In my case, the "invalid drive" error was related to mapped network drive (which has nothing to do with USB drives), and this solution worked perfectly.

It appears Windows 7 has a problem with any drive letters that are associated with drives not local to the PC.

mbelsky said...

v this adobe forum mentions tht the reason for the error is that by default, vista doesnt give the required system account access to the network share. follow these instructions to fix your issue:

So here's how you solve it:
1. Disconnect the previously mapped network drive from Windows Explorer.
2. Right click on Command Prompt in the Start Menu and select Run As Administrator.
3. Type "Net Use y: \\servername\sharename"
4. Exit out of the command prompt
5. Open Windows Explorer
6. Click 'Map network drive' menu item
7. Select the y: drive and typed \\servername\sharename into the Folder box.

Not very intuitive, but it works!

EASIER WAY: If you already have a mapped network drive, just do steps 2-4 and it should work...essentially you map it once for the user, once for the administrator.


FROM:
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=3890

Anonymous said...

I could not install seiko data label software on windows 7 until I read this... Thanks - Looks like a another ms w7 bug.

Hosting said...

I have the same problem installing vmtools on a windows 2003 VM on ESXI4

Anonymous said...

Saved my day :)

Palmetto said...

So much for hoping VMware fixed this. 17 months later and it still isn't fixed. Thanks for the work-around.

Marcus said...

Thank you so much for the solution. It workes also when trying to install other software (in my case HP Printer Driver). Thanks again.

Anonymous said...

I followed the instructions and its an easy fix even for a non computer expert, a great help thanks very much.

Anonymous said...

nasir:
hello
thanks for this solution
bye

Anonymous said...

Thanks mbelsky! Your method worked perfectly for me and is much more simpel than hacking around in the registry.

Anonymous said...

i also find this step useful by using it, but a little bit different..

1. share one of your folder at c: drive (full access shared). (i located my installation folder in c:\program files\vmware). If you dont have that folder, make one first then share it.

2. open windows explorer and map that shared folder (in step 1) as drive z: (for example z:)

3. Run regedit.exe

4. Locate the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

5. Click on File, Export and save this key to your desktop.

6. Change all entries that uses your mapped drive (S: in my case) to the default one (%USERPROFILE%).

7. Now, Install VMware Server.

8. After installation completes, restore your User Shell Folders registry info by double clicking on the file saved on step #3.

Thats it!

paul said...

Thank you for the post - we had issues with installing an Intel IPP update for a camera microscope. Your post provided a quick workaround.

Anonymous said...

Dear Luis,

I had a similar problem with software for a ScanSnap from Fujitsu.

Thank you! This totally fixed my problem.

Sincerely,
Ernie

Kristin Macy said...

Worked like a champ! Great info, found it with a simple search and you gave great instructions.

Liz said...

Thanks a stack!! This was perfect. I couldn't install Acrobat Reader, nor a multitude of other programs

Anonymous said...

This worked for Adobe Lightroom issues too, THANKS!

Unknown said...

The simple and quick resolutions to repair 1327 error are outlined below:

>> Enter Valid Path of My Documents in your Registry
>> Make Required Changes
>> Restore the Original Drive Letter
>> Temporarily Map a Folder to the Drive Letter

Taken from:

http://sorcim.com/knowledgebase/1327.html


Spring Boot Configuration Properties Localization

Spring Boot allows to externalize application configuration by using properties files or YAML files. Spring Profiles  provide a way to segr...