New
#21
Okay, here is the CheckSUR log.
Okay, here is the CheckSUR log.
Here's the remaining errors....
I've got a full schedule tonight already - it'll have to wait until tomorrow before I can see about the fix protocol for theseCode:Checking Component Watchlist (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist Checking Packages (f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3 failed to get CurrentState (f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3 failed to get Visibility
Back then (I hope!)
This is going to be have to be done in stages...
Please open an Elevated Command Prompt, and run the following commands
This should create a new file on your desktop - csbreg.txtCode:REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4" >>%userprofile%\desktop\csbreg.txt REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e" >>%userprofile%\desktop\csbreg.txt REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3" >>%userprofile%\desktop\csbreg.txt .
Please compress it and upload the compressed file
I'll see what I can do then to create the fix script.
Hello again. Attached is the zipped csberg file.
Here we go with the first attempt at a fix...
I've uploaded a file - csbac.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract the contained file to your SFCFix location - which will create a SFCFix.txt file there.
Open the SFCFix location in Windows Explorer - and drag the SFCFix.txt file over onto the SFCFix.exe file - this should force SFCFix to run the file
It will create a new log file - please upload that.
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
Alright, here is the sfcfix log. I will run checksur and upload those when it is done.
Okay, here is the checkSUR log and persist log. Thanks.
Hmmm - SFCFix says that it processed the script, but there's no change in the output from the CheckSUR....
I'm going to have to think about that!
Hi there. Any more thoughts on my situation? Thanks again.
Sorry - bad weekend
I think it may be because you renamed the file, rather than extracting it - so SFCfix couldn't recognise the instructions.
Please follow the instructions in post #25 exactly, and see if anything changes.