Invalid Drive 1327


I have a msi whose shortcut points to an exe that is located the W drive. The Customer has provided me the shortcut and have asked to include in the msi , they have not provided with the exe (they have mentioned that this would work in their environment). While Installing the msi , I have created a dummy drive as W and tested for the msi working. It works fine. Now, Iam asked to avoid this error during installation without creating the Drive W.

To Put it Simple: Is it possible to install a package avoiding 1327 Invalid drive error without having the actual drive in the physical machine. the shortcut being pointed to the same drive?? If so plz help

0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Remove the shortcut from the shortcut table and add a .lnk file to the file table to deploy the shortcut.
Posted by: anonymous_9363 8 years ago
Red Belt

I think the only other way to do what you want would be with a script. That path is fraught with its own problems, not the least of which is that most script examples are pretty basic, with little or no error-trapping and so on.

On an unrelated note, I'm curious as to why your post has so many tags for the AppDeploy repackager, since your question has nothing to do with that product.

  • Thanks Scab !

    Sorry about the tagging. This is my first Post and was in need of some immediate suggestions. Have modified that tags :) - learnmore 8 years ago
Posted by: jagadeish 8 years ago
Red Belt

Please have a public property named EXEFILEPATH="W:\MyApplication\MYApplication.exe" (with correct network path) in property table and enter [EXEFILEPATH] in target section when you create a command line shortcut..

If you want to change the Network Path/Driver Letter in future, simply you can change the path through command line. you no need to redevelop the MSI with new path.

Do you know that W:\ is refering to which path in your environment.. If you know it and if the path is not too long then you can directly use the path in EXEFILEPATH variable instead of using "W:\MyApplication\MYApplication.exe"

For Example: \\SERVERPATH\NEWApps\MyApplication\MyApplication.exe


Posted by: dunnpy 8 years ago
Red Belt

Just a thought - why not remove the shortcut from the shortcut table and add a .lnk file to the file table to deploy the shortcut?

That way it won't try to verify the shortcut path, but will just drop the shortcut file that will poin to the correct place.


Hope that helps,


  • Yes, this willl be the better option so that it will not ask for the drive and one more option is to create command line shortcut. - Visalakshi 8 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ