Windows 10 Recovery Tools - Bootable Rescue Disk

topgundcp said:

There must be some glitches with your current Windows i.e maybe some background process suppose to run to take care of the clean up is not running. If your Windows is running correctly, you should not have any leftover from those 2 folders. Had nothing to do with sfc.

Well I don't think so, if their was a background process not running, maybe...that could be it. BUT......the pendingdeletes folder was empty, and only my pendingrenames folder was not. This happens ever since my 1st clean install of Windows 10 Pro. So its nothing new. Its a problem I think with Windows 10, not weather I have a background process not activated. Also Dino, it IS SFC /scannow that makes those files appear.....nothing else. Happens every time I run SFC. Always takes a new update to remove and clean out those 2 folders. Their was one or two times that the DISM command actually worked, and DID clean them up. But most of the time the DISM command may only clean 1 of the 2 folders.
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Always.....always has been because of running SFC.....always. Right now thou, those folders are empty as I went and restored my last image backup. In the process of updating about 6 different apps.....and windows just installed the last update we got on the 17th of DEC. This restored update was made on 12/11/15 . So their empty now, and will stay empty till I run SFC.....then it will happen as usual.

topgundcp said:

I should not have said that SFC has nothing to do with it but the cleaning part has nothing to do with it. Of cource, when you run SFC and if there's any repair made while Windows is running then the corrupted files cannot be replaced while online, but will be put in those folders for the next reboot.

Yes that is how its suppose to work.....just doesn't work on either of my TWO computers running Windows 10 Pro. That's why I asked about new idea's on how to clean <--- not delete manually or anything like that....just make Windows clean those 2 folders, correctly. Never really found a way that works 100% .....no real big deal....just pisses me off a tad, nothing more than that. :)

Kyhi said:

Booted Win10PESE - and deleted the files - no trick...
I do not run SFC... Dism is good enough for me...

Yes I suppose that's is one way to clean it up, just not the right way....at least for me. But on another note I did get rid of them and gained back almost a gig of harddrive space. I went and restored my last image backup, that I made with Macrium Reflect.
Then only had to update 6 programs, as my last image was almost 3 weeks old. I still think this is a problem with the SFC command and Microsoft should address this bug too. Because it does NOT always clean up after its self. :)

Kyhi said:

The program works by using Dism and Windows 7 does not have Dism...

>>>>

I could add a DISM Attachment and Point the Program to use it - in cases where DISM is not present on the Host (Windows 7)

I do not have a Windows 7 OS anymore - So I have No Way to Test the Results - But You Can Test the Results, if you wish..

Image_Health_Dism

Hi Kyhi,
Thanks for this Image Health_Dism 'special edition' for testing under Windows 7.
The Readme file with the instruction appears to be identical to the standard version.

Currently the OS does not show issues with the standard sfc /scannow check but just in the case, I am interested to check how it works.
So if you integrated the Windows 7 support and I have VM running 7, which procedure should I follow in order to test correctly this special version, please?

Thanks but... if the the sfc /scannow does not find anything because the OS is fine, is there any way to 'test' it without destroying some system file?