Troubleshooting OS updates
How to reason about a release that downloaded but did not activate, a bad pending slot or a rollback.
referencestatus
Operators · OS developersaudience
School-GIT docssource
SCHX nativeruntime
SCHX / FEATURE LAYER
Source map
- lib/cdn/os/client-os-bootstrap.ts
- lib/cdn/os/client-os-updater.ts
SCHX / FEATURE LAYER
Installed but not active
This is expected before restart. Confirm the release exists in the version slot and pending-version points to it. The active version should still report the currently running OS.
SCHX / FEATURE LAYER
Pending release rolls back
Treat rollback as a startup failure signal. Check missing release files, manifest/runtime API mismatch, browser console exceptions, runtime READY timeout and hash verification failures.
SCHX / FEATURE LAYER
Source edit appeared instantly
If you are running Next development mode, HMR can still update source immediately. To test release isolation, boot the installed OS path and verify the active version slot rather than judging from the developer source shell.
SCHX / FEATURE LAYER