Windows Updates fail after reboot. Reverting changes.

[NoelDP]

Sorry - couldn't see it for looking!

As far as I can tell, there's nothing amiss there - which means that all the CheckSUR errors originate from the SOFTWARE registry hive.

Repairing this manually is a royal pain - but possible.
There is a tool available to assist, but I'm not an expert in its use, so I'm going to call for assistance, but it may take a couple of days for the cavalry to come charging over the hill - don't run away!

 

[RFog80]

Sounds good. Thank you!

 

[RFog80]

Not sure if this helps but I figured I might try to uninstall IE 11 and reinstall since the one update was related to it. IE11 wont uninstall and most likely has to do with the software registry errors also.

 

[Kaktussoft]

(f) CBS Registry Error 0x80070002 Package_2_for_KB2563894~31bf3856ad364e35~amd64~~6.1.1.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_2_for_KB2563894~31bf3856ad364e35~amd64~~6.1.1.1 failed to get Visibility
(f) CBS Registry Error 0x80070002 Package_2_for_KB2645640~31bf3856ad364e35~amd64~~6.1.1.0 failed to get CurrentState
(f) CBS Registry Error 0x80070103 Package_2_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2 failed to get owner for package.
(f) CBS Registry Error 0x80070002 Package_2_for_KB2861855~31bf3856ad364e35~amd64~~6.1.1.0 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1 failed to get Visibility
.
.
.
.
Some permission problem on COMPONENTS hive? I'm not an expert on it. Follow @NOELDP's instructions.

 

[NoelDP]

The problem is with entries in the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing part of the registry (The SOFTWARE hive).
The permissions on this are strict - and the hive is always in use by the OS so it's difficult to make changes without either a tool for the job or a lot of sweat and worry.

Hopefully, I'll learn enough from how the cavalry performs to be able to do the job myself next time!

 

[RFog80]

The problem is with entries in the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing part of the registry (The SOFTWARE hive).
The permissions on this are strict - and the hive is always in use by the OS so it's difficult to make changes without either a tool for the job or a lot of sweat and worry.

Hopefully, I'll learn enough from how the cavalry performs to be able to do the job myself next time!

Wow. At least it's narrowed down. Thank you so much for your help and hopefully we can resolve this.

 

[Kaktussoft]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
has explictly set permissions (so not inherited):
TrustedInstaller: FULL CONTROL
Users, SYSTEM, Administrator: Read

So easy to set in my opinion.

All its subkeys inherit the permissions. At least on my computer all subkeys have inherited these permissions.

@RFOG80: Please run regedit and goto key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
right click on "Component Based Servicing" ->Permissions->Advanced. Post screenshot.

 

[RFog80]

@RFOG80: Please run regedit and goto key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
right click on "Component Based Servicing" ->Permissions->Advanced. Post screenshot.

Here you go:

 

[Kaktussoft]

Everyone??? I don't have that. I expected this:
TrustedInstaller: FULL CONTROL
Users, SYSTEM, Administrator: Read

Here my screenshot (sorry in Dutch). Any idea why security is gone on that key? It's not the source of the problem... you grant more access as usual.

 

[RFog80]

hmm... should I change it or wait?

 

[NoelDP]

Please wait. It seems you may have a number of problems.

 

[RFog80]

Great... ok thanks

 

[Kaktussoft]

hmm... should I change it or wait?

Wait for NoelDP. Don't change anything.

The subkeys of that registry key (about 10): permissions->advanced. All permissions are "inherited" ?

 

[NoelDP]

There are very few places in Windows where 'Everyone' should be mentioned at all - let alone with Full permissions.
The permissions shown would make repair easier - but should not exist in the first place and potentially indicate that the machine has been 0wned at some point in the past.
I'm beginning to think in terms of at least a repair install (if not a clean one)

 

[RFog80]

Ok... What's the easiest way to do the repair? I don't have a home premium x64 disc.

 

[NoelDP]

Wait and see what the cavalry has to say first

 

[RFog80]

Wait and see what the cavalry has to say first

Noel... Have you heard anything?

 

[Kaktussoft]

home premium x64 disc ENGLISH: X17-58997.iso Burn it.
Source: Windows 7 Direct Download Links, Official Disk Images from Digital River

http://www.sevenforums.com/tutorials/3413-repair-install.html
You have a valid product key? See sticker on case of laptop

 

[RFog80]

home premium x64 disc ENGLISH: X17-58997.iso Burn it.
Source: Windows 7 Direct Download Links, Official Disk Images from Digital River

http://www.sevenforums.com/tutorials/3413-repair-install.html
You have a valid product key? See sticker on case of laptop

Thank you! Yes I have valid key on the case. Am I still waiting on the cavalry?

 

[NoelDP]

Tom may be away for a few days - I've not had any response from him yet

Up to you!