- Worldstart's Tech Tips And Computer Help - http://www.worldstart.com -

Invalid Driver Error: 1327

Invalid Drive Error: 1327

Ever receive an error for a drive that you don’t even have on your computer? That would be a little strange, wouldn’t it? Well, we actually received a phone call about this yesterday and we thought it was beyond important enough to include in the newsletter. This is actually a common error that seems to be popping up more and more lately, so if you haven’t come across it yet, you might very soon, so this is definitely one tip everyone will want to pay attention to.

First of all, this error is number 1327 and it has to do with an invalid drive. It could be any of the drives on your computer, but it’s mostly been listed under drives D: and E:. The drive letter will just vary depending on the type of computer you have.

This type of error actually falls under several causes. The main one though is that the installation on a particular piece of software was created with a type of hard-coded transfer path to a drive that doesn’t even exist on the computer. For example, when you try to install some software, you may receive the error listed under drive E:. Well, chances are, you don’t even have an E: drive on your computer. So, you tell me how much sense that makes! Unfortunately, if this is the case, there’s no way to make the software install under a different drive. The only thing you can really do is contact the vendor of the software and they can help you out.

Some of the more unknown causes are that your CD ROM or DVD ROM drive letters have changed since a previous install, you could have changed the drive letter for your hard drive in which the operating system of your computer is installed on (it’s usually supposed to be drive C:) or a registry key may have an invalid data value entry.

Now, since error 1327 has all of these causes, it’s possible that you’ll have to check out various items on your computer to try and get the problem fixed. Below are some of the suggestions we have for you. These are all for Windows XP users, because it is the operating system that this error mostly occurs under.

Begin by going to Start, Control Panel, Administrative Tools, Computer Management. (You must be in the classic Control Panel view for this to work). Next, click on Disk Management and then click on the drive that contains your operating system. From there, choose Change Drive Letter and Path. Now, click Edit and change that back to the original drive letter that it’s supposed to be. Click OK and Close to finish. Then try running the installation again.

The next best thing to check on is your registry entries. This, of course, requires you to work within the Registry Editor. If the modifications are done incorrectly, you could cause other problems for your computer, so if you’re not 100 percent sure about what you’re doing, please seek help from someone who does. You may also want to back up your registry [1] before starting.

If you’re ready to do this, go to Start, Run, type in “regedit” and click OK for the Registry Editor to open. Next, find this registry key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders.

Once you’re there, look at the values under the Data column of every entry. If you find that one value has an incorrect drive letter, right click it and choose Modify. Then just type in the correct drive letter in the Value Data spot and click OK. For instance, if you see that one of the entries has a letter X: for the drive, that’s obviously incorrect. Change it to C: and you should be good to go. Make sure you repeat these steps for every entry that you see is wrong. If you’re still having trouble with that, you can also check the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

Once you’re done checking what you need to, close the Registry Editor and try installing the software again.

Now, if neither of those two suggestions worked for you, the only other thing you can do is contact the software vendor, as I mentioned before. They are the ones who created the actual installation and they should have other suggestions on tap for anyone who has trouble. Sometimes the installation process just goes beyond the consumer and there’s nothing you can do about it. Don’t feel bad! You’re not the only one this has happened to. Just do what you can and if you need more help, call!

~ Erin