I'm not sure if this old man is up to it. The 1st and only reconstruction I did was back in 11-2021 to make a 19041.1 LTSC from Pro. I've been totally out of the reconstruction loop since then. At the time, it took me weeks to get it right.
Well this time most of the work is already done by others https://forums.mydigitallife.net/th...-ltsc-2024-preview.88019/page-21#post-1833531 Yeah. But (after my server 2020) is 19041 LTSC is still one of the best Windows out there. Probably the best of the best overall. With newer version you lack features (say edge or RemoteFX), older versions may be faster, but may show the age when dealing with drivers or other apps. So time well spent.
For the record seem that since 26080, there is a stricter check, that prevents the boot on (AMD only) SSE4a CPUs This cuts out a further number of AMD CPUs based on the Barcelona microarchitecture (Phenoms I & II, Turion II, Athlon II, Lano APUs, and so on..). On 26080+ seem you need a proper fully fledged SSE4.2 to boot.
Why that build, what's so special about it? I am now running 26100.268 and it's great, before that I was on 22631 (Constructed).
What's so special? It works w/o problems (unlike 26100, 26085, 26080) It has no CPU hard block (unlike 25903+, which got worse after 26080 as I wrote above) It has no expiration and it has CU updates (unlike any preview build) IoT has a wonderful balanced power scheme, which is way better than the ones seen on Server 11 and on poor man's W11 Last but not least isn't just the stupid build that you install pushing OK 3 times, keeping the brain trained is a great "side effect" although "we know who" tries to keep the users as dumb and tamed as possible.
It probably cannot be bypassed. But CPU's without POPCNT are very, very old by now. Not many users will be affected by this. But a few will.
Typing right now on a Turion X2 based notebook released before vista and sata drives were a thing (albeit later models came with Vista SP0 and a Sata drive). It works great on 25398 (obviously it's updated with a SSD and 4GB of RAM, and a Tyler CPU) there was really no technical to block it other than forcing less informed users to buy new HW when they haven't.
Ok. I have not experienced any issues with 26100 apart from the error popup when I want to restart the PC but maybe the error is gone with the 268 update. I have a 25398 ISO that I downloaded from another forum but I haven't installed it on my PC, just ran it in a vm for a few minutes. On the forum where I downloaded it they were sharing custom updates for it so I guess you can't update it without modifying the updates. Maybe I will give it a try.
Just installed 25398.820 ProWS on an old AMD PC with no issues. Couldn't install 23h2 or 24h2 but like ace-5100 said it's a great OS. And every 2nd Tuesday it get new updates to be converted & installed.
I installed 25398 Enterprise G to a VHD but I had some issues with it so I am back to 26100. Bluetooth driver didn't work, it installs but device manager shows exclamation mark and when I manually select the driver the mark is gone but it shows that the device could not start. Also the "alt gr" key on the keyboard was not working, hmm. I see no reason to not use 26100 if you have a CPU which it supports.
No sane minded people would use the useless MS BT stack, but anyway it works as it's supposed to. I use exclusively the UKX layout although I'm not in UK, it would be useless if the ALT Gr key didn't work. It works perfectly and I can write characters like ẃ é ý ú í ó ç ¦ € É Ó Ẃ Á Ó É Ú w/o any problem Try to open your eyes, high lssas usage, breaking in network protocols, stupid curves in balanced CPU power profile and so on. Everything was OK until 26052 or so, then MS (as usual) decided to screw a perfectly working build shortly before the release
I have not noticed those issues and I don't use balanced profile. I tested another 25398 version and keyboard works fine there but I could not open any exe files. Now I am trying a third version and keyboard works fine too and no issues with Bluetooth driver but Windows did not detect any audio devices so I had to install Realtek driver which I did not have to do in any other Windows version since I use SPDIF and it works fine with Microsoft provided drivers. And also I am not sure how to update to .830. I downloaded a custom update but it's ESD files (SSU-25398.830-x64.esd, Windows11.0-KB5036910-x64) and W10UI doesn't seem able to install them.
I use a domain and the issue are clearly there, in 26100,26085,26080 (and also2606x if not updating a older version), both Server 11 and Win 11 If you aren't in a scenario that triggers a bug / problem doesn't mean the problem isn't there My home server is up h24, having it consuming 20 W instead of 60W or more is something that matters both for my pockets and the environment. What about building the image yourself instead of relying on a badly built one downloaded from somewhere? https://forums.mydigitallife.net/th...struction-project.80939/page-787#post-1834541
Yeah, I didn't say that it's bug free, I just said that I haven't noticed any issues. I could have tried to built it myself but I didn't feel to do it now. I'm not going to bother with 25398 anymore, tried a 4th build and alt key does not work but Bluetooth driver works and sound works out of box. So I tried 4 different versions, one of which is built by a trusted MDL member and they all had some issues. Seems strange that all 4 are badly built. And also updates needs to be modified before they can be installed, one more reason to not use 25398. I have a 22631 EnterpriseG "constructed version" which works well, I can go back to that one if I want.
In short, Win11 24H2 for x86 requires x86_64-v2. While Win11 24H2 for ARM requires ARMv8.1... Funny that Microsoft is moving the baseline architecture up like some Linux vendors are doing.