Get it from the official source
We don't host files. These links take you straight to the genuine, safe installer on the developer's website.
"Setup was unable to create the directory" followed by something like "Error 5: Access is denied" is a classic permissions wall. The installer is trying to make a folder, usually somewhere under Program Files, and Windows is refusing. It almost never means the software is broken; it means the account running the installer doesn't have the rights to write where it's trying to write, or something is locking that path.
This error shows up with installers built on Inno Setup, NSIS, and MSI alike, and the wording varies slightly between them. The causes cluster tightly: missing administrator rights, an antivirus or controlled-folder feature blocking the write, a leftover folder from a previous install that's locked or read-only, or a target path that's invalid or on a drive that isn't writable.
Below, we go through each cause and the matching fix, starting with the one that solves it most often, running as administrator, and ending with the rarer cases. Always make sure your installer came from the official vendor before troubleshooting, since a corrupt or tampered installer can fail in confusing ways too.
Helpful tools
Microsoft Sysinternals Process Explorer
Finds which process is locking a folder or file during install
Visit official site ↗
Sysinternals Handle
Lists open file handles to release a locked install directory
Visit official site ↗
Microsoft Defender
Manages Controlled Folder Access allow-lists for installers
Visit official site ↗
Windows PowerShell
Take ownership and set folder permissions via takeown and icacls
Visit official site ↗Step-by-step fix
-
1
Close the application and any related background processes in Task Manager, then right-click the installer and choose Run as administrator.
-
2
If you lack admin rights, install to a per-user location (your Documents or AppData) or ask your IT administrator.
-
3
Open Windows Security > Virus & threat protection > Ransomware protection and disable or allow-list the installer under Controlled Folder Access.
-
4
Temporarily disable third-party antivirus folder-shield features, then retry the install.
-
5
Navigate to the target folder; delete any stale leftover folder, or take ownership and grant your account Full Control in the Security tab.
-
6
Choose a short, simple install path on your system drive such as C:\Apps\ProgramName instead of long or network paths.
-
7
Confirm the destination drive has free space and is not read-only or disconnected.
-
8
If it still fails, re-download the installer from the official site, verify its checksum, and run it again as administrator.
The Usual Cause: Missing Administrator Rights
By far the most common reason is that the installer needs to write into a protected location like C:\Program Files but is running without elevation. Standard user accounts can't create folders there, so the setup fails immediately.
The fix is simple: right-click the installer and choose Run as administrator. If you're on a work or school PC, you may not have admin rights at all, in which case ask your IT administrator or install to a per-user location such as your own AppData or Documents folder if the installer offers that option.
Antivirus and Controlled Folder Access
Security software can block an installer from creating folders, especially Windows' Controlled Folder Access (part of ransomware protection), which prevents unrecognized programs from writing into protected directories.
Check Windows Security > Virus & threat protection > Ransomware protection. If Controlled Folder Access is on, either add the installer to the allowed apps list or temporarily disable it for the install. Third-party antivirus suites have similar "folder shield" features worth checking too.
Leftover or Locked Folders From a Previous Install
If you're reinstalling or upgrading, an old folder may still exist with restrictive permissions, or a running process may have a file inside it locked. The installer then can't create or overwrite the directory.
Close the application completely (check Task Manager for lingering processes), then navigate to the target folder. If it exists and is empty or stale, delete it, or take ownership and grant your account Full Control via the folder's Security tab. Then rerun the installer.
Invalid Path, Long Names, or a Read-Only Drive
Occasionally the chosen install path is the real problem. A path with illegal characters, an extremely long name exceeding the path limit, a drive that's full or write-protected, or a removable/network drive that disconnected mid-install can all trigger this error.
Try installing to a short, simple path on your system drive, for example C:\Apps\ProgramName. Confirm the destination drive has free space and isn't set to read-only. For network or USB targets, install locally first and move the files afterward if needed.
When the Installer Itself Is the Problem
A corrupted download can also surface as a directory-creation failure when the installer's extraction step fails. If running as admin and clearing folders doesn't help, the installer file may be incomplete.
Re-download it from the official vendor site and verify the checksum if one is provided. Avoid third-party download portals that wrap installers in their own "download manager," since those repackaged files are a frequent source of odd setup errors.
Frequently asked questions
Questions & answers
No questions yet — be the first to ask!
Ask a question
Please sign in with your email to ask a question.
Comments (0)
No comments yet. Share your experience!
Leave a comment
Please sign in with your email to comment.