TechClassy
Tools

Windows Sandbox · reviewed 2026-09-01

Windows Sandbox 0x80370102 diagnostic

The requested virtualization environment could not start because required hypervisor or virtualization support was not available to Windows.

High for Sandbox launch failureNot confirmed until prerequisites and policy state are checked

Review the result here, then choose the context that matches what happened.

0 / 12,000 characters

Local processing · no upload

Ctrl/⌘ + Enter

Try a scenario
Resume a saved session — paste a Resume Capsule

The capsule is validated and restored only in this browser. An invalid capsule changes nothing.

Meaning & limits

What this diagnostic record establishes

Confirmed

  • The requested virtualization environment could not start because required hypervisor or virtualization support was not available to Windows.

Not confirmed

  • The code does not prove virtualization is disabled in firmware.
  • It does not justify changing BIOS, boot configuration, Hyper-V, or group policy before edition and feature state are confirmed.
Applicable versions
Windows 11 on a currently supported release; Windows 10 only where Microsoft or the device vendor still supports the installed edition
Review status
verified · 2026-09-01
Evidence still needed
Windows edition, version, and build; Sandbox feature state; Task Manager virtualization status; Managed-device policy message; Recent update or virtualization-product change

Context changes the route

What is the history of Sandbox on this PC?

Choose the context that matches your incident. These are alternatives, not a sequence of fixes. Follow only the matching check and keep its verification and rollback together.

Never worked on this PC

Likely layer: Windows feature, edition, virtualization, hypervisor, or policy

First safe check: Confirm prerequisites and policy state before changing firmware or Windows features

Expected: You will know whether the missing boundary is edition, feature state, virtualization availability, or managed policy.

Steps, verification and rollback
  1. Check whether the installed Windows edition supports Sandbox and whether the feature is present.
  2. Record Windows edition, version, and OS build; verify whether Windows Sandbox is listed in Windows Features.
  3. Open Task Manager → Performance → CPU and record whether Virtualization shows Enabled. Do not change BIOS settings from a generic guide.

Verify: Compare the same prerequisites with Microsoft's current Sandbox requirements before making any change.

Rollback: No system change is made by this check.

Link to Never worked on this PC check

Stopped after an update

Likely layer: Windows feature, edition, virtualization, hypervisor, or policy

First safe check: Confirm prerequisites and policy state before changing firmware or Windows features

Expected: You will know whether the missing boundary is edition, feature state, virtualization availability, or managed policy.

Steps, verification and rollback
  1. Record the update KB and whether Hyper-V, WSL, or another virtualization product also changed behavior.
  2. Record Windows edition, version, and OS build; verify whether Windows Sandbox is listed in Windows Features.
  3. Open Task Manager → Performance → CPU and record whether Virtualization shows Enabled. Do not change BIOS settings from a generic guide.

Verify: Compare the same prerequisites with Microsoft's current Sandbox requirements before making any change.

Rollback: No system change is made by this check.

Link to Stopped after an update check

Work or school device

Likely layer: Windows feature, edition, virtualization, hypervisor, or policy

First safe check: Confirm prerequisites and policy state before changing firmware or Windows features

Expected: You will know whether the missing boundary is edition, feature state, virtualization availability, or managed policy.

Steps, verification and rollback
  1. Check whether Windows displays an administrator or policy message; do not change policy-controlled features.
  2. Record Windows edition, version, and OS build; verify whether Windows Sandbox is listed in Windows Features.
  3. Open Task Manager → Performance → CPU and record whether Virtualization shows Enabled. Do not change BIOS settings from a generic guide.

Verify: Compare the same prerequisites with Microsoft's current Sandbox requirements before making any change.

Rollback: No system change is made by this check.

Link to Work or school device check

Before any second repair step

Verify the observation and preserve the evidence

After the first safe check, record whether the reviewed intermediate result occurred, whether the original problem was retested, and the exact output. An expected observation is not automatically a repair.

Outcome boundaries

  1. Observed as expected
  2. Observed something different
  3. Result unclear
  4. Could not complete the check

Then separately record whether the original problem still occurs, was not reproduced once, or has not been retested yet. Every session ends in stop, one repeat of the same check, one named missing fact, or escalation—never an open-ended repair sequence.

Evidence fields for this task

  • Windows version/buildExample: Windows 11 24H2, build 26100
  • Windows editionHome, Pro, Enterprise, Education…
  • Feature and virtualization stateSandbox feature, virtualization, hypervisor, or VM context
  • Managed-policy or exact error textExact message and whether this is a work/school device

The browser-local Evidence Pack combines the selected context, safe action, actual observation, sources, review date, missing evidence, and stop boundary. It can be copied or printed without creating an account or uploading a log.

After you perform the safe check

Read the evidence you collected

Paste a bounded msinfo32 or DxDiag text report and extract the Windows build, system model, firmware mode, memory, DirectX, display-driver, and explicitly reported problem-device facts without uploading the report.

Windows System Information Snapshot ReaderOne bounded excerpt · no upload · no root-cause ranking

Review trail

Official and first-party sources

Same task chain

0x80370106Windows Sandbox or virtualization stack could not start the virtual environment

Local-first utility

Privacy

The diagnostic parser, evidence readers, verification loop, and Evidence Pack run in your browser. TechClassy does not intentionally store the raw text you paste, Event Viewer or update-log excerpts, full command output, usernames, local file paths, dump files, device serial numbers, observations, parsed summaries, or generated Evidence Packs.

No advertising, analytics, session replay, account system, upload surface, or third-party diagnostic script is loaded in this release. Standard hosting security logs may contain request metadata such as time, requested path, and network information; diagnostic and evidence text is not sent as a URL parameter or API body by the tool.

Use boundary

TechClassy organizes evidence and reviewed next checks. It is not a substitute for Microsoft, an OEM, an employer's IT team, or a qualified repair professional. Results distinguish confirmed facts from possible causes and do not guarantee a repair.

Back up important data before making system changes. Stop when an action requires credentials, firmware changes, disk work, account recovery, or a command whose prerequisites you cannot verify.

Independent operation

This is a newly researched, independently operated diagnostic product. It does not claim to be the prior TechClassy editorial team or a continuation of prior authorship.

Open the permanent page