Fix it now
Windows Installer resolved a path, found the drive letter in it missing, and stopped. Microsoft’s message is simply “Invalid Drive: [2]”. The letter is nearly always stored in a shell folder value that was pointed at a mapped drive or removable device which is no longer there.
net use
subst
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders"
reg export "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" %USERPROFILE%\Desktop\ushell.reg
- Note the drive letter in the error, then look for it in the
reg queryoutput. Any value whose data starts with that letter is your culprit. - If the letter was a mapped network drive you still use, reconnect it with
net use X: \\server\shareand rerun setup. - Otherwise change the value back to a local path, using the expandable form the default uses, such as
%USERPROFILE%\Documents, then sign out and back in. - If you need the install through immediately, create a temporary stand-in:
subst X: C:\temp, install, then remove it withsubst X: /D.
Export the branch before you edit it. The command above writes a .reg file to your Desktop that puts the original values back if you set one wrongly.
If setup completes without naming a drive letter you are done. If it names one you cannot find, the next section covers the profiles that are easy to miss.
Why it happens
Windows keeps a set of folder locations for each profile: Desktop, Documents, Favorites, AppData and several more. If any of them were pointed at a mapped drive, and the mapping has gone, an installer that touches one of those locations resolves the path, finds no volume behind the letter and raises 1327. The letter in the message is the fastest clue you will get.
The values live in two keys per profile, one holding expandable paths and one holding the literal paths currently in use. There is also a machine-wide set and a set belonging to the default profile. Because a per-machine install runs as SYSTEM rather than as you, a bad value outside your own profile produces 1327 even though every interactive account looks correct.
The neighbouring codes describe related path failures, and one of them means two different things depending on where you see it. As a Windows Installer message, 1606 is published as “Could not access location [2]” – no mention of the network, despite how often it is described that way. As a Win32 return code, 1606 is ERROR_UNKNOWN_FEATURE, “Feature ID not registered”, and that is what the HRESULT 0x80070646 wraps. They are unrelated problems that happen to share a number.
2343, 2707 and 2727 are internal errors about the package’s own directory table rather than about your machine. 2343 is published as “Specified path is empty”. 2707 says target paths were not created because no path exists for an entry in the Directory table. 2727 says a directory entry does not exist in that table at all. If those appear without 1327, you are looking at a packaging fault and the vendor is the right destination.
A user shell folder still points at a mapped drive
You have this one if The letter in the error matches a mapping that no longer exists, and the failure follows one user account between machines.
- In regedit, open
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. - Change any value whose data begins with the missing letter back to a local path, keeping the expandable form where the default uses one.
- Repeat in the
Shell Folderskey alongside it, which holds the resolved literal paths. - Sign out and back in so Explorer re-reads them, then rerun the installer.
The bad path is in a profile you are not logged into
You have this one if Every user hits 1327 for the same letter, including an account created five minutes ago that never had the mapping.
- Check the machine-wide set under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. - Check the default profile under
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. - Correct any value pointing at the missing letter, using local paths.
- Reboot so the installer service picks up the corrected values, then retry.
A per-machine install runs as SYSTEM, which has its own profile. A path that made sense to the administrator who first set the machine up can be meaningless to the account that performs the install.
The cached source location for a repair or patch is gone
You have this one if 1606 appears, or a repair or patch operation fails, and the path in the message is a share or removable media.
- Reconnect the share or reinsert the media so the original source is reachable, then retry.
- If the original source has gone for good, supply the installer file explicitly instead of letting Windows Installer look for its cached copy.
- For a patch that cannot find its base package, reinstall the base product from a location that will still exist later.
A source that is genuinely absent has its own code, 1612 ERROR_INSTALL_SOURCE_ABSENT, which is more specific than either 1606 or 1327 and worth looking for in the log.
The install target itself names a missing volume
You have this one if The error appears only when you choose a custom location, or when a silent install passes a target property.
- Rerun the installer and accept the default location to confirm the target is the problem.
- Check any target property being passed on the command line and make sure the drive exists.
- Use a fixed local drive rather than a removable or mapped one for the install target.
Full reference
The published wording, and the number that means two things
| Code | Where it comes from | Published meaning |
|---|---|---|
| 1327 | Windows Installer message | Invalid Drive: [2] |
| 1606 | Windows Installer message | Could not access location [2]. |
| 1606 | Win32 return code | ERROR_UNKNOWN_FEATURE: Feature ID not registered. |
| 0x80070646 | HRESULT | The Win32 return code above, wrapped: 0x646 is 1606 |
| 1612 | Win32 return code | ERROR_INSTALL_SOURCE_ABSENT: the installation source for this product is not available |
Treat 0x80070646 as the feature-identifier case, not as a missing source. It is commonly described online as a failed patch whose source could not be reached, and that is a different code entirely. If a repair or patch cannot find its media, look for 1612 or for the installer message 1606 in the log, both of which say so plainly.
Package-side errors that arrive at the same screen
| Number | Published message | Who fixes it |
|---|---|---|
| 2343 | Specified path is empty. | The package author |
| 2707 | Target paths not created. No path exists for entry [2] in Directory table. | The package author |
| 2727 | The directory entry [2] does not exist in the Directory table. | The package author |
These three are worth recognising precisely because there is nothing useful to do about them on the machine in front of you. They describe a package whose directory table does not resolve, and the correct action is to send the verbose log to whoever built it.
Where the paths live
| Location | What it holds |
|---|---|
HKCU\...\Explorer\User Shell Folders |
Per-user folder paths in expandable form |
HKCU\...\Explorer\Shell Folders |
The resolved literal paths Explorer is using now |
HKLM\...\Explorer\User Shell Folders |
Machine-wide defaults used before a profile loads |
HKEY_USERS\.DEFAULT\...\User Shell Folders |
The template applied to new profiles and used by system contexts |
subst |
Any virtual drive letters defined in the current session |
net use |
Network drive mappings for the current user |
Using subst safely
subst maps a drive letter to a local folder for the current session. It changes nothing on disk, needs no reboot, and is removed with subst X: /D. That makes it a legitimate way to get an install through while you sort out the underlying path, and a poor way to leave a machine: the mapping does not survive a restart, so anything that depends on it fails the next morning. Use it to unblock, then fix the shell folder value properly.
When the fix does not stick
- Check whether Folder Redirection policy is setting the path. If it is, your local edit is overwritten at the next refresh and the change belongs in the policy.
- Check for a logon script or profile management tool that recreates the mapping and repoints the folder.
- Confirm you edited the profile the installer actually runs under, not just your own.
- Look at both
User Shell FoldersandShell Folders; correcting one and leaving the other is the most common reason this comes back. - If the letter in the error is one nobody recognises, search the registry for it as a string – something wrote it, and finding what is quicker than guessing.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1327 |
A path used by the installation names a drive letter that is not present | Microsoft Learn |
1606 |
As a Windows Installer message, the named location could not be accessed | Microsoft Learn |
0x80070646 |
The HRESULT form of Win32 1606, ERROR_UNKNOWN_FEATURE – the feature identifier is not registered, which is a different problem from an unreachable path | Microsoft Learn |
2343 |
Specified path is empty – a fault in the package’s directory table | Microsoft Learn |
2707 |
Target paths were not created because no path exists for an entry in the package’s Directory table | Microsoft Learn |
2727 |
A directory entry referenced by the package does not exist in its Directory table | Microsoft Learn |
Confirm the fix worked
- Rerun the installer and confirm it completes without naming a drive letter.
- Open File Explorer and confirm Documents, Desktop and Downloads all open to real local locations.
- Run
substwith no arguments and confirm no leftover virtual drive is still defined. - Sign out and back in, then launch the installed application and confirm its shortcuts and per-user files resolve.
- Create a test user profile and confirm it does not inherit the bad path from the default profile.
Questions people ask about this
Will buying anything help?
No. This is a stale path in your own configuration and costs nothing to correct. No licence, key or upgrade has any bearing on where a shell folder points.
Is the subst trick safe?
Yes, as a temporary measure. It creates a virtual drive letter for the current session only, changes nothing on disk, and is removed with subst X: /D. Use it to get an install through, then fix the underlying path.
Why does the installer care about my Documents folder at all?
Many packages create shortcuts, sample files or per-user data during setup and resolve those locations through the shell folder values. One unreachable value is enough to stop the whole transaction.
I see 0x80070646 as well. Does that confirm a missing source?
No. 0x80070646 is Win32 1606 wrapped as an HRESULT, and Win32 1606 is ERROR_UNKNOWN_FEATURE – a feature identifier that is not registered. The missing-source case has its own code, 1612. The two get conflated because the Windows Installer message list also uses 1606, for something else again.
I fixed the registry but the error came back.
Check whether Folder Redirection policy is setting the path. If a policy points the folder at a share, your local edit is overwritten at the next refresh and the policy has to change instead.
