HYPERVISOR_ERROR (0x00020001) means the hypervisor encountered a fatal error. It does not mean Hyper-V must be installed.
Since bootrec /scanos, bootrec /rebuildbcd, bootrec /fixmbr, and bootrec /fixboot let Windows start again, the immediate boot issue is consistent with recovery steps for boot configuration problems. If the system later falls back to recovery again, installing Hyper-V is not the recommended fix.
Try this path:
- Do not install Hyper-V just to fix this error.
The stop code indicates a hypervisor failure, but the available guidance does not say that installing Hyper-V resolves it. - If the PC is back in Recovery, repeat the WinRE command path only as a recovery step:
Troubleshoot > Advanced options > Command Prompt
Then run:-
bootrec /scanos -
bootrec /rebuildbcd -
bootrec /fixmbr -
bootrec /fixboot
-
- After Windows starts, install the latest Windows updates.
Go to Start > Settings > Update & Security > Windows Update > Check for Windows updates. - If the problem keeps returning, use the standard blue-screen checks:
- Remove any newly added hardware.
- Start in Safe Mode if normal boot is unreliable.
- Open Device Manager and check for devices with an exclamation mark; update, disable, or uninstall the affected device if needed.
- Make sure the system drive has enough free space; 10% to 15% free space is a good target.
- If Windows still fails to start repeatedly, use recovery options.
The documented next step is to use Windows recovery options or system restore if the basic troubleshooting does not help. - Do not edit the registry as a workaround.
That is specifically warned against for restart/setup-related issues because it can cause later problems.
About the SrtTrail.txt message: the context only shows that bootrec commands are used from recovery when Windows is stuck on recovery/BCD-related startup problems. It does not identify SrtTrail.txt itself as the root cause.
If the same stop code continues after updates and recovery steps, the supported guidance is to continue with Windows blue-screen troubleshooting and recovery rather than enabling Hyper-V.
References: