Returned components 18363.418
- Thread starter kosta26
- Start date
I thought it was fixed already. There was previously a cleaning function of some kind.
Yes there is a cleanup, ege subtly pointed to it already, it's under "Source - Tools - Remove Reinstalls", or right-click on C:\Windows on the Source page.
Run the cleanup after update and initial reboot, then ignore if there are any returned icons or popups until cleaned.
You can also run it as a parameter from a script/shortcut:
Code:
ntlite.exe /cleancuMaybe automating the cleanup later on, first working on auto-updating the tool itself, so any fixes can be deployed before the autocleanup.
crypticus
Well-Known Member
thank you i didn't know there was a switch for that, i can easly create a task to run this after every windows update's first restart etc...
nuhi is there any way to surpress any diaglog box generated by ntlite? and run it silently maybe? because when i apply that command it asks for some information if u use it first time in a freshly installed computer so i can't automate scripts
nuhi is there any way to surpress any diaglog box generated by ntlite? and run it silently maybe? because when i apply that command it asks for some information if u use it first time in a freshly installed computer so i can't automate scripts
Last edited:
So, I did my first ever Host Refresh for Win10 using the NTLite Wizard. I went from 1903 Home to 1909 Home.
I did a Trim first, which removed the only 3 KB's I had used for 1903. (None of which were a Cumulative Updates.)
Then I had NTLite check for updates for 1909. It found a Cumulative update - which I did NOT download. And a Service Stack update, plus another that I also slipstreamed. (Which was a "cumulative .NET update.)
Everything went well.
Even tho I had not installed a Cumulative Update per se, I decided to run Remove Reinstalls anyway.
To my surprise, it removed a few files.
I don't know why.
I don't know if it's supposed to.
I thought I had saved the log file made during the Remove Reinstall operation. But didn't.
The only thing I can think of is that 1909 is said to be a "service pack" like version of 1903. So maybe it has some "cumulative updates" in the wim itself?
I did a Trim first, which removed the only 3 KB's I had used for 1903. (None of which were a Cumulative Updates.)
Then I had NTLite check for updates for 1909. It found a Cumulative update - which I did NOT download. And a Service Stack update, plus another that I also slipstreamed. (Which was a "cumulative .NET update.)
Everything went well.
Even tho I had not installed a Cumulative Update per se, I decided to run Remove Reinstalls anyway.
To my surprise, it removed a few files.
I don't know why.
I don't know if it's supposed to.
I thought I had saved the log file made during the Remove Reinstall operation. But didn't.
The only thing I can think of is that 1909 is said to be a "service pack" like version of 1903. So maybe it has some "cumulative updates" in the wim itself?
Okay, I remember now. The log was in the NTLite temp folder.
Now, if I am understanding this Feature correctly, if I were to Refresh Win10, and not use a Preset to remove anything from the fresh, new .wim, then in theory, Remove Reinstalls wouldn't remove anything. Is this correct?
That is, there are only items to remove that were added back if I had removed some items in the Refresh?
If true, then it seems to me that one should run Refresh Reinstalls AFTER removals are done.
For example, the first time I ran Remove Reinstalls, I had removed some components with a Present during the Refresh. And a few files were removed.
But then I ran NTLite again and went through the list and removed more components. Then I ran Remove Reinstalls again.
This time it removed 46 files. (Although I don't know why there were orphans left over. Wouldn't NTLite have removed those during the second removal?)
This time, I captured the log.
Now, if I am understanding this Feature correctly, if I were to Refresh Win10, and not use a Preset to remove anything from the fresh, new .wim, then in theory, Remove Reinstalls wouldn't remove anything. Is this correct?
That is, there are only items to remove that were added back if I had removed some items in the Refresh?
If true, then it seems to me that one should run Refresh Reinstalls AFTER removals are done.
For example, the first time I ran Remove Reinstalls, I had removed some components with a Present during the Refresh. And a few files were removed.
But then I ran NTLite again and went through the list and removed more components. Then I ran Remove Reinstalls again.
This time it removed 46 files. (Although I don't know why there were orphans left over. Wouldn't NTLite have removed those during the second removal?)
This time, I captured the log.
I restored my previous Win10 1903 and did a new Refresh to a vanilla 1909 which only had 2 KB's slipstreamed into it.
I have now run NTLite Live about 5 times on it as I carefully removed components from the mostly vanilla 1909.
The last run was Complete Cleanup, which, surprisingly, found more stuff to delete after I had run the Windows' DiskClean.
In theory, there shouldn't be anything more to clean up, since I didn't install any Cumulative Updates.
But I'm tempted to run Remove Reinstalls next.
Any harm in doing so?
My concern is that I don't understand how NTLite knows what was "reinstalled." Shoudn't there be a "snapshot" tool to take a picture of our previous Win10 before we do a Host Refresh, so that NTLite has a catalog (or database) of what was installed? (So that it knows what to remove.)
I have now run NTLite Live about 5 times on it as I carefully removed components from the mostly vanilla 1909.
The last run was Complete Cleanup, which, surprisingly, found more stuff to delete after I had run the Windows' DiskClean.
In theory, there shouldn't be anything more to clean up, since I didn't install any Cumulative Updates.
But I'm tempted to run Remove Reinstalls next.
Any harm in doing so?
My concern is that I don't understand how NTLite knows what was "reinstalled." Shoudn't there be a "snapshot" tool to take a picture of our previous Win10 before we do a Host Refresh, so that NTLite has a catalog (or database) of what was installed? (So that it knows what to remove.)
In my obsessiveness I just couldn't resist one more experiment with Remove Reinstalls. The result surprised me. Here's what I did:
Had been running Win10 1903 with three previous KB's. (A Service Stack (now obsolete I think) and two others.)
I did a "clean" Refresh to 1909. That is, I did not run 1909 through the Host Refresh Wizard's PreSet before refreshing.
The 1909 wim had only two KB's. A new Service Stack. And a cumulative update for .NET.
After 1909 was running, I removed Components using NTLite.
And then I ran a "complete cleanup" using NTLite.
At this point, I didn't expect that there would be any 'Reinstalls" to remove, since 1) I had removed everything ahead of time using NTLite, 2) I hadn't installed any cumulative updates, so nothing should have been reinstalled over what I had already removed, and 3) I had run NTLite's Cleanup, which should have removed all traces of what I removed in 1).
Nevertheless, Remove Reinstalls found a bunch more stuff to remove. Those pesky languages, which I reported earlier in the forum as a possible bug. Windows Defender - which I thought I had removed with NTLite hours before. Others. See log, attached.
So, it seems that Remove Reinstalls should be called "and Deep Cleaner" too, and perhaps users should run it regardless whether they've installed a cumulative update.
Or should NTLite's Clean up catch these things?
Had been running Win10 1903 with three previous KB's. (A Service Stack (now obsolete I think) and two others.)
I did a "clean" Refresh to 1909. That is, I did not run 1909 through the Host Refresh Wizard's PreSet before refreshing.
The 1909 wim had only two KB's. A new Service Stack. And a cumulative update for .NET.
After 1909 was running, I removed Components using NTLite.
And then I ran a "complete cleanup" using NTLite.
At this point, I didn't expect that there would be any 'Reinstalls" to remove, since 1) I had removed everything ahead of time using NTLite, 2) I hadn't installed any cumulative updates, so nothing should have been reinstalled over what I had already removed, and 3) I had run NTLite's Cleanup, which should have removed all traces of what I removed in 1).
Nevertheless, Remove Reinstalls found a bunch more stuff to remove. Those pesky languages, which I reported earlier in the forum as a possible bug. Windows Defender - which I thought I had removed with NTLite hours before. Others. See log, attached.
So, it seems that Remove Reinstalls should be called "and Deep Cleaner" too, and perhaps users should run it regardless whether they've installed a cumulative update.
Or should NTLite's Clean up catch these things?