After upgrade to Windows 7 Pro multiple windows update failures

mmertel

New member
Local time
11:39 AM
Messages
1
Earlier this week I did an upgrade on my laptop from home premium to professional and now I have 4 updates which continually fail. I've been searching around for a solution and there appear to be several other folks who have reported similar problems on this forum and received good results. I tried to infer the solution from previous posts by copying some missing files into the winxsx and packages directories, but they did not seem to help.

I've run sfc and uploaded the log - no errors.
 
Last edited:

My Computer My Computer

Computer type
Laptop
Computer Manufacturer/Model Number
HP
OS
windows 7 pro x64
CPU
amd
Memory
4G
Hello mmertel and welcome to the forums :party:

You copied one file that you shouldn't have, and you also copied it into the wrong folder, but fortunately the SURT has corrected the mistake:

Code:
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\update.mum        Expected file name Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514.mum does not match the actual file name
(fix)    CBS MUM Corrupt    CBS File Replaced    update.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix)    CBS Paired File    CBS File also Replaced    update.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Aside from that, you have fairly substantial damage on your computer which we will need to fix. The two files that the SURT has picked up as having an incorrect name can be safely ignored, this is merely a bug in the SURT.

Code:
Summary:
Seconds executed: 456
 Found 51 errors
 Fixed 1 errors
  CSI Manifest All Zeros Total count: 38
  CBS MUM Corrupt Total count: 8
  Fixed: CBS MUM Corrupt.  Total count: 1
  CBS Catalog Corrupt Total count: 5
  Fixed: CBS Paired File.  Total count: 1

Unavailable repair files:
    winsxs\manifests\msil_system_b77a5c561934e089_6.1.7601.22126_none_981f568e32422d66.manifest
    winsxs\manifests\msil_system.drawing_b03f5f7f11d50a3a_6.1.7601.22126_none_4d22bb3ec71e9066.manifest
    winsxs\manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.17966_none_70683dd88ae037ac.manifest
    winsxs\manifests\amd64_netfx-system.windows.forms_b03f5f7f11d50a3a_6.1.7601.17966_none_83766cf87b5cb13f.manifest
    winsxs\manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.22126_none_5996991aa48b2ca4.manifest
    winsxs\manifests\msil_system.drawing_b03f5f7f11d50a3a_6.1.7601.17966_none_63f45ffcad739b6e.manifest
    winsxs\manifests\msil_system_b77a5c561934e089_6.1.7601.17966_none_aef0fb4c1897386e.manifest
    winsxs\manifests\msil_system.windows.forms_b77a5c561934e089_6.1.7601.17966_none_054d082500298a66.manifest
    winsxs\manifests\amd64_netfx-system.design_b03f5f7f11d50a3a_6.1.7601.22126_none_73ed560c2f3d4fcd.manifest
    winsxs\manifests\amd64_netfx-system.windows.forms_b03f5f7f11d50a3a_6.1.7601.22126_none_6ca4c83a9507a637.manifest
    winsxs\manifests\amd64_netfx-system.directoryservices_b03f5f7f11d50a3a_6.1.7601.17966_none_16bb9be7a08fd446.manifest
    winsxs\manifests\amd64_netfx-system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.22126_none_df5d70d8643fa83d.manifest
    winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.17966_none_89ab3041bfbe7442.manifest
    winsxs\manifests\amd64_netfx-mscorjit_dll_b03f5f7f11d50a3a_6.1.7601.22126_none_353efd74f2fd46ae.manifest
    winsxs\manifests\msil_system.directoryservices_b03f5f7f11d50a3a_6.1.7601.17966_none_2aff7445ee11ac8b.manifest
    winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.17966_none_837b7fa210fd83d6.manifest
    winsxs\manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.17966_none_318a0f2d99f87527.manifest
    winsxs\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.1.7601.22126_none_a862cbd41776593b.manifest
    winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7601.22126_en-us_508ba5e0b0e37ff9.manifest
    winsxs\manifests\msil_system.windows.forms_b77a5c561934e089_6.1.7601.22126_none_ee7b636719d47f5e.manifest
    winsxs\manifests\x86_netfx-mscorjit_dll_b03f5f7f11d50a3a_6.1.7601.22126_none_7cec344c07796fb4.manifest
    winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.22126_none_6ca9dae42aa878ce.manifest
    winsxs\manifests\amd64_netfx-system.drawing_b03f5f7f11d50a3a_6.1.7601.22126_none_ee2a599d0847244d.manifest
    winsxs\manifests\x86_netfx-peverify_dll_b03f5f7f11d50a3a_6.1.7601.22126_none_5a2603132020fb79.manifest
    winsxs\manifests\amd64_netfx-system.directoryservices_b03f5f7f11d50a3a_6.1.7601.22126_none_ffe9f729ba3ac93e.manifest
    winsxs\manifests\amd64_netfx-system.design_b03f5f7f11d50a3a_6.1.7601.17966_none_8abefaca15925ad5.manifest
    winsxs\manifests\amd64_netfx-mscorjit_dll_b03f5f7f11d50a3a_6.1.7601.17966_none_4c10a232d95251b6.manifest
    winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.22126_none_72d98b83d969693a.manifest
    winsxs\manifests\amd64_netfx-peverify_dll_b03f5f7f11d50a3a_6.1.7601.17966_none_294a70f9f1f9dd7b.manifest
    winsxs\manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.22126_none_1ab86a6fb3a36a1f.manifest
    winsxs\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.1.7601.17966_none_bf347091fdcb6443.manifest
    winsxs\manifests\msil_system.directoryservices_b03f5f7f11d50a3a_6.1.7601.22126_none_142dcf8807bca183.manifest
    winsxs\manifests\amd64_netfx-peverify_dll_b03f5f7f11d50a3a_6.1.7601.22126_none_1278cc3c0ba4d273.manifest
    winsxs\manifests\amd64_netfx-system.drawing_b03f5f7f11d50a3a_6.1.7601.17966_none_04fbfe5aee9c2f55.manifest
    winsxs\manifests\x86_netfx-mscorjit_dll_b03f5f7f11d50a3a_6.1.7601.17966_none_93bdd909edce7abc.manifest
    winsxs\manifests\x86_netfx-peverify_dll_b03f5f7f11d50a3a_6.1.7601.17966_none_70f7a7d106760681.manifest
    winsxs\manifests\amd64_netfx-system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.17966_none_f62f15964a94b345.manifest
    winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7601.17966_en-us_675d4a9e97388b01.manifest
    servicing\packages\Package_1_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_5_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_5_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2742599_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2742599_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Package_1_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_5_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_5_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2742599_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2742599_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.cat

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link. It must be downloaded using Internet Explorer.

Download from Official Microsoft Download Centre

You want the file: Windows6.1-KB2742599-x64.msu

Tom
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Build #1
OS
Windows 8.1 Pro x64
CPU
Intel i7 3770K @4.5GHz
Motherboard
ASUS P8Z77-V PRO
Memory
Corsair Vengeance 2x4GB DDR3 1600MHz Low Profile (White)
Graphics Card(s)
Gigabyte Radeon HD 7850 (2GB GDDR5)
Sound Card
Integrated on motherboard
Monitor(s) Displays
23" LG LCD/LED IPS
Screen Resolution
1920*1080
Hard Drives
Samsung EVO 128GB SSD
Seagate Barracuda 2GB 7200rpm
2x Seagate FreeAgent [500gb]
PSU
Corsair TX650W V2 (80+ Bronze)
Case
NZXT Phantom 410 White
Cooling
Corsair H100 Water Cooler
Keyboard
Microsoft Desktop 2000 Wireless Keyboard
Mouse
Microsoft Desktop 2000 Wireless Mouse
Internet Speed
95 Mb/s Download 70 Mb/s Upload
Antivirus
MSE + MBAM Pro
Browser
Firefox
Back
Top