This is what happens when a new ISO leaks, specially with LTSC, all praise them for their long term support and no new feature updates but as soon as there is a new one available all move to the new one (with exceptions), for the new features
I know what you mean personaly I just look for a stable build that has long time support but most important for me is that everything works how it should should be....
And so? I quoted your message just to state the obvious for people who read the forum. No need to be so susceptible.
You obviously have some kind of problem that I answered some guy's question with a kind answer. Unfortunately common here.
Yes, you were kind with that user, and no one denied that. Your problem is that you don't understand how forums work. This is not a chat between me and you, this is a place where a single message can be read by 1000 users, and some of them may find useful what the user X says, using what the user Y wrote as a starting point. It's not rocket science.
Windows XP could be installed to FAT32 and it was even offered as option by the installer for partitions smaller than 32GB
Every MS OS before Vista could use FAT filesystems. This changed when they introduced the Side-By-Side repository (WinSxS) in order to escape DLL hell; as it heavily relies on hardlinking, NTFS is a must (FAT doesn't support any of the new features).
Hard-linking is there to save space not to solve the dll hell. Nothing, in theory, would prevent to have a copy of the file instead of a hardlink. I think in reboot forum there were experiments of vista/seven running on fat32
The SxS Store has been introduced to allow multiple versions of DLLs existing next to each other, and each program can link and use the version it needs, instead of multiple programs overwriting the only DLL in System32. While they could have decided to do it with copies, they chose not to. Carefully read, plz: SxS has been introduced to solve the DLL (and other shared resources) problem. The fact it uses hardlinking is just one aspect of it. It is readily available in NTFS, saves space, and is fast, so they chose it.
That's a different matter, having version copy of the same dll is done putting them inside the user profile. Which perhaps is the negation of the very reason the dll were invented (again saving space). Hardl-linking is just a brilliant way to have always a "copy" of the installed (and not installed) components w/o duplicating the space needed for a real copy. Perhaps you don't save just space but also time, given creating a hardlink is practically istantaneous, no matter the size of the file, while doing a copy takes time, which is proportional to the file size
This is version is RTM version release later in 2024 with cumulative update or not ? I have see microsoft release other build last week.
Finally I had the time to build the IoT /LTSC build 25398, and I'm really really pleased to se how well it works (relatively speaking.... It's still Win11) None of the ugly troubles seen in 26100 and 25941. As a bonus, being the very last 253xx in the wild, it still works on old CPUs As a further bonus being based on a official release it has no expiration date, and can be activated W/O any trouble.