WSL2 not starting despite Hyper-V and virtualization being enabled

[WalshyDev]

Background: I used to run WSL1 & WSL2 perfectly fine, I had to disable Hyper-V along with WSL a little bit ago. Ever since I disabled them in the past I haven't been able to enable everything properly again. Hyper-V features on enabled and services running, Virtualization is enabled in BIOS but yet... I cannot start WSL.

No hardware changes or anything else significant between the last time it worked and now.

Please fill out the below information:

• Microsoft Windows [Version 10.0.19025.1051]

• What you're doing and what's happening:

C:\WINDOWS\system32>wsl
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install

• What's wrong / what should be happening instead:
  It should just go into my WSL2 VM, it is instead just spitting out: Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.

wsl -l -v output:

C:\Users\Walshy\wsl-report>wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2
  Debian    Stopped         1

Images of features, services and virtualization in task manager

Features:

Services:

Task Manager showing Virtualization enabled:

• Strace of the failing command, if applicable:

C:\Users\Walshy\wsl-report>strace wsl -d Ubuntu
--- Process 12808 created
--- Process 12808 loaded C:\Windows\System32\ntdll.dll at 00007ffa89ab0000
--- Process 12808 loaded C:\Windows\System32\kernel32.dll at 00007ffa88b80000
--- Process 12808 loaded C:\Windows\System32\KernelBase.dll at 00007ffa87610000
--- Process 12808 loaded C:\Windows\System32\ucrtbase.dll at 00007ffa878e0000
--- Process 12808 thread 14612 created
--- Process 12808 loaded C:\Windows\System32\SHCore.dll at 00007ffa88cc0000
--- Process 12808 loaded C:\Windows\System32\msvcrt.dll at 00007ffa88d80000
--- Process 12808 loaded C:\Windows\System32\combase.dll at 00007ffa87b30000
--- Process 12808 loaded C:\Windows\System32\rpcrt4.dll at 00007ffa88330000
--- Process 12808 thread 13688 created
--- Process 12808 loaded C:\Windows\System32\ws2_32.dll at 00007ffa89840000
--- Process 12808 loaded C:\Windows\System32\kernel.appcore.dll at 00007ffa85b40000
--- Process 12808 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffa87380000
--- Process 12808 loaded C:\Windows\System32\sechost.dll at 00007ffa899d0000
--- Process 12808 loaded C:\Windows\System32\clbcatq.dll at 00007ffa89550000
--- Process 12808 thread 4416 created
--- Process 12808 thread 4616 created
--- Process 12808 thread 17776 created
--- Process 12808 loaded C:\Windows\System32\lxss\LxssManagerProxyStub.dll at 00007ffa7a100000
--- Process 12808, exception e06d7363 at 00007ffa87645a29
--- Process 12808 unloaded DLL at 00007ffa7a100000
--- Process 12808, exception e06d7363 at 00007ffa87645a29
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install
--- Process 12808 thread 14612 exited with status 0xffffffff
--- Process 12808 thread 13688 exited with status 0xffffffff
--- Process 12808 thread 4416 exited with status 0xffffffff
--- Process 12808 thread 4616 exited with status 0xffffffff
--- Process 12808 thread 17776 exited with status 0xffffffff
--- Process 12808 exited with status 0xffffffff

• I have attached the logman details (Started before running wsl and stopped after it failed):
  wsl-report.zip

[ghost]

Just to be sure, you do have the feature "Virtual Machine Platform" enabled, as in this picture?

[ad-on-is]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

[WalshyDev]

@DropNib Yep, check the summary under wsl -l -v output and above the strace output.

@ad-on-is Yep, already tried with no success.

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume5
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-GB
inherit                 {globalsettings}
flightsigning           Yes
default                 {current}
resumeobject            {fa62a036-d7e2-11e9-8624-8aedbab3624a}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 0

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-GB
inherit                 {bootloadersettings}
recoverysequence        {3f7b4696-0c00-11ea-b600-ebdd96078e40}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {fa62a036-d7e2-11e9-8624-8aedbab3624a}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

[ad-on-is]

Stupid question, but, did you reboot Windows after enabling everything? 😅

[WalshyDev]

@ad-on-is Oh yes. There's been many many reboots during the process of trying to fix this over the last month. Even rebooted since last night when I posted this but yeah... nothing :/

[Gareth001]

I was having this same problem. I disabled AMD SVM, booted, then re-enabled AMD SVM and it worked again. Hope this helps

[Hambugers]

I got the same problem,now I can only use wsl1.

[onomatopellan]

First of all, if you are in Windows 10 Pro try to run an hyper-v VM or launch Windows Sandbox. If those don't work either then the problem is in hyper-v.

[singhdharmveer311]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

So, It is not possible to use VM and WSL2 at same time?

[benhillis]

@moriarity9211 - VMware Workstation 15.5 supports it.

https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html

[ravesonly]

@benhillis
How it's going to help on original issue, did anyone solved this original issue in Win 10 home edition successfully? Can you please elaborate valid steps?
Thanks in advance!

[soccerdude288]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Mine was working fine till I started up an Android Studio Emulator last week. Since then I've been fighting to try and get wsl2 working again. BIOS was good, features were turned on, but no dice.

Finally tried the command above with a reboot and it worked!

[singhdharmveer311]

It works for me after update. I tried both bcdebit /set hypervisorlaunchtype auto & off it works but i have to restart my pc every time to update setting. After update it is working fine.

[benhillis]

VMWare Workstation 15.5.5 Pro supports using the Microsoft Hypervisor Platform APIS. You will need to be running that version or later.

WSL2 requires the "Virtual Machine Platform" optional component which is available on all SKUs.

[johannfenech]

This fixed it for me https://blog.johannfenech.com/fix-wslregisterdistribution-failed-with-error-0x80370102/

It took me days and two formats to figure out !

[kubichris]

Did you try bcdedit /set hypervisorlaunchtype auto
I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Mine was working fine till I started up an Android Studio Emulator last week. Since then I've been fighting to try and get wsl2 working again. BIOS was good, features were turned on, but no dice.

Finally tried the command above with a reboot and it worked!

Yes, it work for wsl, but doesn't good for VirtualBox.

WSL : bcdedit /set hypervisorlaunchtype auto + RESTART
VirtualBox: bcdedit /set hypervisorlaunchtype off + RESTART

[parikshit90900]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Mine worked after this command

wsl doesn't work with other software using virtualization
I installed Andy Android Emulator and then this error code '0x80370102' appeared
maybe some VMs changes the windows features and wsl don't work after that

[ZayenJS]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

I was having the same problem, this worked great, thanks a lot !

[mrivard]

@WalshyDev, at 2:58 in, this YouTuber says to not enable Windows Hypervisor Platform when adding WSL2. He doesn't say why, though.

[feland207]

Did you try bcdedit /set hypervisorlaunchtype auto
I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

So, It is not possible to use VM and WSL2 at same time?

I quote this question. Is any way to have both WSL2 and VM ?

[yiqiangjizhang]

Did you try bcdedit /set hypervisorlaunchtype auto
I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

So, It is not possible to use VM and WSL2 at same time?

I quote this question. Is any way to have both WSL2 and VM ?

I quote this reply as well, I want to have both WSL and VM working, is this possible? Thanks to all community for helping out!

[zhangxj19]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

It really works if you ever tried android emulator.

[yiqiangjizhang]

Did you try bcdedit /set hypervisorlaunchtype auto
I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.
It really works if you ever tried android emulator.

Yeah it worked finally!

I used:

Activate VirtualBox (Disable Hyper-V):
bcdedit /set hypervisorlaunchtype off

Activate WSL (Enable Hyper-V):
bcdedit /set hypervisorlaunchtype auto

to enable and disable Hyper V so I can run WSL or VM. However, the PC needs restart

[Soromeister]

I have Hyper-V, Virtual Machine Platform and all the required features enabled, but this still doesn't work for me even after setting the bcd entry to auto.

[geekyshubham]

bcdedit /set hypervisorlaunchtype auto

oops i did something similar. Thanks It worked.

[Kenttleton]

I had a similar issue after an upgrade on the dev channel to Windows 10.0.22000 (Windows 11) Pro. Having the Windows features Windows Subsystem for Linux and Virtual Machine Platform checked and Hyper-V unchecked allowed me to run VirtualBox and WSL2 at the same time. I also needed to bcdedit /set hypervisorlaunchtype auto as this was set to off during the upgrade likely causing my issue.

[ElCosmoXD]

I have the same issue, I have all the required features enabled (with the virtualization enabled in the BIOS). I don't have any emulator like the Android simulator, VMware, VirtualBox or anything like that. I tried everything but nothing solves this issue.

[husniadil]

Had no problem last week. But this is now happening to me. I didn't touch anything about the VirtualMachinePlatform. I didn't touch any BIOS settings. I'm relying on WSL2 for my work and now suddenly not working

I tried:

• reinstall WSL via Turn on/off features
• run dism thingy to disable and enable WSL2 and Virtual Machine Platform
• disable + re-enable the VT-d and Intel Vietualization Technology
• run bcedit thingy to auto, and off as well
• enable / disable hypervisor
• uninstall docker desktop
• uninstall windows subsystem for android
• reset network adapters
• reset winsock
• restart the computer many times
• check windows event viewer: no error related to wsl
• subscribe to beta channel

Nothing worked for me.

[fellipec]

I got so frustrated today that I did the same. I'm in the process of reinstall the things. But before I choose to format the PC, , I was suspecting spacedesk too, but I just disabled it, and did not restart too, and dismissed because it worked before.
I'll not install that again.

wait, when you said you "disabled spacedesk", did you mean you uninstalled it and did not restart because I uninstalled it and restarted my pc but it is still not working.

No, I just disabled the driver in the main window. I have no screenshots and I'll not install it again to do one, sorry.
If you fully uninstalled, reboot and sfc /scannow it don't fix the issue, MAYBE it have a rootkit-like behavior of some sorts.
As far as I know what we have in common here is having installed Spacedesk before our WSL2/Hypervisor gone corrupted.
Also, I couldn't use VMWare too before formatting my machine.

[daniel-iroka]

I got so frustrated today that I did the same. I'm in the process of reinstall the things. But before I choose to format the PC, , I was suspecting spacedesk too, but I just disabled it, and did not restart too, and dismissed because it worked before.
I'll not install that again.

wait, when you said you "disabled spacedesk", did you mean you uninstalled it and did not restart because I uninstalled it and restarted my pc but it is still not working.

I read that about spacedesk just now. i updated it recently and then wsl2 stopped working. I updated like 10 programs in the same time so I didnt really suspeted that spacedesk maybe have something to do with wsl failing. But I guess thats an important clue, spacedesk is intefering with wsl / virtualisation on windows.

@daniel-iroka I would suggest you the update installation with the MediaCreationTool. It reinstalled windows and after 30 min my ubuntu distro ran again.... iam so happy, but also sad about 2 days of lost time, because of such an ackward bug

I have few more questions please. What about the normal settings update as well? Will that also work and will I also loose data if i update through the media tool?? Also, how will I know what media tool link to follow can you help me with a link please. My OS buid is 19043

[husniadil]

Re-installing Windows with "Keep my personal files" settings worked for me.

I you uninstall spacedesk using spacedesk installer before re-installing Windows, the driver will not be brought back to your new Windows installation.

But if you don't uninstall spacedesk, Windows will still bring spacedesk over your new Windows installation, BUT somehow they work together (WSL and spacedesk), then again don't use the spacedesk installer to install it again.

[daniel-iroka]

Re-installing Windows with "Keep my personal files" settings worked for me.

I you uninstall spacedesk using spacedesk installer before re-installing Windows, the driver will not be brought back to your new Windows installation.

But if you don't uninstall spacedesk, Windows will still bring spacedesk over your new Windows installation, BUT somehow they work together (WSL and spacedesk), then again don't use the spacedesk installer to install it again.

Okay. Thank you

[yangmeishu]

Finally it fixed it for me by doing an update installation "keep my personal files and programs" through the MediaCreationTool. Wsl (and Windows sandbox) is finally working again.

One tip for anyone wondering about the output of the Intel® Processor Identification Utility. It still shows for me an X (for not enabled) for Intel Virtualisation Technology and EPT/SLAT support. But my wsl2 and Windows sandbox is working fine. (i5-10600k)

This problem bothers me too much time and energy. Before I saw this post, I had no reason to connect the two software wsl and spacedesk. Similarly, I also installed spacedesk on my computer, and it was updated recently. Finally see your operation. The problem is solved

[daniel-iroka]

Finally it fixed it for me by doing an update installation "keep my personal files and programs" through the MediaCreationTool. Wsl (and Windows sandbox) is finally working again.
One tip for anyone wondering about the output of the Intel® Processor Identification Utility. It still shows for me an X (for not enabled) for Intel Virtualisation Technology and EPT/SLAT support. But my wsl2 and Windows sandbox is working fine. (i5-10600k)

This problem bothers me too much time and energy. Before I saw this post, I had no reason to connect the two software wsl and spacedesk. Similarly, I also installed spacedesk on my computer, and it was updated recently. Finally see your operation. The problem is solved

wait, so you mean that spacedesk is now working well with wsl??

[yangmeishu]

No, if spacedesk is installed, wsl cannot be started. It can be repaired according to your method. After reinstalling the system, wsl and spacedesk coexist

[daniel-iroka]

No, if spacedesk is installed, wsl cannot be started. It can be repaired according to your method. After reinstalling the system, wsl and spacedesk coexist

Oh that's nice. I uninstalled spacedesk though because I was told wsl won't still work if I reinstall it with windows

[yangmeishu]

l

Without uninstalling spacedesk, after reinstalling windows, it can be used normally. But I think it would be better to use a lower version of spacedesk

[grzegorztomasiak]

+1
I am also looking for a solution. After installing spacedesk, wsl stopped working and re-enabling it does not do anything.

[Nachtalb]

There is a thread open over at the spacedesk forum referencing this thread here so for cross reference sake: https://www.spacedesk.net/de/forums/topic/wsl2-not-starting-after-spacedesk-installation/

If any of you have more information about this that could help the spacedesk guys, please tell them :)

[DamienGdn]

I found this.
Wsl is not started because Hyper V service is not started and I can't started manually this.
I Try to install an old version but Wsl don't start.

[Lyndonpett]

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆

The software school I go to was troubleshooting a student's issue with virtualization saying it was disabled when trying to run Ubuntu on WSL and would fail saying virtualization was not enabled, even though it was showing in task manager and other ways we verified it was enabled. When we ran bcdedit we found that hypervisionlaunchtype was set to off by default. We solved the issue by setting it to auto and restarting. This is the answer!

[Nachtalb]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

[sith-lord-vader]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

This surely works mates. Saved my life. Had this problem in past. Did a clean install of Windows several times but this problem used to come back. But this saved me.

[ElCosmoXD]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

I tested this and it solved the problem, Thanks.

[yasharya2901]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

Thanks, this really worked for me. Now I can use WSL without any problems.

[Gauravkumar2701]

This bcdedit /set hypervisorlaunchtype auto is not working in windows 11

Showing the below error -

The boot configuration data store could not be opened.
The system cannot find the file specified.

[kvnyng]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

This surely works mates. Saved my life. Had this problem in past. Did a clean install of Windows several times but this problem used to come back. But this saved me.

BTW this solution references this forum .

After installing "microsoft hyper-v virtualization infrastructure driver" from the legacy hardware wizard, it gave me an error that it the infrastrucutre driver could not start.

To fix this, I followed what one of the forum users posted:

In my situation,
– After reinstall the microsoft hyper-v virtualization infrastructure driver,
– In the device manager list, it still shows that there is a problem with this driver，
– Then i uninstall it in the device manager, After automatic reinstallation

Hopes this helps!

Credit to Spacedesk forum user Aiken

[ReactiveSlime]

Found on the spacedeak forums and worked for me

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

[tijko]

I was having this same problem. I disabled AMD SVM, booted, then re-enabled AMD SVM and it worked again. Hope this helps

I don't feel great pointing to this but this is exactly what I did and it fixed the issue.

Between Microsoft, Docker, and the OEM the group most likely needs some collaborative debugging.

[tijko]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.

It seems as if the problem could be solved by manually re-installing this driver.

Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.

2. Choose Option „Select hardware manual from list“ in the wizard

3. Choose „Systemdevices“ in the list

4. Choose „Microsoft“ in vendors

5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models

6. Follow the wizard to finish the installation

7. Restart the computer

Thanks, this really worked for me. Now I can use WSL without any problems.

I haven't had a chance to do a test with this fix but I can say that I have been able to switch it off (actually off) in the "virtualization" section in the UEFI for a Dell XPS I have.

While not ideal, this exact situation has occurred on two identical but separate laptops for my employer. After turning off the WSL feature both laptops (same Windows 10 Enterprise versions) will then incorrectly report that the VMM instruction set are not enabled. Going into UEFI, as I said, turning it off properly->reboot->shutdown->re-enable-> all is working as before.

[github-wow]

WSL : bcdedit /set hypervisorlaunchtype auto + RESTART
VirtualBox: bcdedit /set hypervisorlaunchtype off + RESTART

worked for me

[LynxTR]

After uninstalling spacedesk and rebooting, wsl seems like working again!

[LeonBraga]

I was having this same problem. I disabled AMD SVM, booted, then re-enabled AMD SVM and it worked again. Hope this helps

I was with the same problem! Doing this fixed it for me, thank you very much @Gareth001

[ddimick]

I was having this same problem. I disabled AMD SVM, booted, then re-enabled AMD SVM and it worked again. Hope this helps

I have been beating my head against this wall for a long time, and this did the trick.

[elevenTrue]

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can't try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver.
It seems as if the problem could be solved by manually re-installing this driver.
Please try the fix below and let us know if it solved the problem.

1. Go to device manager -> Action -> add legacy hardware.
2. Choose Option „Select hardware manual from list“ in the wizard
3. Choose „Systemdevices“ in the list
4. Choose „Microsoft“ in vendors
5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
6. Follow the wizard to finish the installation
7. Restart the computer

Thank you very much. I installed spacedesk to cause this problem. It seems that you can't install software randomly