hmm,,,,,I have same problem.
hmm,,,,,I have same problem.
To be clear, are you saying the same NTLite version works correctly on W10 host, but doesn't on W11? Or using the same host, but different results for W10 & 11 images?This problem only appears when running ntlite on windows 11.
In windows 10 no problem, after update the size of the image stays at 4.81gb.
Howdy if your using Ntlite under Win11 use the Ntlite 2.3.2.8526 version that works atleast worked fine for me using it just for DISM cleanup update then use the up to date version to make changes to the image.I have same problem.
Dism clean-up image not working in windows 11.
Original Iso 4,8gb, after update and cleanup resetbase, it 6gb
This problem only appears when running ntlite on windows 11.
In windows 10 no problem, after update the size of the image stays at 4.81gb.
that's right sir !To be clear, are you saying the same NTLite version works correctly on W10 host, but doesn't on W11? Or using the same host, but different results for W10 & 11 images?
tks bro ! i will try it.Howdy if your using Ntlite under Win11 use the Ntlite 2.3.2.8526 version that works atleast worked fine for me using it just for DISM cleanup update then use the up to date version to make changes to the image.
You will have to integrate using that version 2.3.2.8526 and use DISM to clean up.
If you did install the update using new versions or other type of Ntlite than 2.3.2.8526 will not clean up the image but i think this will apply on every other version.
I know kinda weird combination to use but still works out and it will not brake the image like MSMG did so yeah Ntlite DISM is still safer even on older builds atleast thats how i feel.
To be clear, are you saying the same NTLite version works correctly on W10 host, but doesn't on W11? Or using the same host, but different results for W10 & 11 images?
Can you re-read the question? There are two possibilities:that's right sir !
sorry sir I didn't read carefully.Can you re-read the question? There are two possibilities:
1st says changing the host makes a big difference.2nd says changing the Windows version makes a big difference.
"Yes", doesn't tell us if it's case #1 or case #2. Thanks.
ohhh ntlite 8526 working well.Howdy if your using Ntlite under Win11 use the Ntlite 2.3.2.8526 version that works atleast worked fine for me using it just for DISM cleanup update then use the up to date version to make changes to the image.
You will have to integrate using that version 2.3.2.8526 and use DISM to clean up.
If you did install the update using new versions or other type of Ntlite than 2.3.2.8526 will not clean up the image but i think this will apply on every other version.
I know kinda weird combination to use but still works out and it will not brake the image like MSMG did so yeah Ntlite DISM is still safer even on older builds atleast thats how i feel.
Reduced disruption
When there are fewer steps to perform, it generally results in faster installation. That's another product of redesigning how inbox, non-system apps are modeled in the UUP collection of files. In our internal, lab-based testing of canonical feature updates, we see an offline time (i.e., when the user cannot use the device) reduction of 30% when compared against Windows 11. We estimate we'll see ~21% reduction in offline time when measured at the 95th percentile.
We've also reduced disruption by integrating .NET Framework updates into the UUP based feature updates. Starting in Windows 10, version 1809, servicing of the .NET Framework moved from the Windows cumulative update to a separate, .NET Framework cumulative update. This change gave IT pros more control over the testing and deployment of these updates, separate from the OS cumulative update.
For Windows 11, version 22H2, we've integrated .NET Framework updates into the UUP based feature update. The result is one less reboot required after moving to Windows 11, version 22H2. Why? Well, before this change, a device would install the latest OS feature update via Windows Update. Being UUP-based, it would also include the last cumulative update as well, to let the device get current in one step. However, since .NET Framework is a separate update, it would not automatically get installed. Instead, once the new OS was booted, a separate scan against Windows Update would detect and install the .NET update, unfortunately requiring another reboot.
Editor’s note: The integration of .NET Framework updates with the Windows 11, version 22H2 feature update is coming soon.
Thanks for the feedback.Howdy if your using Ntlite under Win11 use the Ntlite 2.3.2.8526 version that works atleast worked fine for me using it just for DISM cleanup update then use the up to date version to make changes to the image.
You will have to integrate using that version 2.3.2.8526 and use DISM to clean up.
If you did install the update using new versions or other type of Ntlite than 2.3.2.8526 will not clean up the image but i think this will apply on every other version.
I know kinda weird combination to use but still works out and it will not brake the image like MSMG did so yeah Ntlite DISM is still safer even on older builds atleast thats how i feel.
Howdy no just download the latest Win11 22h2 clean no tweaks Ntlite Dism /comp does not clean up the superseded links this does not happend when using Ntlite any version type under Win10 21h2 22h2 only under Win11 even 21h2/22h2.Thanks for the feedback.
Do you have an exact image + updates + settings combo for me to test that?
I'm asking as in your existing preset there is no such tweak set.
Don't forget any REGs if you're integrating, try without those first.
What would help is also logs at the moment of the error with the latest version, %temp%\ntlite.log and ntlite_dism.log
Yes 100% your correct but only under Win11 and the only one version seems to work fine is 2.3.2.8526.BAZ.Andreas the superseded is still being listed inside the updates and bloating the image..... am i correct ?
Please attach the %temp%\ntlite.log and ntlite_dism.log at the moment of the error.Howdy everyone
So i just did install the new version of Windows 11 latest update with the latest NtLite version and i wanna say that DISM works and it does clean the image as it did under Win10.
Now i dont know if it was the new update for the Windows or NtLite new version.(Also did disable UAC to when i did the test)
Thank you everyone!!!