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.
From what I understand about the windows 10 install is you have to remove the internet connection to get the option.
This is the easiest way.
It says no such command found.
Make sure you use a back slash and not a forward slash.
oobe\bypassnro
Try Windows 10 Enterprise LTSC. There is an official evaluation .iso out there. Keys for full version cost very little. Enterprise 10 is the ONLY Windows out there which is not complete bullshit.
I use win 10 ltsc image, it did not require me to set up an account last time I installed it, maybe try that? You can get it from the mass grave’s. Don’t forget to enable USB passthrough in your VM manager.
You could either try dockur/windows, a Docker container that runs a Windows VM in QEMU. They have account creation etc. handled automatically afaik.
If that doesn’t work for you, you could try looking into how they set up accounts automatically.
Try Win11 IoT Enterprise LTSC. It is available from this link. I know it’s piracy, but fuck Microsoft.
What’s this got to with Linux?
Nobody knows how to work around Microsoft BS better than Linux users.
Check the first rule
I’m not the OP, report the post if you feel it’s in violation…
In Windows 10 there should be “Join domain instead” button. Click it and enter your new username
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.
Maybe you can use a public computer at your friendly neighborhood library
Tiny11 iso
i always think it’s ridiculous to just use an ISO manipulated by some third party people. at least last time when i quickly googled it, it was intransparent as hell. not only weren’t i able to see the full extent of changes, but also it was published by some rando in the internet. i don’t think anyone should seriously consider using it.
Tho to be fair I wouldn’t want to use an iso distributed by a shady company like Microsoft.
Not wrong, it is shady. Though the NTDEV guy behind it does have some (sparse) information on their patreon about how and what tools, mainly seems to be done with osdbuilder. Comes down to trust as with anything on internet, I just need to run chkdsk.exe on drives from time to time and the smaller it is the better.
He has a GitHub repository with all the build scripts that are used to do it. But I’ll still use Win11 IoT Enterprise LTSC instead of this.
Once the downloads work again, this might help:
https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
i got around this by opening cmd (Shift + F10) during the setup and disabling the network adapter.
wmic nic get name, index
wmic path win32_networkadapter where index = 2 call disable
index will be 1 or 2 probably depending on your setup it was 2 for me. this worked for me recently on boxes on fedora with a win10 iso.
This does work anymore for some ISOs. Depending on the version and Region i actually could not continue without connecting it to the internet. The oobe\bypassnro does work more reliably.