New
#11
The latest log files, if I'm reading it right looks like your bitflip fix worked. 15 other errors unresolved, mostly CSI payload.
The latest log files, if I'm reading it right looks like your bitflip fix worked. 15 other errors unresolved, mostly CSI payload.
Didn't quite catch all the errors
I'll post a new fix soon, then we can work on the other errors.Code:ummary: Seconds executed: 914 Found 18 errors Fixed 3 errors CSI Manifest Missing Total count: 4 CSI Catalog Missing Total count: 1 Fixed: CSI Catalog Missing. Total count: 1 CSI Missing Deployment Key Total count: 4 CSI Missing Identity Total count: 1 Fixed: CSI Missing Identity. Total count: 1 CSI Missing C Mark Total count: 1 Fixed: CSI Missing C Mark. Total count: 1 CSI Payload File Missing Total count: 7 Unavailable repair files: winsxs\manifests\amd64_c0fdc861933d0947db648ac369548ced_31bf3856ad364e35_11.2.9600.16476_none_ab1e0a0216b79505.manifest winsxs\manifests\amd64_0b4881e432545abdfb74fbf922bdd2af_31bf3856ad364e35_11.2.9600.16476_none_62b08cc68c2f457b.manifest winsxs\manifests\x86_microsoft-windows-i..rityzones.resources_31bf3856ad364e35_11.2.9600.17239_en-us_f4d1b46a3e1920f7.manifest winsxs\manifests\amd64_7b330273a4d9b11bf117ccc7fd7ed608_31bf3856ad364e35_11.2.9600.16476_none_c8d8daed6e2bb466.manifest
I've uploaded a file - sfwac.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sfwac in the same place.
Open this folder - there should be one folder inside it (Manifests)
Copy the content of the Manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
Great! - CheckSUR is as happy as it's going to get...
Now we just have to deal with the payload files.Code:Summary: Seconds executed: 888 Found 11 errors Fixed 4 errors CSI Manifest Missing Total count: 4 Fixed: CSI Manifest Missing. Total count: 4 CSI Payload File Missing Total count: 7
First, let's check that they are the only ones...
Please do another SFC /SCANNOW, and post the new CBS.log file (compressed!)
Here is the CBS.log compressed.
SFC found these problems...
... which fits rather nicely with the ones that CheckSUR found...Code:Line 214417: 2015-07-13 00:36:42, Info CSI 000003ee [SR] Repairing 2 components Line 214418: 2015-07-13 00:36:42, Info CSI 000003ef [SR] Beginning Verify and Repair transaction Line 214419: 2015-07-13 00:36:42, Info CSI 000003f0 [SR] Cannot repair member file [l:38{19}]"TS_Connectivity.ps1" of Microsoft-Windows-WindowsUpdateDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing Line 214420: 2015-07-13 00:36:42, Info CSI 000003f1 [SR] Cannot repair member file [l:30{15}]"DiagPackage.dll" of Microsoft-Windows-WindowsUpdateDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing Line 214421: 2015-07-13 00:36:42, Info CSI 000003f2 [SR] Cannot repair member file [l:38{19}]"DiagPackage.diagpkg" of Microsoft-Windows-WindowsUpdateDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing Line 214422: 2015-07-13 00:36:42, Info CSI 000003f3 [SR] Cannot repair member file [l:36{18}]"Amd64\hpf2200t.exp" of prnhp003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing Line 214423: 2015-07-13 00:36:42, Info CSI 000003f4 [SR] Cannot repair member file [l:36{18}]"Amd64\hpf2100t.exp" of prnhp003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing Line 214424: 2015-07-13 00:36:42, Info CSI 000003f5 [SR] Cannot repair member file [l:36{18}]"Amd64\hpf2100t.gpd" of prnhp003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing Line 214425: 2015-07-13 00:36:42, Info CSI 000003f6 [SR] Cannot repair member file [l:36{18}]"Amd64\hpf2100t.xml" of prnhp003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
I'll post a fix protocol laterCode:f) CSI Payload File Missing 0x00000000 Amd64\hpf2200t.exp amd64_prnhp003.inf_31bf3856ad364e35_6.1.7600.16385_none_2fd781a76c9dcc13 (f) CSI Payload File Missing 0x00000000 Amd64\hpf2100t.exp amd64_prnhp003.inf_31bf3856ad364e35_6.1.7600.16385_none_2fd781a76c9dcc13 (f) CSI Payload File Missing 0x00000000 Amd64\hpf2100t.gpd amd64_prnhp003.inf_31bf3856ad364e35_6.1.7600.16385_none_2fd781a76c9dcc13 (f) CSI Payload File Missing 0x00000000 Amd64\hpf2100t.xml amd64_prnhp003.inf_31bf3856ad364e35_6.1.7600.16385_none_2fd781a76c9dcc13 (f) CSI Payload File Missing 0x00000000 TS_Connectivity.ps1 amd64_microsoft-windows-w..owsupdatediagnostic_31bf3856ad364e35_6.1.7600.16385_none_d8bc9f93971275e0 (f) CSI Payload File Missing 0x00000000 DiagPackage.dll amd64_microsoft-windows-w..owsupdatediagnostic_31bf3856ad364e35_6.1.7600.16385_none_d8bc9f93971275e0 (f) CSI Payload File Missing 0x00000000 DiagPackage.diagpkg amd64_microsoft-windows-w..owsupdatediagnostic_31bf3856ad364e35_6.1.7600.16385_none_d8bc9f93971275e0
I've uploaded a file - sfwad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\sfwad
hit the enter key - if you get a 'Not Found' error try
DIR D:\sfwad
or
DIR E:\sfwad
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\sfwad <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
This is exciting, after running the sfc scannow, received message "Windows Resource Protection found corrupt files and successfully repaired them". The CBS log is now just 685KB vs almost 50MB.
If you see no other errors do you have any suggestions for me to avoid getting in this mess again? I have removed the RAM I had added and presume it would be smart to save a Restore Point here but not sure what else I should do.
Also please let me know how I can send you some pub money. It won't pay for your time but will at least let you enjoy a few pints.
Great! - There's no errors in the background of that log, either.
Do a Check for Updates - attempt to install ONLY the oldest update found - what happens?
If it goes in OK, try any others rem.aining.
If it fails, post the C:\Windows\windowsupdate.log file