[SOLVED] Updates Failed, strange 8.3 (MSDOS) named files in servicing\packages (7 Pro x64)

[overand]

First - this is sort of a double post - I posted in the wrong forum somehow (too many tabs!) buit the info there isn't quite up to date anyway.

So - I had some update issues, described in depth here (in the improperly located post), but in short, I was able to run the Updated Readiness tool, load some .MSU files in, and make a bunch of progress. Now, however, two updates are stillf ailing, and... well...

The *current* state of affairs is a little weirder. I've included the CheckSUR.log below, and will update with a whole cbs log archive in a moment.

What seems to be the case here, though, is that in the midst of a bunch of normal files in c:\windows\servicing\packages, there's a a set of old-school, MS-DOS styled 8.3 with-long-filenames files.

That is to say, names like PA1A4B~1.MUM and PA1A4B~1.cat - that's odd, right?

I certainly am capable of either removing these, or renaming them as the CheckSUR.log seems to indicate they SHOULD be named. Or, I can delete them, run the CheckSUR tool, and install the MUM files from the Update Catalog as needed. But, I didn't want to make ANY changes to that directory without some pointers first!

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-28 23:38


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA1A4B~1.MUM Expected file name Package_53_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA1A4B~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA2771~1.MUM Expected file name Package_56_for_KB2868725~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA2771~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA543D~1.MUM Expected file name Package_54_for_KB2492386~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA543D~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA6730~1.MUM Expected file name Package_110_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA6730~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA89EF~1.MUM Expected file name Package_53_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA89EF~1.cat


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 267
Found 10 errors
CBS MUM Corrupt Total count: 5
CBS Catalog Missing Total count: 5


Unavailable repair files:
servicing\packages\PA1A4B~1.mum
servicing\packages\PA1A4B~1.mum
servicing\packages\PA2771~1.mum
servicing\packages\PA2771~1.mum
servicing\packages\PA543D~1.mum
servicing\packages\PA543D~1.mum
servicing\packages\PA6730~1.mum
servicing\packages\PA6730~1.mum
servicing\packages\PA89EF~1.mum
servicing\packages\PA89EF~1.mum
servicing\packages\PA1A4B~1.cat
servicing\packages\PA1A4B~1.cat
servicing\packages\PA2771~1.cat
servicing\packages\PA2771~1.cat
servicing\packages\PA543D~1.cat
servicing\packages\PA543D~1.cat
servicing\packages\PA6730~1.cat
servicing\packages\PA6730~1.cat
servicing\packages\PA89EF~1.cat
servicing\packages\PA89EF~1.cat

 

[overand]

More possibly relevant info - this had some sort of McAfee trial on it, before any of these updates, but I uninstalled it *and* used the McAfee uninstaller tool. (Some sort of norton cloud backup tool too, and same deal, removed & used the norton tool). Also, just some context for the weird files, (with the Windows Update diag tool in the background)

 

[Go The Power]

That is to say, names like PA1A4B~1.MUM and PA1A4B~1.cat - that's odd, right?

Very strange! I have not seen anything like this before.

Can you please upload a few and provide me a link to them? I would like to see what they contain.

Now I don't think this will work, but it will put the correct files onto your system.

SURT Package replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download Packs.zip attached to this post and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
7. Run the System Update Readiness Tool (SURT) again.
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.log

 

[overand]

Ready for the plot to thicken?

I've been two-timing with another forum (gasp!) and we did a little digging over there.

Per the CheckSUR log, those 8.3-named .MUM files are supposed to be named something else (probably due to hashes?) - which is what I suspect you attached.

Turns out that I *do* already have those files (with the correct names) in my c:\windows\servicing\packages location.

Given the file dates on these (8.3 named ones), either they were extracted from somewhere with their datestamps intact, this is an issue dating to the original installation of the OS, there was some sort of filesystem corruption, or some sort of not-actually-filesystem-corruption but an erroneous copy made for some reason.

I went ahead and searched the entire registry for "PA89EF~1" - nothing. (That's one of the .MUM ones) - I also searched for PA4DDC~1 (which is one of the cat files), still nothing.

Even though I can't really tell which CAT files are what, I'm quite tempted to just move these files off, maybe re-run the Update Readiness tool (maybe) - and try to install updates again.

Thoughts?

Given these files already exist in their proper form, I'm reluctant to apply the fix you suggested, BUT I will do so if you suggest so!

Here are the files in question, though! https://www.dropbox.com/s/gigcp0ltologu7n/Overand-weird-mum-cat.zip?dl=0

 

[Go The Power]

Did you also search the COMPONENTS hive? I would like to take a look at it.

SFCFix Collect COMPONENTS

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
5. SFCFix will now begin to upload your CBS logfiles to our server.
6. Upon completion, a log should be created on your Desktop: SFCFix.txt.
7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

If all goes well, you should see that your logfiles have now been added to your thread.

Given these files already exist in their proper form, I'm reluctant to apply the fix you suggested, BUT I will do so if you suggest so!

If the files are already there, there is most likely no point, unless the ones that are there are corrupt. If they are not corrupt it will just be replacing good files with good files, the system wont even notice the difference.

Even though I can't really tell which CAT files are what, I'm quite tempted to just move these files off, maybe re-run the Update Readiness tool (maybe) - and try to install updates again.

That is what I was thinking of trying, but first I want to make sure there are no references to this inside the COMPONENTS hive.

 

[LogBot]

Logfile submission from Overand

Logfile submission from Overand.

The logfiles are available at: https://www.sysnative.com/niemiro/fileDistribution/2014-09/2395.zip

 

[overand]

Here's the output!

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-30 17:04:56.067
Using .txt script file at C:\Users\Geo\Downloads\SFCFixScript.txt [0]




Collect:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-30 17:06:06.497
----------------------EOF-----------------------

 

[Go The Power]

Na there is no traces of them in the registry. I found your other thread over at SF, try what Noel said and move the files out, see what SURT says.

The names do not appear inside the the COMPONENTS hive, also looking inside the MUM files there is no reference to these files.

 

[overand]

Well, I deleted the files, then ran SURT. When I try to run updates, I get "Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB2892074)." in the event log.

The CBS directory is attached here, but you can see the basic log is clean.

https://www.dropbox.com/s/1su90gjy1l9e6n4/CBS-overand-afterdelete.zip?dl=0

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-30 23:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 200
 No errors detected

 

[Go The Power]

SFC /SCANNOW

1. Click on the
   
   button. Inside the search box type in CMD
2. Right click on CMD => Choose Run as Administrator
3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
4. Please wait for this to Finish before continuing with the rest of the steps.

Convert CBS.log to CBS.txt

1. Click on the
   
   button => Inside the search box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

2. Press Enter
3. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or ge.tt

 

[overand]

As was the case with the last time I ran sfc /scannow (as admin), no dice - no integrity violations.

The previous post I made has my CBS.log inside the zip, but for simplicity's sake, I have uploaded a fresh copy of it, (renamed to .txt as requested) to dropbox for you, linked below.

https://www.dropbox.com/s/zf7crsjciw171tm/cbs.txt?dl=0

 

[Go The Power]

Looks good, not corruptions that could not be fixed and also no (f) reports.

Try and update again, if they fail please post the following log.

Windows Update Log

1. Right click on the
   
   button
2. Click on Run Inside the Run box copy and paste the following command
   cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
   
3. Please go to your desktop and attach WindowsUpdate.txt to your next post

 

[overand]

WindowsUpdate.log(txt) as requested: https://www.dropbox.com/s/lsamcf7eu3up583/WindowsUpdate.txt?dl=0

Possibly Relevant bits:

2014-10-01	21:17:09:488	7524	a66c	Handler	Installing express with source=C:\Windows\SoftwareDistribution\Download\6ab637ae1daf5afdab2ee9bceace03c8, workingdir=C:\Windows\SoftwareDistribution\Download\6ab637ae1daf5afdab2ee9bceace03c82014-10-01	21:17:13:865	7524	c444	Handler	WARNING: CBS called ResolveSource
2014-10-01	21:17:13:991	7524	c444	Handler	FATAL: CBS called Error with 0x800f081f, 
2014-10-01	21:17:13:991	7524	a66c	Handler	FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8024200d
2014-10-01	21:17:13:991	1040	c130	AU	>>##  RESUMED  ## AU: Installing update [UpdateId = {04B27F14-2812-41EE-BC43-87592A28EA28}]
2014-10-01	21:17:13:991	1040	c130	AU	  # WARNING: Install failed, error = 0x8024200D / 0x8024200D
2014-10-01	21:17:14:017	7524	a66c	Handler	:::::::::
2014-10-01	21:17:14:017	7524	a66c	Handler	::  END  ::  Handler: CBS Install
2014-10-01	21:17:14:017	7524	a66c	Handler	:::::::::::::
2014-10-01	21:17:14:019	1040	c2dc	DnldMgr	Install failed because the update {9F22D114-865C-4EC5-802F-3D0DB04C6492} was not complete; mark update as not downloaded.
2014-10-01	21:17:14:023	1040	c2dc	DnldMgr	Preparing update for install, updateId = {96DC3B6A-68CF-4934-B126-ACAE91013D3E}.201.
2014-10-01	21:17:14:025	7524	a66c	Handler	:::::::::::::
2014-10-01	21:17:14:025	7524	a66c	Handler	:: START ::  Handler: CBS Install
2014-10-01	21:17:14:025	7524	a66c	Handler	:::::::::
2014-10-01	21:17:14:026	7524	a66c	Handler	Starting install of CBS update 96DC3B6A-68CF-4934-B126-ACAE91013D3E
2014-10-01	21:17:14:028	7524	a66c	Handler	CBS package identity: Package_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0
2014-10-01	21:17:14:030	7524	a66c	Handler	Installing express with source=C:\Windows\SoftwareDistribution\Download\94ac601787cc385c9781b61895c29b6c, workingdir=C:\Windows\SoftwareDistribution\Download\94ac601787cc385c9781b61895c29b6c
2014-10-01	21:17:14:305	7524	c444	Handler	WARNING: CBS called ResolveSource
2014-10-01	21:17:14:394	7524	c444	Handler	FATAL: CBS called Error with 0x800f081f, 
2014-10-01	21:17:14:394	7524	a66c	Handler	FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8024200d
2014-10-01	21:17:14:394	1040	c130	AU	>>##  RESUMED  ## AU: Installing update [UpdateId = {9334B915-72B1-4F60-8885-4C327D7CC433}]
2014-10-01	21:17:14:394	1040	c130	AU	  # WARNING: Install failed, error = 0x8024200D / 0x8024200D
2014-10-01	21:17:14:395	7524	a66c	Handler	:::::::::
2014-10-01	21:17:14:395	7524	a66c	Handler	::  END  ::  Handler: CBS Install
2014-10-01	21:17:14:395	7524	a66c	Handler	:::::::::::::
2014-10-01	21:17:14:395	1040	c2dc	DnldMgr	Install failed because the update {96DC3B6A-68CF-4934-B126-ACAE91013D3E} was not complete; mark update as not downloaded.

Should I get the MSU files for those updates it barked about, drop 'em into the folder for SURT?

 

[Go The Power]

For the error 0x8024200D, it is rather simple to fix. Just download the update and double click on it to run it.

 

[overand]

Tentative "Solved" here - downloading & installing did work. Still have a reboot to do and such, and don't know about future updates, but I think we may be good! Sure took a while to get to this point, with my weird unknown mystery .mum/.cat files, but yay!

 

[Go The Power]

That's good news that it is working now. This one did take a little longer than normally to solve this sort of error message, but we had to be careful about removing those files.

Alex