Is it safe to "Custom" clean up expired patches?

Mr. Yu

Mr. Yu

Member
Messages
314
Reaction score
24
Hello, when Win7 integrates patches or Win10 integrates. net3.5, these patches are marked as suspended. At this time, the "Dism Compatibility" and "Dism Resetbase" in the update backup will no longer be available and will report an error, but "Custom" will still be available. Is it safe and reliable? And it cleans up more expired files than the previous two. Should I use this option for all versions of Windows?
 
For .NET frameworks before 4.8.1, integrating any .NET update will create a pending operation in the install image. That's because on install, Windows needs to apply pending .NET changes only after the next available restart.

Until then, DISM doesn't allow you to perform cleanup. What you should do is apply the .NET updates separately in a second pass, so the .NET-free image can be cleaned up without being blocked by pending operations.
 
Thank you very much, Garlin。 So the correct operation for win10 is: integrate cumulative updates - clean up patches - install. net3.5- remove components?
 
Hi, how do I clean up expired files after the Windows 7 integration patch? The cleaning work is blocked by these pending patches. All integrated patches in Win7 will be suspended.
My operation is: integrate over 50 patches - attempt to clean up expired files and be blocked
捕获.PNG
 
Apply patches first and load your patched image and do removals in a second run of NTL.
 
You apply the non-pending updates first, then run clean up. Apply the pending updates last. Only a few W7 updates will be pending.
 
You must log in or register to reply here.
Back
Top