Skip to main content

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.

Frequently Asked Questions


Installation

JarvisOS v30.05.26 supports the following Windows 11 builds:
  • 22000 (21H2)
  • 22621 (22H2)
  • 22631 (23H2)
  • 26100 (24H2)
  • 26200
  • 27686
Always start from a clean, unmodified Windows install. Do not apply JarvisOS on top of an existing tweaked system.
Technically yes — AME Wizard can run on an existing install. But it is strongly recommended to start from a fresh Windows installation for a predictable, clean result.Any third-party tweaks, debloat scripts, or registry modifications already present will conflict with AME’s configuration and may cause instability.
This means you may have an older version of the playbook. Download the latest JarvisOS_30.05.26.apbx from GitHub Releases.The current build uses Privacy+ style DependsOn linking which forces the full-screen selection flow in AME Wizard.
If the system force-shut down during the mitigation phase, your Windows install may be in an inconsistent state. The safest path is a clean reinstall.Do not attempt to resume or repair the AME process mid-run.

Apps & Software

Removed. The Microsoft Store and its background Appx infrastructure are a significant telemetry vector — so it is purged during installation.Use App Fetch to sideload any UWP app you need:
app-fetch install <URL_or_local_path>
For most software, WinGet is the better option and is fully preserved in JarvisOS:
winget install <PackageName>
Removed. Your selected browser (Brave, LibreWolf, or Zen Browser) is installed instead during the playbook run.Edge cannot be easily reinstalled on a JarvisOS system and is not supported.
All removed. OneDrive, Microsoft Teams, Xbox, Game Bar, Cortana, and all consumer Microsoft apps are uninstalled during the playbook run. They will not be reinstalled by Windows Update in this configuration.
Yes — all three are explicitly preserved in JarvisOS. They are protected from the service and component removal passes.Verify WSL2 is active after install:
wsl --list --verbose
If no distribution is installed yet:
wsl --install -d Ubuntu

Updates & Security

Use the AtlasOS Toolbox (on your desktop):
  1. Open AtlasOS Toolbox → Windows Update → Enable
  2. Run Windows Update and install security patches
  3. Windows Update → Disable when done
Do not use the Windows Settings app to manage updates — it will not respect JarvisOS’s configuration.
If Windows Update is left enabled long-term, yes — Microsoft may push updates that attempt to restore Edge, OneDrive, or telemetry services.This is why JarvisOS suppresses automatic updates. Patch on your schedule, then disable.
Yes, by default. JarvisOS leaves Defender enabled — removing it requires trusting your entire software supply chain.If you want to disable it:
ame-settings-cli set defender --state off
The playbook also includes an optional Defender removal checkbox during install (unchecked by default).

Developer Tools

These are optional checkboxes during install — all checked by default, but if you unchecked them, they were not installed.You can install them manually via WinGet:
winget install Git.Git
winget install Microsoft.VisualStudioCode
winget install OpenJS.NodeJS.LTS
Yes. Hyper-V and WSL2 are both preserved, so Docker Desktop works normally.Install via WinGet:
winget install Docker.DockerDesktop