After the system blue screen, hyper-v cannot be started

ZHOU JIANWEN 21 Reputation points
2023-07-15T16:16:17.34+00:00

After the system blue screen, hyper-v cannot be started, wsl cannot be started normally, and all software based on hyper-v cannot be started

User's image

User's image

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,636 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2023-07-18T00:51:30.2433333+00:00

    this is because of a problem with Windows version 25905

    The product group for insider's builds actively monitors questions over at
    https://answers.microsoft.com/en-us/insider/forum
    https://techcommunity.microsoft.com/t5/windows-insider-program/bd-p/WindowsInsiderProgram

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-07-15T17:04:26.2166667+00:00

    Not much to go on but one option may be to copy the VHDs off to removeable, clean install the operating system, patch fully, install hyper-v role, create new VM based on existing VHDs and move on.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Anonymous
    2023-07-16T01:40:47.75+00:00

    BSOD generally happens because of hardware failure and or driver corruption. The server manufacturer will be your best resource to troubleshoot problems with your hardware.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Anonymous
    2023-07-16T11:52:05.51+00:00

    The simplest solution may be to copy the VHDs off to removeable, clean install the operating system, patch fully, install hyper-v role, create new VMs based on existing VHDs and move on.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  4. ZHOU JIANWEN 21 Reputation points
    2023-07-16T15:01:28.4766667+00:00

    I also tried to create a new virtual machine and use the windows installation image to install the system, but the same error still occurred when starting the virtual machine installation