sodcalculator

10 Tech How-To

Fix Windows Sandbox Error 0x80070005 Access Denied

Guide 10-53528 · Updated · Step by step

Windows Sandbox gives you a clean, isolated desktop to test software safely, but the 0x80070005 (Access Denied) error stops it from launching. This usually happens when the Sandbox service lacks proper permissions or virtualization features are misconfigured. Below are the exact steps to restore access and get Sandbox running again.

What You’ll Need

  • Administrator account on the Windows PC
  • Access to Windows Settings and Command Prompt (or PowerShell)
  • Virtualization enabled in BIOS/UEFI (check if unsure)
  • Stable internet connection for Windows updates (if needed)

Step-by-Step

  1. Check if Windows Sandbox is enabled. Press Win + R, type optionalfeatures.exe, and hit Enter. In the Windows Features window, make sure Windows Sandbox is checked. If it isn’t, check it, click OK, and restart when prompted.
  2. Enable required virtualization features. In the same Windows Features list, ensure Virtual Machine Platform and Windows Hypervisor Platform are also checked. If they were off, enable them and restart.
  3. Verify virtualization is active in BIOS/UEFI. Restart your PC and enter BIOS/UEFI (usually by pressing Del, F2, or F10 during boot). Look for a setting named Intel VT-x, AMD-V, or SVM Mode and ensure it is enabled. Save and exit.
  4. Run the Sandbox as administrator. Right-click the Windows Sandbox shortcut (or the executable C:\Windows\System32\WindowsSandbox.exe) and select Run as administrator. This often bypasses permission issues.
  5. Check the Sandbox service permissions. Press Win + R, type services.msc, and press Enter. Find Windows Sandbox in the list. Right-click it, select Properties, and ensure the Startup type is set to Manual or Automatic. Click Start if it isn’t running, then apply and OK.
  6. Repair the Sandbox via PowerShell. Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin). Run the following command and wait for it to finish:
    Get-AppxPackage Microsoft.WindowsSandbox | Reset-AppxPackage
    This resets the app’s data without uninstalling it.
  7. Re-register the Sandbox package. In the same admin PowerShell or Terminal, run:
    Add-AppxPackage -Register "C:\Windows\System32\WindowsSandbox.dll" -DisableDevelopmentMode
    If the path is incorrect, replace it with the actual location of the Sandbox package.
  8. Check Group Policy settings. Press Win + R, type gpedit.msc, and press Enter. Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Sandbox. Double-click Allow Windows Sandbox and set it to Enabled. Click OK.
  9. Create a new user profile. If the error persists, the current user profile may be corrupted. Create a new local administrator account (Settings > Accounts > Family & other users > Add someone else to this PC) and try launching Sandbox from that account.
  10. Perform a Windows Update. Go to Settings > Windows Update and click Check for updates. Install all pending updates, especially cumulative updates, and restart.

Common Mistakes

  • Skipping the restart after enabling features. Windows Sandbox requires a full restart for virtualization features to take effect.
  • Forgetting to check BIOS virtualization. Even if Windows features are enabled, the CPU must have VT-x/AMD-V turned on in BIOS.
  • Running the wrong PowerShell command. The Reset-AppxPackage command only works if the Sandbox app is installed correctly; otherwise it throws an error.
  • Ignoring Group Policy. On some systems, a policy disables Sandbox entirely, overriding local settings.
  • Not using an administrator account. The error 0x80070005 specifically indicates a permission issue, so non-admin accounts will often fail.

Tips

  • Always run Windows Sandbox as administrator to avoid permission hiccups.
  • Keep your Windows installation up to date; many Sandbox issues are fixed in cumulative updates.
  • If you use third-party antivirus, temporarily disable its real-time protection to see if it’s blocking Sandbox (re-enable it after testing).
  • Use the sfc /scannow command in an admin Command Prompt to repair system files that might be causing the error.
  • Check the Windows Event Viewer (under Windows Logs > System) for errors related to Sandbox to get more specific clues.

Troubleshooting

If the steps above don’t resolve the issue, try these additional checks:

  • Verify Hyper-V is installed. Windows Sandbox relies on Hyper-V. Open Turn Windows features on or off and ensure Hyper-V is checked. If it isn’t, enable it and restart.
  • Check if your CPU supports virtualization. Download a tool like Coreinfo (from Microsoft) or check Task Manager > Performance > CPU. If virtualization shows Disabled, you must enable it in BIOS.
  • Reset Windows Sandbox via Settings. Go to Settings > Apps > Installed apps, find Windows Sandbox, click the three dots, and select Advanced options. Then click Reset.
  • Use DISM to repair system image. In an admin Command Prompt, run:
    DISM /Online /Cleanup-Image /RestoreHealth
    Then run sfc /scannow again.
  • Check if Sandbox is blocked by a policy. If you’re on a work or school PC, the IT department may have disabled Sandbox via policy. Contact them for assistance.
  • Try a clean boot. Disable all non-Microsoft services and startup items (using msconfig) to rule out software conflicts.

Frequently Asked Questions

Why does Windows Sandbox give an Access Denied error?

The error 0x80070005 typically means the Sandbox service lacks the necessary permissions to create a virtual environment. This can be due to disabled virtualization, missing Windows features, or a corrupted user profile.

Do I need Hyper-V to use Windows Sandbox?

Yes, Windows Sandbox uses Hyper-V technology. You need to have Hyper-V and the Virtual Machine Platform enabled, and your CPU must support virtualization.

Can I fix this without admin rights?

No, most fixes require administrator privileges. You’ll need to log in with an admin account or ask your system administrator for help.

Will resetting Windows Sandbox delete my files?

No, Windows Sandbox is a temporary environment that doesn’t store personal files. Resetting it only clears the Sandbox’s own data, not your main system files.

Does this error occur on Windows 10 and Windows 11?

Yes, the 0x80070005 error can appear on both Windows 10 and Windows 11. The steps to fix it are essentially the same, though some menu locations may differ slightly.

What if I still get the error after trying all steps?

If the error persists, you may have a deeper system issue. Try performing a system restore to a point before the problem started, or consider using an alternative like a virtual machine (VMware, VirtualBox) if Sandbox is not critical.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →