New
#51
alright well i guess ill be back in 12 or so hours (thats how long it takes for me to do a virus scan, at any rate)
alright well i guess ill be back in 12 or so hours (thats how long it takes for me to do a virus scan, at any rate)
CHKDSK just finished, said the volume was clean.
gonna boot into safe mode so i can run SFC, ill be back with the files you asked for in a few minutes.
sfc scannow saying the same thing it's been saying the past times i've ran it - there's corrupt files but can't fix them.
Code:Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of th em. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log C:\Windows\system32>
Here's the SFC errors...
There are a few odd entries in the event logs - which I'll come to later.Code:Line 29870: 2015-07-04 09:38:54, Info CSI 00000381 [SR] Repairing 3 components Line 29871: 2015-07-04 09:38:54, Info CSI 00000382 [SR] Beginning Verify and Repair transaction Line 29874: 2015-07-04 09:38:54, Info CSI 00000384 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 29877: 2015-07-04 09:38:54, Info CSI 00000386 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 29880: 2015-07-04 09:38:55, Info CSI 00000388 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 29883: 2015-07-04 09:38:55, Info CSI 0000038a [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
I'll post a fix protocol for these error later (prolly tomorrow, now)
hey, sorry for not checking back on this thread in a while - real life things to attend to... any news on that fix you were working on?
Sorry about that - I've had my own frustrations as well!
I've uploaded a file - fcfaa.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:\fcfaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\fcfaa
or
DIR E:\fcfaa
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\fcfaa <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
Last edited by NoelDP; 28 Jul 2015 at 11:57. Reason: correct typo in command
here's the log.
Great! the only remaining errors are from KB3022345, which can be ignored.
Do a check for updates, and attempt to install only the oldest found update.
If it goes in OK, try the rest
If it fails, post the C:\Windows\windowsupdate.log file.
KB3033890 already borked, and i didn't even restart my computer yet - it gave me error 80246007. here's the log.
still got 2 other hidden ones i haven't tried yet, from the topic i mentioned way back in OP.
Reboot and try again - if you get the same error message, try this...
Open an Elevated Command Prompt, and run the following commands
then reboot, and try Windows Update again.Code:REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS REG DELETE HKLM\COMPONENTS /V PendingRequired .