I need to use a Windows VM to do a few things - I’m on Fedora and my Xbox controller has been glitching out a lot and I need to try updating the firmware. Also, I got a new RGB keyboard and I’m not able to use the proprietary software using Wine and OpenRGB does not support my keyboard (Cosmic Byte GK34 Firefly).
But when I try to install a Win 10 ISO it won’t let me past the Microsoft account page and the oobe command that’s suggested everywhere on reddit is not working. It says no such command found.
Windows 11 ISOs also aren’t working because even if I put 6GB memory and 80GB Storage for the VM (Microsoft lists 4GB and 64GB as requirement) it still says system does not meet requirement. I’m using the Boxes app for the VM creation.
As for w11 requirements, you also need a uefi, iirc. Here’s a random article on doing that: https://www.ctrl.blog/entry/how-to-win11-in-gnome-boxes.html
@fl42v @absurdity_of_it_all , what’s funny about the whole TPM2 requirements is that I disable Bitlocker in my VM anyways, which I do since my Linux hosts always have FDE, and thus sort of making the whole requirements a bit ridiculous. TPM2 should be an OEM only requirement.
If TPM2 is missing, warn me about the tedium and risks of memorizing my FDE key, let me make a key if I desire for Bitlocker. Warn me about not encrypting resting data. Then get out my way.
I suppose Microsoft doesn’t really care what ppl think or are comfortable with: it’s mostly OEMs that buy windows keys anyways, and they’ll continue doing so in the foreseeable future no matter how much windows sucks 🤷
@fl42v , my only disagreement with that is they work so hard patching their system to keep people from using hardware they deem “obsolete”. If it weren’t for their active effort to generate excessive e-waste and revenue by making sure people and organizations using their products continue to purchase new hardware, then I would be in complete agreement. They definitely do not care beyond making their ever growing quarterly profits.