No offense but deploying and testing a SKU in a native vhdx (or inside a VM) is matter of 10 minutes, so why not start trying what you're interested to now that you received the basic directions?
Thanks very much for the info. I ask that because i think that i will switch to LTSC 2021 for a very important computer that is use only for work and i need maximum stability
No, EVAL versions do not support KMS or other activation methods, in general. EVAL version can only use the Evaluation license channel, which is time-based.
has microsoft ever published the hash of the LTSC iso's? if yes, they can be accessed through archive.org?
https://forums.mydigitallife.net/th...ot-enterprise-n-ltsc-2021.84509/#post-1705449 They are not publicly shown anymore. Need to be Volume license customer. However, the linked checksums are directly from the horse's mouth. LTSC 2024 is a leak, no confirmed checksums for it.
In your opinion, when Windows 11 LTSC 2024 is available, will it be possible to install it on a pendrive using Windows To Go?
Who cares of win to go when you can use a native vhdx, no matter if its on a hdd or removable device?
I'm currently running Windows 10 IoT Enterprise LTSC 2021 (21H2) on a Microsoft Surface Laptop 5. It works great. I'm fortunate to have the opportunity to upgrade to a Microsoft Surface Laptop Studio 2. Even though Microsoft officially only supports 22H2 on the SLS2, I'm not too concerned since the difference between 21H2 and 22H2 is very minor. What I am concerned about is that the drivers available for the SLS2 are only out for 22H2 (19045). Will I be able to integrate those drivers into the image LTSC - which is, of course, 21H2? I don't want to buy the SLS2 unless I can use LTSC. I could force the integration of 22H2 to meet the SLS2 spec, but I'm concerned that this will cause the OS to become unsupported in 2025. - Not to mention, it'll be an unpredictable frankenbuild. Has anyone else integrated or applied 19045 drivers to a 19044 build? Is this possible? Will it break future driver updates? I usually do everything the proper way, but this is basically what I'd expect with newer hardware.
I'm using Vista drivers on Win 11 and you're concerned by a cosmetic writing? That said when you guys realize that updating W10/W11 images is a pointless activity? Win7/8 was a different matter, but times changed NINE years ago.