Thank you, it worked perfectly. I don't know how I missed this tool until now... For the first problem, I found a couple of users in other forums with the same problem. In one case it was an official MS site, where "experts" answer to people, but every time I read the "expert" answer, it is always a generic, useless answer. In this case the user removed the Windows Fax and Scan and another feature, got stuck with KMOD BSOD. The expert answered to hide those two updates... I don't know if they even understand what they read (if they read at all). Another user with the same problem tried with sfc scannow, dism scanhealth, but nothing worked. He thought it was a problem with remaining disk free space, as he got less than 32 GB, At last restoring a previous image with system restore worked but every time he removes Fax & Scan the problem reappear. I also made a lot of trials, but I cannot find a solution: at the moment I can say with confidence that in 32 bit Windows 10 if you remove the Fax & Scan feature it is an automatic BSOD. Tomorrow I will make another try, removing that feature before installing Windows.
Yes, if you remove it on 32bit Windows version (I tried on various 21H2 editions), you get a BSOD. Now I removed Fax & Scan before installing Windows and everything worked fine. I used NTLite to remove Fax & Scan, with Configure > Features > Features On Demand (Capabilities) Then I tried re-adding the feature (you need an Internet connection for Windows to get the package) and everything was ok. But if you remove again the feature, the BSOD returns. There must be something very wrong in the Fax and Scan package...
@BubuXP good morning, well as far as I know NT Light does NOT work correctly with LTSC versions of Windows so...
In fact I used W10UI instead and it worked perfecly. If you talk about the BSOD, it is not related with NTLite. The blue screen appear even on vanilla Windows installers, but only on 32 bit. I tried in November 21H2 images (LTSC and also Pro) and in fully updated images (that means the bug is still not fixed). Now I'm curious since what version this bug is present, like since 20H1, or 2016, or earlier?
For me on vmware all Win 10 x86 installs show a BSOD and sometimes at the second run it goes thru. on vbox or real hardware it never gives a BSOD on my tests.
Nice to know for real hardware, but I used both vmware and virtualbox and they behave exactly the same, and never happened to go thru after reboots or power off. I should test with real hardware too...
Hello. Does these stuff work with Windows 10 Enterprise LTSC 2021 or should i go with Windows 11 instead? Windows store Netflix App with HDR and Atmos? HBOMax with HDR and Atmos? Disney+ with HDR and Atmos?
Is there any easy way to sideload windows store apps when using windows enterprise? I found winget but have run into a whole other can of worms trying to get it to build so I was curious if there is other solutions without having to use windows store. Edit: Ended up using Device Portal in developer settings to install packages that Enterprise otherwise didn't allow.
I don't know where else to ask this question, but I do know that the people here are smart enough to tell how to do it: As you know, During Windows setup you can no longer name the computer during OOBE. So is there any way to bring up the DOS prompt and name the computer during Windows setup. It truly annoys me the idiotic random generated names that the Windows installer now gives to computers.
The 2019 version did not work with HDR and Atmos when playing HDR and Atmos content with Windows Netflix app. Does the 2021 version have all media codecs like Windows 11 have? Are the 2021 version similar UI to Windows 11?
So what is the DOS command to do it and will setup overwrite the name you set, when it auto generates one?
This is not DOS, this is Windows. You can launch regedit, lusermgr.msc, powershell and so on. Whatever... from the command line the command netdom renamecomputer %computername% /newname:<NewName> /reboot:0 I guess should be enough Likely there are many other ways (via cpl, powershell, regedit....)