Windows Server runs worse than even original debloated Windows 10, even if I disable the server related features and switch the SKU to pro with your method. I guess every hardware is different . Maybe it is because I cannot install Ryzen Power Plan there?
Define worse I never noticed any meaningful performance difference, btw there are few settings that may impact performances (nx bit protection, prefetch/superfetch, compressed memory, prefer background services over foreground apps and so on. Perhaps you are talking of one specific build, while I'm talking in general starting from WinNT4 server
You can run Win7 on almost any modern hardware just put extra usb3 ahci ethernet wlan & rst drivers then you are good to go Edit : i forgot to write one more thing which is to update install wim from win7 iso sources directory to a working win10 iso sources directory.
Is not that simple, here people are talking not just of modern HW (where the right drivers are everything you need), here the point is about modern HW + pure UEFI, where bios calls are not emulated and so on. It's mostly an uncharted land.
if i am quoting a msg as modern hardware i mostly quote it as for UEFI bios but not for legacy bios one.
Then your sentence is not valid, or at least, is not universal given the number of variables involved, starting from vga make, generation, and firmware.
Do you know something that you are trying to puzzle people here to get there modern hardware Pure UEFI work flawlessly with win 7 sp1 updated offline using simplix updated pack with adding some more drivers to install wim plus adding final made install wim to working win 10 iso does the job . i thought to share those drivers i use but now i wont share them here on mdl in anyway.
No need to react this way, I just said that the world is often more complicate than it seem. You can't say, after a success on a machine or two, that everyone should expect a success, no matter the machine in question. Just to say I have a 2006 machine where win2000 is impossible to install, no matter the patched drivers or any other voodoo tecnique I tested, when there are W2k installations working perfectly in machines 10 years younger
try installing it in VMware, back it up with Macrium reflect or ghost if its that old, and deploy it back to the machine you want
I'm not exactly a newbie, deploying to virtual disk is what I do for everything (and there is no need to use crap like Macrium or Ghost when dism and wimlib can do whatever you want). The point is that W2K just dont like the bios telling that is not acpi compatible, no matter the acpi.sys I use, so old school setup or modern way is irrelevant, something in the bios is broken from W2K point of view. Thanks for your suggestion anyway.
I don't think patching ACPI.sys is the cause of the winlogon error, I think it was already present even before ACPI patch, but ACPI error had a higher priority so it wouldn't show.