Windows Update: problems with installing some security updates

[AWS]

From William MWP

 

I have tried to resolve a problem with Windows Update but, so far, without success and would appreciate some assistance. The relevant information is as follows:-

 

Dell Laptop Studio 1745 computer. Windows7 Home Premium. Version 6.1.7601 Service Pack 1 Build 7601. Type X64 based PC.

 

On the 12 October the McAfee security programme kept indicating that my computer was not protected and I was unable to recover it; shortly afterwards the computer crashed irretrievably and had to be returned to Dell who installed a new motherboard. On return

(17 October) it worked normally but I was still getting security messages that my computer was not protected . This problem was finally resolved on the 20 October after a remote access session with a McAfee technician.

 

According to the reliability history monitor the system reached stabilty level 10 by the 7th November. On the 15th there were a number of updates that installed successfully but with the exception of KB2761226 which failed with error code 800b0100. It continued

to fail daily to the 11th December. However, on the 28th November update KB2762895 installed successfully.

 

On the 12th Dec it installed KB2779562, 2761465, 2753842, 2758857, 2770660 and Windows malicious software removal tool. It did not install KB 2779030 with error code 800b0100; I believe this replaced KB2761226 mentioned above. 2779030 has failed to install

from 12th Dec. to date. However, on the 21st Dec. security update KB 2753842 installed successfully.

 

 

Windows Update currently recommends 3 important updates; KB 2779030, 2739159,and 2743555. These return error codes 800b0100, 80073712 and 800b0100 respectively.

 

 

I have tried Microsoft Fixit and automatic trouble shooter without success, and, from answers on the Community Forum, System Update Readiness Tool and System File Checker. I cannot send all the detail from the CheckSUR Log or sfcdetails.txt but the following

are extracts.

 

CheckSUR: please note that KB2731847 was installed successfully on the 15th August 2012.

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

(f) CBS MUM Corrupt 0x800F0900

servicingPackagesPackage_2_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0.mum

Line 1:

(f) CBS Catalog Corrupt 0x800B0100

servicingPackagesPackage_2_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0.cat

 

(f) CBS MUM Corrupt 0x800F0900

servicingPackagesPackage_2_for_KB2739159~31bf3856ad364e35~amd64~~6.1.1.1.mum

Line 1:

(f) CBS Catalog Corrupt 0x800B0100

servicingPackagesPackage_2_for_KB2739159~31bf3856ad364e35~amd64~~6.1.1.1.cat

 

(f) CBS MUM Corrupt 0x800F0900

servicingPackagesPackage_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum

Line 1:

(f) CBS Catalog Corrupt 0x800B0100

servicingPackagesPackage_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat

 

 

Checking Component Store

(f) CSI Manifest All Zeros 0x00000000

winsxsManifestsamd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_42c0e26cca86d4bc.manifest

amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_42c0e26cca86d4bc

 

(f) CSI Manifest All Zeros 0x00000000

winsxsManifestswow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_4d158cbefee796b7.manifest

wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_4d158cbefee796b7

 

 

Summary:

Seconds executed: 1763

Found 46 errors , CSI Manifest All Zeros Total count 12; CBS MUM Corrupt Total count: 17; CBS Catalog Corrupt Total count: 17

Unavailable repair files:

winsxsmanifestsamd64_microsoft-windows-security kerberos_31bf3856ad364e35_6.1.7600.17095_none_42c0e26cca86d4bc.manifest

winsxsmanifestswow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_4d158cbefee796b7.manifest

winsxsmanifestsamd64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7600.21316_none_033c4f3f4f80b23e.manifest

winsxsmanifestsamd64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7600.17119_none_02b5b16c36606152.manifest

 

Tried System File Checker: elevated command prompt > sfc/scannow

findstr /c:"[sR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt"

Extract from sfcdetails.txt (unrepairable files only)

2013-01-07 14:54:50, Info CSI 00000130 [sR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64

(9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-07 14:54:53, Info CSI 00000132 [sR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64

(9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-07 14:54:53, Info CSI 00000133 [sR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2013-01-07 14:54:53, Info CSI 00000136 [sR] Could not reproject corrupted file [ml:520{260},l:46{23}]"??C:WindowsSystem32"[l:20{10}]"tcpmon.ini"; source file in store is also corrupted

2013-01-07 15:03:10, Info CSI 000002ee [sR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64

(9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-07 15:03:10, Info CSI 000002f0 [sR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64

(9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-07 15:03:10, Info CSI 000002f1 [sR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2013-01-07 15:03:10, Info CSI 000002f4 [sR] Could not reproject corrupted file [ml:520{260},l:46{23}]"??C:WindowsSystem32"[l:20{10}]"tcpmon.ini"; source file in store is also corrupted

2013-01-07 15:03:10, Info CSI

000002f6 [sR] Repair complete

2013-01-07 15:03:10, Info CSI 000002f7 [sR] Committing transaction

2013-01-07 15:03:10, Info CSI 000002fb [sR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction

have been successfully repaired

[NB: 31bf3856ad364e35 seems to be a Hex number or address that`s repeated numerous times in both logs.]

Tried Administrator Command Prompt

C:Windowssystem32>takeown /f E:windowssystem32jscript.dll.Returned: “ERROR: File ownership cannot be applied on insecure file systems; there is no support for ACLs.”

 

Unfortunately, I needed to use my computer in the run up to Christmas and now it is too late to do a system restore prior to the 15th Nov. as the restore points are deleted after 7days. It seems that it will install some updates but not specifically

Security Updates for Windows 7 (x64) but apart from this problem the computer is working normally. I have not tried a clean boot as "services" indicate that the update service is started, Automatic (delayed) and BITS, started, manual.I should

be grateful for any advice and whether it`s possible to repair the corrupted files (?) without having to re-install W7.

Regards,

William MWP

 

 

View this thread