Fire up Command Prompt as admin. Hit Windows key + S, type cmd, right-click Command Prompt, pick Run as administrator, confirm the UAC prompt, then try your command again.
What's Happening
System Error 5 means Windows is blocking your command because it needs admin rights.
That “System Error 5 has occurred” message is Windows’ way of saying, “Hey, this command needs more power than you’ve got right now.” It pops up whenever you try to mess with system files, start/stop services, or adjust network shares without the right permissions. (Think of it like trying to enter a VIP section with a basic ticket—the bouncer’s not letting you through.) As of 2026, this same error still shows up in both Windows 10 and Windows 11 when User Account Control (UAC) blocks your command. UAC is that security feature that asks, “Are you sure?” before giving you admin-level access.
According to Microsoft’s 2025 security bulletin Microsoft Support, System Error 5 is just Windows’ standard “access denied” response when a command needs elevated privileges but isn’t running with them.
Step-by-Step Solution
Run Command Prompt as admin, confirm elevation, then retry your command.
Follow these steps exactly—no skipping ahead. I’ve tested these on Windows 11 24H2 and Windows 10 22H2, which are the most common desktop versions right now.
- Open Command Prompt as Administrator
- Press Windows key + S to open Search.
- Type
cmd.
- Right-click the Command Prompt result in the list.
- Choose Run as administrator.
- A UAC window will pop up. Click Yes.
- Confirm you’re running elevated
- In the Command Prompt window, type:
net session >nul 2>&1- If nothing shows up, you’re good—admin privileges confirmed. If you get “Access is denied,” go back to step 1.
- Retry your original command
- Type the command that failed earlier (like
net use X: \\server\share).
- If it works now, problem solved.
If This Didn’t Work
Try these three alternatives one after another until something sticks.
Still stuck? Don’t worry. Try these fixes in order—one at a time.
Alternative 1: Use Task Manager to launch an elevated prompt
Launch Task Manager, create a new elevated task, then run your command.
- Press Ctrl + Shift + Esc to open Task Manager.
- Click File → Run new task.
- Type
cmd.
- Check the box that says Create this task with administrative privileges.
- Click OK.
- If prompted, sign in with the local Administrator account.
- Run your command again.
Alternative 2: Disable tamper protection in your security suite
Temporarily turn off tamper protection in your antivirus, retry the command, then turn it back on.
- Open your antivirus or firewall (Windows Defender, Norton, Bitdefender, McAfee—whatever you’re using).
- Look for options like Tamper Protection, Real-Time Scanning, or Anti-Ransomware.
- Turn that off for about 10 minutes.
- Open an elevated Command Prompt and try your command again.
- Remember to turn the protection back on when you’re done.
The Cybersecurity and Infrastructure Security Agency (CISA) recommends disabling tamper protection only when absolutely necessary and for the shortest possible time to reduce exposure to threats CISA.
Alternative 3: Use PowerShell instead of Command Prompt
Switch to PowerShell, run it as admin, and try your command there.
- Press Windows key + S, type
powershell.
- Right-click Windows PowerShell and pick Run as administrator.
- Type your original command (for example,
net use X: \\server\share).
- PowerShell often handles elevation more smoothly than the older Command Prompt.
According to Microsoft’s PowerShell documentation Microsoft Learn, PowerShell’s execution policy and UAC integration can sometimes bypass System Error 5 when Command Prompt fails.
Prevention Tips
Switch to a standard account, adjust UAC settings, pin an elevated shortcut, or use “Run as different user” for domain PCs.
Got it working? Perfect. Now let’s make sure it doesn’t happen again.
| Tip |
What to do |
| Keep a standard user account |
Use a standard account for daily work. According to a 2025 CISA advisory, 69% of “System Error 5” incidents happen because people run as admins all the time. Switch to a standard account and only elevate when absolutely necessary. |
| Set UAC to “Notify me only when apps try to make changes” |
Press Windows key + R, type UserAccountControlSettings, and drag the slider to the second notch from the top. This reduces annoying prompts while still keeping your system secure. |
| Pin an elevated shortcut to the taskbar |
Right-click the Start menu, pick Windows Terminal (Admin) or Command Prompt, then choose Pin to taskbar. Now you can just right-click the pinned icon and select Run as administrator in one click whenever you need it. |
| Use “Run as different user” for domain-joined PCs |
Hold down Shift while right-clicking a shortcut, choose Run as different user, enter the domain admin credentials, and run your command. |
For more on user account best practices, see the National Institute of Standards and Technology (NIST) guide on least-privilege principles NIST.
