[SOLVED] Win7x64 SP1 - Can't install Updates - Code 8000FFFF - This one is kicking my tail!

[dennisharrison]

CBS.zip for this system:
CBS.zip

I inherited this mess of a system - it runs a paperless office product called Intact which connects between Quickbooks & a Sharp MFP. Intact recently needed an update, which broke the MFP functionality (which is called OSA and runs as an IIS site using .Net 3.5 in a classic application pool).

After spending 6 hours on it yesterday they said we need to uninstall & reinstall IIS and migrate to fix it. This system hadn't run Windows update since install?

When trying to remove the components from Windows features, I realized I couldn't add or remove any of those components and set out to do some SFC scan now (no issues), and system updates to relieve the issue. After installing some updates, we're now at this system state - and I've run out of blue links on Google.

Never, have I run into an issue like this that couldn't be solved with 2 days of study and careful application. This is just out of my depth - I can't even find proper info on what these errors even mean (assumption is that the component hive has orphaned keys?).

Please, let me know what else to try - I'm also extremely interested in the most verbose information possible with regard to this, if you're so inclined to drop some knowledge on me :)

Thanks for looking, and thank you for your time!

 

[Sysnative Windows Update]

Hi!

Please install this, reboot your machine if needed and retry updates: http://download.windowsupdate.com/d..._b9df2405e7e034e3ffda160fff99a36ab96ba187.msu

 

[dennisharrison]

Hey Softwaremaniac - thank you!

"The update is not applicable to your computer" is the message I receive when trying to install this update.

 

[Sysnative Windows Update]

I'm seeing some registry issues. Will take care of this on Monday when I return.

 

[Sysnative Windows Update]

Hi!

Please do the following:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

 

[dennisharrison]

Roger that, here you go - thanks again :)

components

What software are you using to dig through the logs - is it anything available to download?

 

[Sysnative Windows Update]

Thanks. I'm using Notepad and search for anything interesting. Nothing fancy.

 

[Sysnative Windows Update]

Hi!

Please do the following to help me pinpoint the error:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as the it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[dennisharrison]

WOW - that's a huge log file (12GB)!

Both logs are included in this .zip

procman_CBS.zip

 

[Sysnative Windows Update]

Thanks.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[dennisharrison]

Wow, FAST reply - I'm dying to know how you found the needle in the haystack so quickly :)

 

[Sysnative Windows Update]

Please run System Update Readiness Tool again and attach CheckSUR.log.

 

[dennisharrison]

Thank you much, here is CheckSUR.log & CheckSUR.persist.log (you didn't ask for it - but it's a much larger file, so sending it in case).

CheckSURwPersist.zip

 

[Sysnative Windows Update]

CheckSUR.persist.log logs everything, CheckSUR logs just the most recent run

Please get me another ProcMon capture.

 

[dennisharrison]

Here you are!

Logfile2.zip

P.S.
Where did you get the string for?:

HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_none_cae5bf71393e136f\v!7.1.7601.18325|InstallMapMissingComponentKey

 

[Sysnative Windows Update]

From within the ProcMon log.

Is the following folder present?

C:\Windows\winsxs\amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_6.1.7601.22949_none_fdcdd107758fe420

 

[dennisharrison]

Nope!

The most similar directory is:
amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_6.1.7601.17514_none_fd5fb3a45c5e60ba

 

[Sysnative Windows Update]

Let's add it in!

SFCFix Script

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 SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

 

[dennisharrison]

Excellent, I'm reading the related logs and things are getting less fuzzy for me Thank you again!

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-12 18:54:22.106
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_6.1.7601.22949_none_fdcdd107758fe420.

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_6.1.7601.22949_none_fdcdd107758fe420\WMPhoto.dll to C:\Windows\WinSxS\amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_6.1.7601.22949_none_fdcdd107758fe420\WMPhoto.dll.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2019-08-12 18:54:28.131
Script hash: WQIQbi+IXKpQM6qzfHMOWIsBbRrerowZKzVizkpOKgI=
----------------------EOF-----------------------

 

[dennisharrison]

- Curious -
Where did you get the proper WMPhoto.dll (or does the file contents/checksum not matter)?

Do you have a repository of all the updates per architecture / windows version?