I recently found that the above update had failed installation several times. I did various searches on Windows Update problems and obtained a CBS file (attached.) My intention was to find the corrupted files that the CBS file indicated - There were four ( pdmproxy100.dll, d2d1.dll.mui,Wimprovider.dll and ATL90.dll) - and replace these with the same files from another PC running the same Windows 7 professional, I find that there are multiple instances of these four files in my windows folder and I am unsure how to proceed of even if I am going in the right direction. I would very much appreciate any advice.
Thanks & Regards
Jim
PS your SFSX fix doesn't detect any problems.
PPS I seem to have a problem attaching the CBS.log file I tried under "Manage Attachments" it has opened but I can't see if it has attached itself to this post.
PS your SFSX fix doesn't detect any problems.
PPS I seem to have a problem attaching the CBS.log file I tried under "Manage Attachments" it has opened but I can't see if it has attached itself to this post.
File is to big, there's a limitation in file size upload, use dropbox or one drive online storage then post a link... Also what was the error code that the install gave you, you can check event viewer for details..
Hi and welcome to Sysnative. I do see the corruption but would like one more log to review before providing a fix. Please do the following.
Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Thank you very much for your reply. i had thought that I had run the SUR a couple of time before but gave up after the progress bar appeared to stall for several minutes! However I have done what you described without incident and here is the Log file:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-06-02 15:51
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-MiniLP~31bf3856ad364e35~amd64~sk-SK~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~sk-SK~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~sk-SK~7.1.7601.16492.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_3_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3006226_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Base-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
Summary:
Seconds executed: 432
Found 18 errors
CSI Manifest All Zeros Total count: 3
CSI Manifest Failed Catalog Check Total count: 3
CBS MUM Corrupt Total count: 4
CBS Catalog Corrupt Total count: 8
No problem. OK, let's get some of the corruption fixed. Please do the following.
Step#1 - Fix Corrupt Files 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.
Please download the attached file, Packs.zip and save this to your Desktop.
Right-click on the file and select Extract All...
Tick the box labelled Show extracted files when complete then click Extract
A window will open showing two folders, Manifests and Packages
Open the Manifests folder and copy the files into the following folder (if there are any files). If the Manifests folder doesn't exist within Winsxs you will need to create it. C:\Windows\Temp\CheckSur\Winsxs\Manifests
Open the Packages folder and copy the files into the following folder (if there are any files). If the Packages folder doesn't exist within Servicing you will need to create it. C:\Windows\Temp\CheckSur\Servicing\Packages
Run the System Update Readiness Tool (SURT) again.
When the SURT finishes installing, zip up and attach the following log file: C:\Windows\Logs\CBS\CheckSUR.log
It looks as though the operation was successful. I carried out your instructions and the log file (see below) indicates that the 18 errors have been fixed. In addition I have now been able to apply the update!
I am very much impressed and obliged for your help and will be making a donation
