windows 11 won't boot

%3CLINGO-SUB%20id%3D%22lingo-sub-2963234%22%20slang%3D%22en-US%22%3Ewindows%2011%20won't%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2963234%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I'm%20running%20Windows%2011%20a%20clean%20install%20everytime%20I%20tried%20to%20turn%20windows%20feature%20(virtual%20machine)%20on%20after%20restart%20it%20wont%20boot.%3CBR%20%2F%3Eother%20than%20that%20on%20task%20manager%20virtualization%20is%20shown%20as%20enabled%2C%20afterward%20I%20tried%20installing%20kaspersky%20but%20it%20show%20that%20virtualization%20isn't%20enabled.%20anybody%20can%20help%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2963234%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConfiguration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFeatures%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2963581%22%20slang%3D%22en-US%22%3ERe%3A%20windows%2011%20won't%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2963581%22%20slang%3D%22en-US%22%3EYou%20mentioned%20Windows%20is%20not%20boot%20up%2C%20so%20what%20error%20is%20being%20displayed%3F%3CBR%20%2F%3ECheck%20with%20your%20device's%20manufacturer%20support.%3C%2FLINGO-BODY%3E
New Contributor

Hi, I'm running Windows 11 a clean install everytime I tried to turn windows feature (virtual machine) on after restart it wont boot.
other than that on task manager virtualization is shown as enabled, afterward I tried installing kaspersky but it show that virtualization isn't enabled. anybody can help ?

5 Replies
You mentioned Windows is not boot up, so what error is being displayed?
Check with your device's manufacturer support.
Check if enabling virtualization under BIOS helps you to resolve this issue,
it just stuck on windows logo
I'm running win 11 on
Ryzen 5 5600x
gigabyte B550M-DS3H
16gb RAM
GTX 1070ti
it's enabled since I'm using AMD it's SVM
checked under task manager virtualization is enabled
under system info enabled too
Check with your device's manufacturer support.
Make sure report this issue using the Feedback Hub app.