Windows 10: How can I clean these .MUM and .CAT files from failed updates?

Thanks for the info will see how it works...I'm still on v1703 but that won't change anything will it? Going to wait for the next release to upgrade. Hell an upgrade would probably clear up my problem now wouldn't it? *chuckle Suppose I could wait on that LOL!

 

I have a very large quantity of them! And they occupy quite a bit of space?

:)

 

How to stop Windows 10 from installing

I have re-hidden the optional Upgrade to Windows 10 update but as I have explained in previous communications, KB3035583 is not in the Update list.

I am still wondering if the references to KB3035583 found on my c: drive, are not causing this condition. I
find these references (using the dos command dir c:\*KB3035583* /s /p.

Directory of c:\Windows\servicing\Packages

07/06/2015 09:09 PM 13,315 Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.cat

07/06/2015 09:09 PM 3,929 Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.mum

07/06/2015 09:09 PM 7,749 Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.29.cat

07/06/2015 09:09 PM 1,490 Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.29.mum

07/06/2015 09:09 PM 7,749 Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.cat

07/06/2015 09:09 PM 5,378 Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.mum

 

System Restore Error PA3E08~1.MUM

I am continually getting the same error message when I try to do a system restore:

"System restore failed to extract the file C:\Windows\Servicing\Packages\PA3E08~1.MUM from the restore point. The restore point was damaged or deleted during the restore"

What can I do about this damaged/deleted file?

 

Just for grins, I ran the following command at an administrative command prompt with voidtools (Search) Everything open and *.mum as the display criterion:

Code: DISM /online /cleanup-image /startcomponentcleanup[/quote] The total number of objects before I started that operation was: 9,322. After the operation completed 20%, the total number was 6,940. It will take another 5 minutes or so for the command to finish, but I'll bet that the final count is even lower than it is right now. I'd say this provides proof positive that you can use this DISM command to clean up those files.
HTH,
--Ed--

 

The total number of objects before I started that operation was: 9,322. After the operation completed 20%, the total number was 6,940. It will take another 5 minutes or so for the command to finish, but I'll bet that the final count is even lower than it is right now. I'd say this provides proof positive that you can use this DISM command to clean up those files.
HTH,
--Ed--[/quote] Yes I only want to clear the ones that reference KB4093107 and KB4093117?

 

I could also use 10.0.1.3 and 10.0.1.6 I believe?

 

So how exactly would you recommend that I go about cleaning these files out? What would be the best procedure to follow?

 

You can use the DISM /remove-package command to target and remove specific updates in Windows 10, but you can use neither the KB number nor the Windows version number to target your removal efforts. It's more indirect than that, and requires some messing about with the list of installed packages to figure out what must stay, and what can go. I can't find a TenForums tutorial on this (anybody know of one? @Kari @Brink @essenbe @topgundcp @Bree) so I'll (reluctantly) point to this ArsTechnica piece: Removing Windows Updates via Command Line Not Working.
HTH,
--Ed--

 

My problem is that KB4093107 & KB4093117 failed to install in the first place and I reran the installations from windows update several times and these files are the remnants!

 

DISM /online /cleanup-image /startcomponentcleanup is used only clean up the component WinSXS folder and is advisable after every cummulative updates, It will clean up quite a bit of space.
If you list all .mum & .cat files in deltail view, you'd see the date and also the KB in question. I have mine listed and most of them dated back in sept. 2017
These files are owned by Trusted Installer and cannot be deleted even if you are the Administrator.
Try:

• Take ownership of these files and delete them. If failed, go to step 2
• Download: PowerRun v1.3 (Run with highest privileges)
  then run. Click on the Command icon to run as Trusted Installer, cd to the folder then delete them.
• An easy way is to boot up Linux then delete them.

If those KB's failed to update, you can safely delete them. Since I have a backup image, I booted into Linux and delete them all. Once back to Windows, Manually download the latest KB4093105 that update Windows to 16299.402 by passing all the updates in between.
You can use this link from @EdTittel post #1 or use mine in post #2 of this link, whatever you feel comfortable:
Download and Install Windows Update from Microsoft Update Catalog Windows 10 Tutorials

FYI, Even in this folder, there are thousands of .mum, .cat files but they don't occupy much space. After delete all the .mum and .cat files in mine, Windows re-created 1,668 files just to install KB4093105 and occupy 22MB total.

 

Great follow-up @topgundcp. Nice job of explaining what to do, and then pondering its advisability or necessity. You rock!
--Ed--