I've also had detecting nw fail on Win 10 installs on older hw. Sometimes post install, going into the n/w settings and toggling the jumbo frames setting or using an older chipset driver worked. Seems MS or 3rd parties are giving up support for older chipsets and components.
So why support it, it's not interesting. Even version 26200.хххх (25H2) causes problems, so what can we say about Canary? I'll tell you more: don't expect anyone to tell you when a normal, problem-free Canary will be released. Canary/Dev is the future state of Windows, and it may or may not be in Stable. That's why I personally don't see any point in working on this version of Windows. ИМНО
MS is now focusing on the Canary version. All the bugs left over from Win10 and early Win11 will be fixed in Canary first. Secondly, Win11 and Win10 are both based on the NT10 kernel, except that MS will release Win12 in the future and upgrade the NT11/NT12 kernel. On the contrary, Win11 Canary is the latest bug-fixed version of Win10, so it runs very stably. As for Canary being a future version, don't expect stability, etc. IMHO, the latest Win11 27881 is already very stable. We can regard the high-version NT10 kernel Canary as the most stable "Win10"
In addition to Microsoft releasing Win12 with upgraded NT11/NT12 kernel, we should use the latest Win11 Canary, which is of great significance
Microsoft has all solutions. but it wouldn't release them now, or in an all-in-one package. Microsoft will release some every time. (of course, if you identify its one bug, such as EternalBlue. Microsoft would release its solution one second later. it has the solution in advance). people here are working on their own solution as they know Microsoft well. they are NOT Microsoft's co-workers. but they know how to use Microsoft's work in a better way, in a safer way.
I have no doubt that Microsoft already has all the solutions, but they are in no hurry to implement them in their product. Because right now they have other concerns, such as cramming as many unnecessary components and features into the image as possible. Well, we, for our part, are trying to clean up the image of all this crap to the best of our ability and knowledge so that our system works stably and quickly.
Well, who's arguing with you? Everyone is entitled to their opinion on this matter. You really like Conary, fine, use it to your heart's content. Believe that it's a very stable and good system, it's your decision — good luck!
Question for the audience, maybe someone knows and can help me out: it's super easy to use a script to change the Eterprise LTSC edition to the IoT Eterprise LTSC edition, but how do I change the IoT Eterprise edition to the IoT Eterprise LTSC edition?
The software in the Tools folder is very old. I dug out the old software and upgraded it to the latest DISM11 and also upgraded it to ADK 27798
Normal SKUs and LTSC SKUs are from two totally different branches. Neither are they virtual siblings of the same parent SKU (for easy switching using Product Key), nor is there an officially supported upgrade path whatsoever. So, according to MS, you can't. You might still be able to do it with a tool like this: https://forums.mydigitallife.net/threads/upgradematrix-xml-fix-tool-very-beta.88518/ and following ISO upgrade installation.