Cause: Windows Home edition or feature not enabled

Solution:

• Upgrade to Windows 10/11 Pro, Enterprise, or Education
• Or let SandboxStart enable it (requires admin and restart)

Cause: Hardware virtualization not enabled

Solution:

1. Enter BIOS/UEFI (usually Del, F2, or F12 during boot)
2. Find virtualization settings (Intel VT-x / AMD-V)
3. Enable virtualization
4. Save and exit
5. Try installing Windows Sandbox again

Check:

• Virtualization is enabled in BIOS
• Windows Sandbox feature is fully installed (may need restart)
• No other sandboxes are running

• Check Verbose mode to see errors
• Verify script syntax is valid PowerShell
• Ensure $SandboxFolderName is used (not hardcoded folder names)

Check wsb\script-mappings.txt:

• Patterns are matched top to bottom (first match wins)
• More specific patterns should be at the top
• *.* catches everything (should be last)

• Check networking is enabled
• Try "Clean (cached dependencies)"
• Try specifying a specific WinGet version
• Check internet connection

• Verify package IDs are correct (use winget search)
• Check networking is enabled
• Ensure list file is in wsb\ folder
• Remove comment-only lines

• Check file has .txt extension
• Verify file is in wsb\ directory
• Check wsb\sandboxtest-config.ini under [Lists] section - should be ListName=1 not 0
• Restart SandboxStart

• Check wsb\AutoInstall.txt exists and has package IDs
• Ensure networking is enabled
• File must have actual package IDs (not just comments)

Can't delete:

• AutoInstall (special list)
• Empty selection
• [Create new list...]

• Ensure # CUSTOM OVERRIDE is the first line
• No spaces before the #
• Save with UTF-8 encoding
• Restart SandboxStart

Problem: Files with Swedish/international characters fail (Error 0x8007007b)

Solution:

• Scripts and .wsb files now use UTF-8 encoding automatically
• If you create custom scripts, save as UTF-8 with CRLF line endings
• Old versions used ASCII which broke international characters (fixed in recent releases)

• Check mapped folders are accessible
• Verify you have read access to source folder
• For read-only issues, uncheck R/O checkbox

• Check antivirus isn't blocking
• Run PowerShell as admin once
• Manually create shortcut if needed

Check Verbose in Runtime Options to:

• See detailed execution log
• View error messages
• Wait for keypress before window closes

Scripts are written to:

%LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\SandboxTest\

Check:

• SandboxTest.ps1 - The bootstrap script
• BoundParameterScript.ps1 - Combined pre-install + user script

Use "Clean (cached dependencies)" to clear:

• Cached WinGet files
• Cached dependencies
• GitHub API cache
• Bootstrap scripts

1. Try Verbose mode first
2. Check this page for similar issues
3. See the FAQ
4. Open an issue on GitHub