Documentation Index
Fetch the complete documentation index at: https://jarvisos.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Troubleshooting Guide
Installation Issues
AME Wizard fails at a specific task with an error
AME Wizard fails at a specific task with an error
Most common causes:
- Defender / Tamper Protection still on — disable both in Windows Security before running
- Third-party antivirus running — disable or uninstall it completely before the playbook run
- Windows Updates not fully applied — install all pending updates and reboot before running AME
Registry FormatException errors in the log
Registry FormatException errors in the log
This occurs if registry values are in an unexpected format. JarvisOS v30.05.26 normalizes all REG_DWORD values to decimal format to prevent this.If you see this error, ensure you are using the latest release:
JarvisOS_30.05.26.apbx.w32tm / time sync not working after install
w32tm / time sync not working after install
The Windows Time service (This was fixed in v30.05.26 with an explicit service start action in the build.
w32tm) requires an explicit start after some configurations. Run:svchost.exe errors immediately after playbook completes
svchost.exe errors immediately after playbook completes
These are transient memory violations that occur during the first boot after mass service deletion — SvcHost is merging process groups mid-restart.Fix: Simply restart the machine. The errors are self-resolving and do not indicate a corrupted install.
Browser Issues
Zen Browser install failed
Zen Browser install failed
Zen Browser uses a GitHub release as its download source. If the installer fails, download it manually from the Zen Browser GitHub releases page and run
zen.installer.exe directly.Browser not set as default
Browser not set as default
After install, Windows may still reference Edge (even though it is removed). Set your default browser:Or right-click any
.html file → Open with → Choose another app → your browser → set as default.Developer Tool Issues
WSL2 not working / can't install a distro
WSL2 not working / can't install a distro
Verify Hyper-V and Virtual Machine Platform are enabled:Reboot after enabling. Then:
WinGet is not found / not working
WinGet is not found / not working
WinGet is preserved by JarvisOS. If it is not found in PATH:
VS Code extensions not installing (marketplace errors)
VS Code extensions not installing (marketplace errors)
VS Code’s extension marketplace requires internet access. Verify your network connection and DNS resolution:If DNS fails, the network stack may not be fully initialized. Restart and try again, or manually configure your preferred DNS (1.1.1.1 or 9.9.9.9) in Network Settings.
System Tools Issues
AtlasOS Toolbox won't launch
AtlasOS Toolbox won't launch
Ensure the AtlasDesktop files are in place:If these paths don’t exist, the maintenance tools were not installed. Re-run the
INSTALL_MAINTENANCE_TOOLS.bat from C:\Program Files\JarvisOS Tools\.Printer not working
Printer not working
The Print Spooler is disabled by default. Enable it:Or via Services (
services.msc): find Print Spooler → Start → set Startup Type to Manual.Disable again when done printing:Windows Time / Clock is wrong
Windows Time / Clock is wrong
Still Stuck?
Open a GitHub Issue with:- Your Windows 11 build number (
winver) - JarvisOS version (e.g.,
30.05.26) - The full error message or log from AME Wizard
- What you were doing when the issue occurred
