New
#21
here's the new CheckSUR and the CBS log file is .13 mb too big for the forum's limit But if it helps SFC /Scannow says that Windows did not find any integrity violations.
here's the new CheckSUR and the CBS log file is .13 mb too big for the forum's limit But if it helps SFC /Scannow says that Windows did not find any integrity violations.
The CheckSUR tool itself doesn't download anything - so if you're expecting that, it ain't gonna happen.
What you may be doing is downloading a new copy of the tool every time (all 300MB+ of it!)
Your CheckSUR result shows the following problems...
It's surprising that the SFC scan showed no problems - it should have pointed out the 'payload File Missing' errors. - we can however work around that (I hope!)Code:================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2014-11-13 08:04 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Payload File Missing 0x00000000 dfshim.dll x86_netfx-dfshim_dll_31bf3856ad364e35_6.2.7601.17514_none_42b62da05a075d19 (f) CSI Manifest Missing 0x00000002 x86_netfx-shared_registry_whidbey_31bf3856ad364e35_6.1.7601.22724_none_68fd8bc3de7d941b.manifest x86_netfx-shared_registry_whidbey_31bf3856ad364e35_6.1.7601.22724_none_68fd8bc3de7d941b (fix) CSI Manifest Missing CSI File Replaced File: x86_netfx-shared_registry_whidbey_31bf3856ad364e35_6.1.7601.22724_none_68fd8bc3de7d941b.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab (f) CSI Payload File Missing 0x00000000 schannel.dll amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22616_none_80c7d71484fe4d1b (f) CSI Payload File Missing 0x00000000 certcli.dll amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22653_none_360100f46c86223f (f) CSI Payload File Missing 0x00000000 certcli.dll x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22653_none_d9e26570b428b109 Summary: Seconds executed: 819 Found 5 errors Fixed 1 errors CSI Manifest Missing Total count: 1 Fixed: CSI Manifest Missing. Total count: 1 CSI Payload File Missing Total count: 4
I'll post a fix protocol asap - but it may not be until Saturday.
I sure hope we can work around it!
I've uploaded afile - jl5ac.zip - to my OneDrive at Noel'sOneDrive
Please downloadand save it.
Right-click onthe saved file and select Extract all...
Change the targetto C:\ and click on Extract
Close all windows(it would be a good idea to print these instructions!)
Now reboot to theRepair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced BootMenu, at the top of which should be the option'Repair my Computer'
Pick that
You'll have tolog in with your username and password.
Pick the optionto use a Command Prompt
At the prompttype
DIR C:\jl5ac
hit the enter key- if you get a 'Not Found' error try
DIR D:\jl5ac
or
DIR E:\jl5ac
The drive letterin use when you find the folder will need to be substituted (for<drive>)into the following command...
XCOPY <drive>:\jl5ac <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPYP:\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 Enterkey to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
When complete, reboot and run the CheckSUR tool again
then reboot andupload the new CBS.log and CheckSUR.log files to your reply
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2014-11-30 22:26
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 785
No errors detected
Woohoo!!! and SFC Scan now found no integrity violations. Thank you for all of your help!!! Sorry it took so long to get back to you on this!!!
It seems to be working fine! But when I started my PC up today it failed to boot 2 or 3 times, then I attempted Startup Repair (which failed) but after Startup Repair failed, it booted up fine.
Possibly a run of SFC /SCANNOW would help - if it comes up clear, post the event logs, and we'll see what we can find....
Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.