So I use the above preset on non-patched ISO, OK, will try a bit later.
My test was on latest 24H2 patched with Copilot components removed.
NTLite Features page is DISM.
garlin, tested by removing both Copilot components from the image, and all 3 copilot named from Live.
Explorer tabs are still there, so cannot replicate, please attach a preset demonstrating that - could be it's some other component in conjunction.
Also for those configuring instead of...
Thanks, indeed that's a good idea, will see about adding the support for it it and to the update list.
Will reply here when done, if all good in a few weeks.
ogoniciel, thank you for the feedback.
Listening to NVDA, I'm not happy with the result, mainly the ribbon toolbar navigation which does not focus correctly to read the options.
Will work on it and reply here when an update is released. Due to summer slowdown, it might take a few weeks.
Tested it, it's LDDM
Remove this line from the preset
<Tweak name="DXGKrnl\DXGKrnl">1</Tweak>
Will lock it from editing since it's so sensitive just going from Boot to System, will test if just for 24H2 modern setup.
But this entire Extra Services section is better to avoid unless you want to...
First time I'm hearing that, people used it with NVDA before, maybe there is a mode that needs to be turned on.
Either way, please describe what is the issue and what is expected compared to some other tool - could be File Explorer for example.
You can use the latest, never use older versions unless there is a temporary bug for your scenario.
Whatever worked before, will still work. Note that newer Windows versions might require a license renewal, depending which one you aim.
List and dates are at ntlite.com/features, scroll down...
It doesn't, as all images already have winget/appinstaller licenses built-in. Haven't seen any issues so far.
Not clear why Microsoft ships that file, could be for some older Win10 images and those that are shipped without the installer.
But do let me know if there is a scenario where you saw a...
It reads the license file content and matches the family name, also searches for internal licenses in the image during integration.
So if you meant can you add multiple packages and their licenses, yes - also filename itself doesn't matter.
If anyone sees any issue with the described, no matter...
I don't yet, but just to comment on the assumption that Legacy means for old machines.
Legacy just means use boot.wim setup, the way it was always in all Windows images until 24H2, while its "Modern" setup uses winre.wim.
They left the legacy setup in for a reason, probably the new one is not...
zeroone011011, does this still happen with the latest version and fresh (non-edited) ISO content?
If so, please attach your preset (auto saved xml, not autounattend).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.