If you’ve encountered the error “Could not access network location %SystemDrive%\inetpub\wwwroot" while installing software (like Infragistics NetAdvantage) or configuring IIS on Windows, you’re not alone. This common issue occurs when the Windows registry contains an incorrect path reference to the IIS wwwroot directory.

What Causes This Error?

This error typically occurs when:

• Installing web development software that needs to access IIS
• The registry contains environment variables instead of actual paths
• IIS configuration is corrupted or incomplete
• Software installers cannot resolve the %SystemDrive% environment variable

The Solution: Registry Path Fix

⚠️ Important: Always backup your registry before making changes. Registry editing can be dangerous if done incorrectly.

Step-by-Step Fix

1. Open Registry Editor
   • Press Windows + R to open the Run dialog
   • Type regedit and press Enter
   • Click “Yes” if prompted by User Account Control
2. Navigate to the Registry Key
   • Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\PathWWWRoot
   • You can paste this path directly into the registry editor’s address bar
3. Modify the Registry Value
   • Double-click on the PathWWWRoot entry
   • Current (problematic) value: %SystemDrive%\inetpub\wwwroot or \inetpub\wwwroot\
   • New (fixed) value: C:\inetpub\wwwroot
   • Click OK to save the changes
4. Verify the Change
   • Ensure the value now shows the full path without environment variables
   • Close Registry Editor
5. Restart and Test
   • Restart your computer or the installer
   • Retry the installation or operation that was failing

Alternative Solutions

Method 2: Create the Directory Manually

If the directory doesn’t exist:

mkdir C:\inetpub\wwwroot

Method 3: Reinstall IIS

If the problem persists, consider reinstalling IIS:

1. Go to Control Panel → Programs and Features
2. Click Turn Windows features on or off
3. Uncheck Internet Information Services
4. Restart Windows
5. Re-enable IIS with the same steps

Custom IIS Installation Paths

If your IIS wwwroot is installed in a different location:

• Use that custom path instead of C:\inetpub\wwwroot
• Common alternative locations:
  • D:\inetpub\wwwroot
  • C:\wwwroot
  • Custom enterprise paths

Verification Steps

After applying the fix, verify it worked:

1. Check IIS Manager
   • Open IIS Manager
   • Verify the Default Web Site points to the correct physical path
2. Test Registry Value
   • Run: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp" /v PathWWWRoot
   • Should return the absolute path without environment variables

Prevention Tips

• Always use absolute paths in IIS configuration
• Regularly backup your registry before software installations
• Keep IIS updated to the latest version
• Use IIS Manager to verify paths after installations

Troubleshooting

If the fix doesn’t work:

• Ensure you have administrator privileges
• Check if the path actually exists on your system
• Verify IIS is properly installed
• Look for additional registry keys that might need updating

---

Note: This solution has been tested on Windows 7, Windows 10, and Windows Server versions. The registry path remains consistent across these platforms.

Have you encountered this error with other software? Share your experience in the comments below!

-->