Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work on a computer where the folder "Documents" is mapped to a network drive (H:). From time to time that causes problems with software installation.

Recently I was installing IAR Embedded Workbench and as part of it the drivers for SafeNet's Sentinel USB dongle which holds the license for that piece of software.

After switching to Windows 7 the part of the installation which installed the drivers for the dongle failed and as a result I could not use the software. The installation failed with message box (entitled "Sentinel Protection Installer - Installer Information" saying:

"Error 1327. Invalid Drive H:\"

Initially, the tech support at SafeNet recommended to clean up the installation with their SSD clean-up software (I tried both 32-bit and 64-bit versions) and reinstall the drivers with a separate installation bundle ( However, that installation failed just the same.

An attempt to use "Update Driver Software" option in Device Manager with a bare driver files from a custom ZIP provided by SafeNet failed as well.

share|improve this question

migrated from Feb 8 '13 at 12:17

This question came from our site for professional and enthusiast programmers.

This isn't something we can help you with. You need to contact SafeNet and have them fix their installer. Why the installer is even doing ANYTHING to your Documents directory should concern you. You claim you used an .inf and it failed, if thats the case, then your system configuration is to blame. – Ramhound Feb 8 '13 at 12:21
As I mentioned in my post I was in touch with SafeNet - they were not able to help. – user2054027 Feb 8 '13 at 12:33
Anyway, in the end the solution was to run the following command to temporarily reassign the network drive back to the system drive: subst H: "C:\Windows" – user2054027 Feb 8 '13 at 12:34
You contacted them once, they gave you a "level 1" technical answer. My suggestion was to escalate the problem to the highest level possible. – Ramhound Feb 8 '13 at 13:30

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

Take from

Fix error1327

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .