Error 1327 “Invalid Drive” while installing or updating applications in Windows

Symptoms

When trying to install or update an application, you receive an error message similar to the following:

I’ve encountered this error installing Google Earth and another application, and it also apparently happens with many others including Microsoft and Adobe applications.

Cause

These installers/updaters are failing to access the drive that one of your shell folders is on — probably your Personal folder, ‘My Documents’. This could be because:

1. the hard drive is no longer attached or isn’t recognized by the system, or the drive was a mapped network drive that is no longer mapped,
2. it’s a network folder / mapped drive on a computer or server that is not currently available, or
3. it’s a network folder / mapped drive that the installer/updater doesn’t have access to.

Resolutions

Cause 1: the drive is no longer attached or mapped

Reattach the hard drive or map the folder back to the drive. If you need help with these, ask your administrator or local geek.

Alternatively, update the registry to point your shell folder to a location that exists on a drive that exists. You may follow the directions at either Microsoft or Adobe for updating your registry (they are essentially identical).

Cause 2: The network folder is on a computer or server that is not currently available

Try again when the server is available (or see #1 above).

Cause 3: The installer/updater doesn’t have access to the network folder / mapped drive

The drive that your shell folder (again, probably ‘My Documents’) is on is a mapped network drive and is connected using your own user account. However, the application installer/updater is running as the Administrative user, which does not have access to your mapped network drives (even if you are an administrative user).

The way to resolve this is simple, seamless, and temporary. Let’s say that the network folder is \user\Robert LaThanh on a server named FileServer (so the full path would be \\FileServer\user\Robert LaThanh), and it’s mapped to the Z:‘drive. We’ll confirm these first (step #2)…

1. Run the Command Prompt as Administrator.
   1. Click on the Windows Logo (Start Menu)
   2. Type ‘Command Prompt’
   3. Right-click on the ‘Command Prompt’ shortcut and choose “Run as administrator”
   4. Click “Yes” in the User Account Control security dialog to allow the Command Prompt to run
2. Let’s verify that the drive is mapped but unavailable to the Administrator by typing net use at the command prompt. If this is the case, your output will look like this:

   C:\Windows\system32>net use
   New connections will be remembered.
   
   Status       Local  Remote                            Network
   -------------------------------------------------------------------------------
   Unavailable  Z:     \\FileServer\user\Robert LaThanh  Microsoft Windows Network
   The command completed successfully.

3. Remap the network folder as Administrator by typing net use Z: "\\FileServer\user\Robert LaThanh". (The double-quotes aren’t necessary if the network path does not contain any spaces.)

   C:\Windows\system32>net use Z: "\\FileServer\user\Robert LaThanh"
   The command completed successfully.
   

That’s it!

Your installer/updater should now work. This won’t affect your ability to use that drive, and once you reboot, you’re back to normal.