CBS.log error points to nonexistent folder

[Arakus]

Here's the Check SUR - and Check SUR persist, just in case.

 

[NoelDP]

That is nowhere near as bad as I was expecting to see - there is a fair amount of obvious corruption in the file I have, but some of it is probably simply stuff that's been overwritten by amendments.

I've cleaned it up as much as I can - but it still causes my corruption-tester app to crash on exit (possibly because it won't unload cleanly from the registry for some reason). I've let the app's author know, and he'll work on it when he can, but it may be a few days.

There's one thing I'd love to try - but there is no way I could even think of it without extensive testing, since the potential for harm is so high. (and I don't have time this week to do much of this kind of testing )

So - back to the mundane...


I've uploaded a file - aksab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

[COLOR=black][FONT=Segoe UI]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT=Segoe UI]REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT=Segoe UI]COPY "%userprofile%\desktop\aksab\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
 
[COLOR=black][FONT=Segoe UI].[/FONT][/COLOR]

If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.


If we're lucky, this should clear all but one error in the CheckSUR log - if we're not lucky, it'll create a slew of new ones.

 

[Arakus]

Once again, here's the CheckSUR and CheckSURpersist. Fingers crossed. (Also, question - is sending the persist version actually helping?)

 

[NoelDP]

Like I said...

Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_fedee0b0e2af1d43 HKLM\Components\CanonicalData\Deployments 
Summary:
Seconds executed: 643
 Found 1 errors
  CSI Missing Deployment Key Total count: 1
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

Looks like we got lucky!
...... too much beer ( and whisky!) to be sure what to say next - come back tomorrow...

 

[Arakus]

Ummm... have you sobered up yet?

Seriously though, it's been 2 days with no reply. Are you busy or something?

 

[NoelDP]

Sorry - busy in real life as well as here!

Please upload another copy of the COMPONENTS hive - I'll have a go at it tonight.

 

[Arakus]

Here's the Dropbox link.


https://www.dropbox.com/s/7tjax2vannik78n/COMPONENTS.zip?dl=0

 

[NoelDP]

Got it - but I'm not seeing the error I was expecting to see!

I'll have to root around a bit - back later/tomorrow!

 

[Arakus]

I don't want to pressure you, but it's been 4 days since you said anything. It's OK if you're busy and need some more time, but want to be sure you haven't just forgotten.

 

[NoelDP]

Sorry about that!
I'm having a problem working out how to create the required key


This area of the registry is not one I know well, and making an error is not something I really want to do, with someone else's machine.


AH- finally found it!




I've uploaded a file - aksac.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the saved file and select Extract all...
Save it to the default location
This should create a file aksac.reg

Now open an Elevated COmmand Prompt, and run the following command..

REG LOAD HKLM\COMPONENTS C:\Windows\System32\Config\COMPONENTS

right-click on the aksac.reg file, and select Merge
Accept the warnings, - you should then get a 'Success' message.
Close all windows, and reboot.


Run another CheckSUR scan, and post the new log.

 

[Arakus]

Here's the CheckSUR and CheckSURpersist.

 

[NoelDP]

CheckSUR is happy at last!

Now the crucial test - does Windows Update work? does everything else work?

 

[Arakus]

*opens Update*

*checks for updates*

it says "Install new Windows update software"

*clicks "Install now"*

*error 800736B3*

WWWHYYYYYYYY?!

Nope, still isn't working. Everything else seems to be working fine though. Also, sorry for the stupid thing, just frustrated. (Although you're the guy doing all the work, so I imagine this is even more annoying to you.)

 

[NoelDP]

POST THE DATA
without the logs , we are just guessing.

 

[Arakus]

Knew I forgot something.

I presume you wanted me to do another Check SUR? Here they are.

 

[NoelDP]

CheckSUR looks OK
... which means that there are errors somewhere in the registry that aren't covered by CheckSUR

Unfortunately, it usually also means that a repair install of Windows won't work

I'm beginning to think of a clean install as your best option ;(

 

[ray06130]

thank