this post was submitted on 19 Jul 2023
6 points (80.0% liked)

Linux

48313 readers
932 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I'm trying to run Windows 10 on a virtual machine, but every ISO I launch shows me a blue screen with an error: system thread exception not handled

I'm using Arch and my specs are: AMD Ryzen 7 1700x, ROG STRIX B550-E GAMING

LC_ALL=c lscpu | grep Virtualization Virtualization: AMD-V

I read archwiki and it says: "On KVM machines this issue can generally be solved by setting the CPU model to core2duo." I selected the Conroe model, which is a codename for a core2duo, and now I can see the Windows logo, but the VM instantly closes to a default black screen.

top 5 comments
sorted by: hot top controversial new old
[–] dark_stang@beehaw.org 7 points 1 year ago

You may need to turn on virtualization support in your BIOS for the CPU. That's often disabled by default.

[–] CrabAndBroom@lemmy.ml 1 points 1 year ago

You could try something like QuickEmu which does all the setup stuff for you. I haven't tried it with Windows yet but it worked for me to get a Mac VM up and running pretty easily.

[–] NoRecognition84@lemmy.world 1 points 1 year ago (1 children)

Check your bios and make sure SVM is enabled

[–] ProgKing@lemmy.ml 1 points 1 year ago

It's enabled

Try re-creating the VM from scratch but keep the virtual HD. Sometimes this fixes similar issues. At least you don't have to worry about TPM2 emulation with Windows 10. That's a big positive.