Error 1327. Invalid Drive N:

[Tesla]

Hi all

 

Trying to install an MSI of a program, and get this issue upon starting the installation wizard

 

this has popped up in the past, but my usual work around is to not map the drives (my pc is not on the domain, i use a seperate Logon script to map the drives), but even if i don't, and i save the download to my local drive, this error still pops up. any ideas?

[Tesla]

bumppp

[sted]

is your my docs redirected to the right place/broken ive seen this when my docs etc get borked up

[Tesla]

it doesnt matter where i save it, it always has that error message. tried a reg fix i've seen, and that made no difference (cross referenced with a laptop that isnt on network either, and it runs fine from that laptop....)

[gavins38]

I've seen this happen when the My Documents folder is redirected to a network location by group policy.

[Tesla]

Is there a fix for that? That's what is set up on my px

[Meldrew]

Is there a fix for that? That's what is set up on my px

 

A workaround I've used is to disconnect N as a mapped drive (temporarily), then use the DOS subst command to create a 'fake' N drive that points to say a temporary folder on your hard drive, so for example create a folder on the root of C drive, called tempNdrive, then in a dos box, type:

 

subst n: c:\tempNdrive

 

Then install your program (hopefully it'll work this time)

 

When you are finished, at a DOS box again, type:

subst n: /d

To remove the drive and then you can manually remap your N drive back to where it was supposed to be, or logoff/on whichever you choose.

 

Meldrew

[Tesla]

thanks @Meldrew, was able to install it, what a pain in the **** though, there doesn't seem to be any logic to it.... (still, if anyone has a more permanent fix for this.... :] )

[Tesla]

...does anyone have a more permanent fix for this?

[gavins38]

In Group Policy or your login script (whichever is redirecting your My Documents folder) change the redirect from a drive letter to the full UNC path name. I've heard that this resolves the problem although I've not tested it personally.

[tmcd35]

This happens when a drive is referenced in the registry and not available to the computer, regardless to whether or not the installer needs to use that drive. The solution should be to either map the drive to a valid location (doesn't matter where) or search the registry for every mention of the drive and delete it from the registry.