Thanks for sharing your experience with this - good to know.Not sure if there's a fix for this (other than to return to regular Windows 11 non-LTSC, which is not something I intend to do, given how bloat-free the LTSC version is), but I thought I'd post in case someone else happens to have the same issue and can't find a fix.
A somewhat similar thread here - without any apparent solution or answer - just to link these probably related things:
https://forum.rainmeter.net/viewtopic.php?t=42521
The problem with bloat is that one doesn't know for sure if some potentially useful things (like some .dll or something that prevents such issues) are included in that bloat.
P.S. Also, if that file doesn't come directly from Microsoft and it's some user customized / slipstreamed / whatever version, then that could explain this issue (or others) as well. I used to slipstream Windows installations in the past too, but the process is time consuming and a bit tricky if one doesn't know precisely which is which and the entire set of implications after excluding some package from the said installation / ISO file.
Statistics: Posted by Yincognito — Today, 11:30 am — Replies 11 — Views 16150