Error 1606
Error 1606. Could not access network location
Same underlying problem as error 1327: a folder path recorded in Windows points somewhere that no longer exists. Here it is a network path rather than a drive letter.
What it actually means
Installers read the standard shell folder locations. If any of them was redirected to a share that is now unreachable, or contains a stale variable, the installer cannot resolve the path and stops before doing anything.
How to fix it, in order
Ordered by how often each one is the answer, not by how clever it sounds.
- 01Read the path in the error message. It names the location Windows cannot reach.
- 02If it is a network share you still have, reconnect to it and retry.
- 03Otherwise correct the shell folder paths under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders so they point at local folders on C:.
- 04Check the same key under HKEY_LOCAL_MACHINE as well, since a machine-wide redirect produces the identical error for every user.
- 05Sign out and back in so Explorer picks up the corrected paths before retrying.
Common questions
- How do I fix error 1606 could not access network location?
- A shell folder path points at an unreachable location. Correct the entries under User Shell Folders in the registry so they point at local folders, or reconnect the network share named in the error.
Before you retry the installer
If the package came from anywhere other than the publisher, confirm it is the file they actually shipped. Check its SHA-256 against our index, which settles in seconds whether you are debugging an installer or a damaged download.