Security Update for Windows could not be installed

[JackNaylorPE]

Been ignoring this box for a while now and I'll try one more attempt at a fix before wiping and reinstalling. It started when for the 1st time ever, Windows started installing updates w/o my initiating same. I looked up the error, saw several folks afflicted, followed MS advice on technet and support forums and after several efforts just gave up as i didn't have the time.

These are the last 4 entries in the Windows setup log

Windows update "Security Update for Windows (KB2871997)" could not be installed because of error 2147942487 "The parameter is incorrect." (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\JackN\Desktop\Windows6.1-KB2871997-v2-x64.msu" ")

Windows update could not be installed because of error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "R:\Download\Microsoft\SystemReadinessTool\Windows6.1-KB947821-v33-x86.msu" ")

Windows update could not be installed because of error 2147943623 "The operation was canceled by the user." (Command line: ""C:\Windows\system32\wusa.exe" "R:\Download\Microsoft\SystemReadinessTool\Windows6.1-KB947821-v33-x64.msu" ")

Windows update could not be installed because of error 2147944018 "Another installation is already in progress. Complete that installation before proceeding with this install." (Command line: ""C:\Windows\system32\wusa.exe" "R:\Download\Microsoft\SystemReadinessTool\Windows6.1-KB947821-v33-x64.msu" ")

And last ditch ideas before I dedicate a weekend to rebuilding this OS / system. It serves as file server on a SOHO network.

 

[matts6887]

I know this may sound pretty simple; but Im not sure if you have tried it or not; have you tried rebooting this server and then trying to install the updates? Sometimes it only takes something as simple as rebooting to refresh everything and enables windows to close out any processes that are open that arent needed so you can hopefully try and run those update(s) again. If you try that and that does nothing; its possible you may have a corrupt windows update folder in which case you might be able to try a system repair off the windows disc if you have one somewhere and that may help. If you try both things and still get nowhere with it; post back and we can go from there.

 

[gregrocker]

Are there updates queued with a ! mark on the Start menu Shutdown button? Sometimes these can only be installed by Shutting Down.

You can reset Windows Update components

System Update Readiness Tool fixes Windows Update errors in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008

Windows Update Posting Instructions - Windows 7 Help Forums

 

[JackNaylorPE]

Matts:

This isn't a true "server" in that it manages apps and licenses and is up 24/7. It's a simple "file server" for a SOHO (small office / home office) meaning that the users of the 4 office boxes keep all their files on it for the business and the home folks backup their stuff there. It runs Win 7 64 pro not a server OS. It's used as a CAD Workstation during the day and at night I been known to blast a few aliens / bad guys / monsters.

I have tried:

-Installing the update manually
-Installing from Safe Mode
-System Repair from Backup
-Windows Repair fro USB / DVD
-In place upgarde
-Run SFC SCan Now
-Reset Windows Update Componnets
-Chkdsk completes with no indication of problems

-scannow worked the first time I did it ..... now says Windows Resource Protection could not perform the requested operation


Greg

I have tried the System Update Readiness Too ... it's mentioned in the last 3 error messages in 1st post

sfc /scannow created a 187 KB file that mostly says its moving things and ignoring directories with multiple owners but after rebooting it went to 1,162 KB.

The System Readiness Tool created a 65KB file w/ the following summary:

Summary:
Seconds executed: 399
Found 190 errors
Fixed 165 errors
CSI Manifest Missing Total count: 2
CSI Catalog Missing Total count: 1
Fixed: CSI Catalog Missing. Total count: 1
CSI Missing Component Key Total count: 31
Fixed: CSI Missing Component Key. Total count: 31
CSI Corrupt Component Keyform Total count: 1
CSI Missing Identity Total count: 31
Fixed: CSI Missing Identity. Total count: 31
CSI Corrupt Identity Total count: 5
Fixed: CSI Corrupt Identity. Total count: 3
CSI Missing C Mark Total count: 57
Fixed: CSI Missing C Mark. Total count: 57
CSI C Mark Deployment Missing Total count: 20
CSI F Mark Missing Total count: 42
Fixed: CSI F Mark Missing. Total count: 42

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_ar-sa_2eb37ca44d9f.manifest
winsxs\manifests\amd64_microsoft-windows-networkprojection_31bf3856ad364e35_6.1.7600.16385_no4e_3fbc74d90a6e33f8.manifest

This is all I can add at this point as I'm on my lappie

 

[gregrocker]

Jack, I asked an Updates expert to look at this.

I'd have cbs and other requested logs ready from Windows Update Posting Instructions - Windows 7 Help Forums

Of course if you have less than a perfect install to begin with, you can enjoy Win7 perfect performance for the first time by following closely the steps for Clean Reinstall Windows 7

 

[NoelDP]

If we strip the summary down to the remaining errors, we get...

Found 190 errors
Fixed 165 errors
CSI Manifest Missing Total count: 2
CSI Corrupt Component Keyform Total count: 1
CSI Corrupt Identity Total count: 2
CSI C Mark Deployment Missing Total count: 20

I need to see the whole CheckSUR log file please, as well as the SFC data (you didn't mention if it found errors and fixed them?) - and also the actual COMPONENTS hive, as it appears to have been corrupted.
The fact that there were 5 corrupted Keyforms and a couple of corrupt Identities could indicate that there are problems with the machine's RAM.


I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.


Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[JackNaylorPE]

Jack, I asked an Updates expert to look at this.

I'd have cbs and other requested logs ready from Windows Update Posting Instructions - Windows 7 Help Forums

Of course if you have less than a perfect install to begin with, you can enjoy Win7 perfect performance for the first time by following closely the steps for Clean Reinstall Windows 7

Yes, as indicated in the first post, this was my last attempt to potentially avoid this step. Taking this box down essentially put me outta business until it's back up as no one has access to their files.

 

[JackNaylorPE]

I need to see the whole CheckSUR log file please, as well as the SFC data (you didn't mention if it found errors and fixed them?) - and also the actual COMPONENTS hive, as it appears to have been corrupted.
The fact that there were 5 corrupted Keyforms and a couple of corrupt Identities could indicate that there are problems with the machine's RAM.

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.


Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

-The files are already up on one drive from when I tried to get help from MS. I just added the components file which is where I suspect the problem is and the CBS folder
https://onedrive.live.com/?cid=a95c5fa81fd1c5d5&id=A95C5FA81FD1C5D5!105

-RAM passes 12 hour runs on MemTest 86+

- I did see that there is a new version on the Update Readiness Tool since I had the problem.... the files on the one drive site are from version 33.... ran v34 and it completed. It completed and ran after which I ran Windows Update. Pror to this, it gave an error after about a minute..... it;'s now been searching for about 10 minutes so I will report back when done.

- OK Ran the Update tool a 2nd time just to make sure and after rebooting got a popup to update Defender. Took quite a while but it finally finished. Ran Windows Update again and got the familiar 80070246 error after quite a while.

- Next Tried the MS FixIt tool KB971058 .... It completed saying that It did not detect any problems.

- Found this which again reinforces the "feeling" that it's the components file ... this apparently required manual editing of the components file.
[SOLVED] Windows Update nor working (Error code 80070246) - Sysnative Forums

I also looked at a solution using AIK but users who tried it got nowhere so didn't bother

Hope this is enough....

On a side note .... I have a vague recollection of trying this already and not being able to get anywhere .... I installed Windows via UEFI USB method, is an in place upgrade a potential solution using the original DVD ?

Much thx for your assistance.

 

[NoelDP]

You have rather a lot of registry corruption...

Key:   HKEY_LOCAL_MACHINE\23182350\CanonicalData\Catalogs\14b6d24d635e00aa25be1dbfe26ddb1cd0035a95705b3735b69334d3d97fa502
Value: c!cc9106f3867..638d5®45385_31bf3856ad364e35_6.1.7601.17857_6a805db4e223abbd
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\CanonicalData\Deployments\462b2da2a76..3f651305909_31bf3856ad364e35_6.1.7601.22012_4f4dcd83519ab9e5
Value: p!CBS_packagÜ_4_for_kb2698365~31bf3856ad364e35~amd64~~6.1.1.2.2698_607bec10eí6d9901
Data:  hex:4E,00,00,00,01,00,00,00,50,61,63,6B,61,67,65,5F,34,5F,66,6F,72,5F,4B,42,32,36,39,38,33,36,35,7E,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7E,61,6D,64,36,34,7E,7E,36,2E,31,2E,31,2E,32,2E,32,36,39,38,33,36,35,2D,33,36,5F,6E,65,75,74,72,61,6C,5F,4C,44,52,32
Key:   HKEY_LOCAL_MACHINE\23182350\CanonicalData\Deployments\c156ea67800..ab834dde01d_31bf3856ad364e35_6.1.7601.22012_087fe7bbbcf4a14b
Value: p!CBS_package_4_for_kb269836î~31bf3856ad364e35~amd64~~6.1.1.2.2698_7666a1ab741d8023
Data:  hex:90,00,00,00,01,00,00,00,50,61,63,6B,61,67,65,5F,34,5F,66,6F,72,5F,4B,42,32,36,39,38,33,36,35,7E,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7E,61,6D,64,36,34,7E,7E,36,2E,31,2E,31,2E,32,2E,32,36,39,38,33,36,35,2D,33,34,5F,6E,65,75,74,72,61,6C,5F,4C,44,52,33
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_3a591bb58d8027941e28a3d29744778e_31bf3856ad364e35_6.1.7601.17857_none_afd056e555609acd
Value: c!3a591bb58d8..3d29744778e_3Èbf3856ad364e35_6.1.7601.17857_afd056e555609acd
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_c156ea678006708cf9919ab834dde01d_31bf3856ad364e35_6.1.7601.22012_none_087fe7bbbcf4a14b
Value: Ⅳㅣ㘵慥㜶〸⸰愮㡢㐳摤づ搱㍟戱㍦㔸愶㍤㐶㍥張⸶⸱㘷㄰㈮〲㈱た㝖敦户扢晣愴㐱
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-basic-misc-tools_31bf3856ad364e35_6.1.7600.16385_none_7351a917d91c961e
Value: c!windowsfoundation_31bf3856ad364e35_6.1.7601.17514_Å15fdfe2a739474c
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-d..-mmc-usersandgroups_31bf3856ad364e35_6.1.7601.17514_none_62031a1b9887a2a0
Value: c!windowsfouÅdation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_ar-sa_2eb37ca44d9f
Value: identity
Data:  Microsoft-Windows-LSA-MSPrivs.Resources, Culture�ar-SA, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35,ProcessorArchitecture=amd64, versionScope=NonSxS
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22465_none_04c503168cb026a0
Value: Ⅶ獫捥歰⹧祳
Data:  k
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-m..ac-ado-ddl-security_31bf3856ad364e35_6.1.7601.17857_none_102c632b571fc1ba
Value: c!cdÚ8c3f548b..495af7fcfc2_31bf3856ad364e35_6.1.7601.17857_5873d815db2c93f1
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-networkprojection_31bf3856ad364e35_6.1.7600.16385_no4e_3fbc74d90a6e33f8
Value: identity
Data:  Microsof,-Windows-NetworkProjection, Culture=neutral, Version=6.1.7600.1�385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amdW4, versionScope=NonSxS
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_microsoft-windows-s..c-standardfx_plugin_31bf3856ad364Q35_6.1.7600.16385_none_48b861ab00668513
Value: 摩湥楴祴
Data:  Microsoft-Windows-Sonic-StandardFX_Plugin, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\amd64_netfx-mscorsec_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_9e8b6c6f9c9684f3
Value: c!windowsfoundation_31bf3856ad364e35_6.1.7601.17514_ý15fdfe2a739474c
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7600.16385_none_1c9a3ec1e01c684b
Value: c!windowsfoundation_31bf3856Âd364e35_6.1.7601.17514_615fdfe2a739474c
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\wow64_microsoft-windows-p..ll-preloc.resources_31bf3856ad364e35_6.1.7600.16385_en-us_27fbee50ef7f6588
Value: f!about_hashÞtables.help.tx_9db6809a4822a41d
Data:  a
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\x86_microsoft-windows-m..ac-ado-ddl-security_31bf3856ad364e35_6.1.7601.22012_none_b4bd7ad2b7c43519
Value: c!c156ea67800..ab834dde01d_31bf3856aÓ364e35_6.1.7601.22012_087fe7bbbcf4a14b
Data:  
Key:   HKEY_LOCAL_MACHINE\23182350\DerivedData\Components\x86_netfx-webhightrust_config_b03f5f7f11d50a3a_6.1.7¯00.16385_none_74c08aa44dd33c76
Value: iden+ity
Data:  NetFx-WEBHIGHTRUST_CONFIG, Culture=neutral, Version=6.1.i600.16385, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitectu�e=x86
 
Operation Completed!

(I don't know how well that will survive HTML... - better than I expected, but it's still much worse than it looks.)

I'm going to have to dive in with a hex editor and try and remove/repair all the problematic entries, and then see where we get to.

It may take a while - because there will probably be a lot that the scanner I used isn't showing.

I'll try and get back to you tomorrow with a new version for testing.

 

[JackNaylorPE]

Much thx.... the thing that gets me is that I never let Windows do anything automatically. I prefer that I install updates manually and if Windows update says I need 17, I generally do them in smaller groups and always after backing up registry before hand.

This time I was running AutoCAD most of the day.... went to shut down and Windows on it's own decided to install updates. Apparently this update did this to a lot of people as their support forums were clogged with people who all had the same problem with the same update (KB287119970

 

[NoelDP]

There have been a few 'dodgy' updates lately - but as far as I can see, none of them have involved faulty code. The problems have involved unexpected side-effects from other installed programs. (still inexcusable, but ....)

All the errors I've seen so far tend to indicate a problem with flaky hardware at come point in the chain - either RAM, HD, Processor, or motherboard. I still tend to favour RAM as the prime cause (although a RAM problem itself may possibly be caused by flaky power supply).

I should be able to post your 'new' components hive in the morning.

 

[NoelDP]

I've uploaded a file - jneaa.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.

[/FONT][/COLOR]
[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\jneaa\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"] [/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"].

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.

 

[JackNaylorPE]

There have been a few 'dodgy' updates lately - but as far as I can see, none of them have involved faulty code. The problems have involved unexpected side-effects from other installed programs. (still inexcusable, but ....)

All the errors I've seen so far tend to indicate a problem with flaky hardware at come point in the chain - either RAM, HD, Processor, or motherboard. I still tend to favour RAM as the prime cause (although a RAM problem itself may possibly be caused by flaky power supply).

I should be able to post your 'new' components hive in the morning.

Motherboard - Asus Maximus VI Formula
RAM - 16GB Mushkin DDR3-2400 CAS 10 (10-12-12-28)
PSU - Seasonic X-1250
SSD - (2) Samsung 840 Pros
SSHD - (2) Seaagte SSHDs 2TB
GFX - (2) Asus 780

Let me suggest another possible cause. The Asus Z87 / Z97 series are afflicted by a BIOS Clock Freeze Bug. When using certain BIOS functions (i.e. saving / restoring BIOS profiles) or a OC crash failure, the BIOS clock freezes. This I believe is troublesome because say it is Feb 1 when it freezes and you don't boot for 2 weeks, doing your last WU on February 13. The PC has a system date of February 13 at the time of the WU.... now you reboot and the machine is sent back in time to Feb 1 cause the BIOS clock is frozen there. You do anither WU on Feb 4, and its like.... WTH ? .... I see system updates 9 days in the future ?

Back after completing your instructions.....

Ran the SURT and when completed told me to run WU ..... but looking at the file, it still says 20 errors so I expected it not to work .... checking I got error message 8007370B

New files is up on onedrive

https://onedrive.live.com/?cid=a95c5fa81fd1c5d5&id=A95C5FA81FD1C5D5!105

CheckSUR-02-27.log

 

[NoelDP]

That's not too bad actually most of the errors are simple bitflips rather than bad files.

Please upload the new COMPONENTS file, and I'll get to work on it when I have the time.

 

[JackNaylorPE]

Again, Muchos Grassyass ....

1. Is there a source of information with which I could educate myself on the process of analyzing and repairing this type of error ?

2. Does the BIOS Clock Freeze thing and the resulting Windows Update mixup of WU trying to do an update on when the system thought it was Feb 2 when it saw files dated Feb 6 and actual date was Feb 14 a likely cause of the problem ?

3. Recently the system started "losing" some of the drives connected to the system. They just disappear tho a rescan from Disk Manager always "finds them". Is this possibly a result of this problem ? It never loses the Boot Drive, mostly the 1st SSD, once the 2nd, once the 2nd SSD

.... will be back in a bit w/ the file

 

[NoelDP]

Those symptoms sound more to me as if they may be the result of failing hardware - possibly low voltages on the power supply? Check the voltages using something like Speccy and see if they show anything.

 

[JackNaylorPE]

File is up.

https://onedrive.live.com/?cid=a95c5fa81fd1c5d5&id=A95C5FA81FD1C5D5!105

Power Supply is 10.0 performance and build quality jonnyguru rated and I routinely check bus voltages

Right Now:

+5V = 5.040v
+3.3 = 3.328v
+12 = 12.096v

 

[NoelDP]

OK - I think I got all the bitflips that show...


I've uploaded a file - jneab.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.

[/FONT][/COLOR]
[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\jneab\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"] [/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"].

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.

 

[JackNaylorPE]

I put the system through heavy stress testing last night..... 3 and 5 volt rails didn't budge..... 12 v dropped to 11.88

Downloading now

You are **THE** man

SUR log says no errors detected

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-03-03 12:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 426
No errors detected
====================================

74 important updates to be installed .... Yahooooooo

Closest relative I have to you are in Ireland but if ya get close, I'll make sure a nite at the pub is on them !

EDIT: All 74 updates installed.

 

[NoelDP]

It's nice when a plan comes together

Whereabouts in Ireland? <eg > I may be able to do it by proxy!

Good luck