[SOLVED] Windows 7, security update fails


Recommended Posts

Have a friend who can't get his machine to update at all. it will download and start installing and then almost instantly fail with ""windowsUpdate_800B0100" " WindowsUpdate_dt000"

All the search results I found for that error seem to be about having trouble installing SP1, but this machine is already running SP1 (and has all updates installed except the one thats failing, KB2778344).

I tried quite a few things, renaming the software distribution folder so it would download it fresh (this helped a little but, there was initially 3 updates failing and this let me install two of them), running the fixit to reset/repair windows update, running the system update readiness tool, using the windows update troubleshooter in control panel. I also scanned for malware with malwarebytes which found 2 items in the user's internet explorer temp files and removed them, didn't find anything else and shows no other symptoms of malware.

edit: update readiness tool gives me these errors in the log:


Unavailable repair files:
winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22137_none_21e50706feb2618b.manifest
winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22137_none_17905cb4ca519f90.manifest
winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.17977_none_16dba817b1543c48.manifest
winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.17977_none_21305269e5b4fe43.manifest
servicing\packages\Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_3_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_3_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_3_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_3_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat
[/CODE]

Recently had a problem with Win 8 laptop erroring out for WU, to fix I had to:

Stop the Windows Update service in services.msc

then delete the contents of:

SoftwareDistribution\DataStore

and

SoftwareDistribution\Download

Then restart Windows update service and check for updates again

All worked fine after that

Recently had a problem with Win 8 laptop erroring out for WU, to fix I had to:

Stop the Windows Update service in services.msc

then delete the contents of:

SoftwareDistribution\DataStore

and

SoftwareDistribution\Download

Then restart Windows update service and check for updates again

All worked fine after that

Yeah I did try that (just different method, renamed entire SoftwareDistrobution folder to Softwaredistrobution.old, and let windows regenerate the folder). This helped for 2/3 updates that were failing, but one continues to. I even tried doing it again and rebooting but it didn't help.

whew, think I've got it now. ended up having to download the .msu package for the update that checksur was complaing was corrupted (KB2761226), extracting the files from it, placing them in the correct directories under C:\Windows\Temp\CheckSUR, run the windows update readiness checker again, and now it was able to fix most of the problems. Its still complaining about a few files but I think I just missed a few files to manually copy over, so I just have to try again, it fixed most of the errors :)

whew, think I've got it now. ended up having to download the .msu package for the update that checksur was complaing was corrupted (KB2761226), extracting the files from it, placing them in the correct directories under C:\Windows\Temp\CheckSUR, run the windows update readiness checker again, and now it was able to fix most of the problems. Its still complaining about a few files but I think I just missed a few files to manually copy over, so I just have to try again, it fixed most of the errors :)

wow what a mess on, wonder why its doing that

no idea lol, if i had to guess it was powered off during a windows update or something

Maybe yea, WU seeing a partial install of the file or something

Maybe try an sfc /scannow and see if anything gets repaired / replaced

Maybe yea, WU seeing a partial install of the file or something

Maybe try an sfc /scannow and see if anything gets repaired / replaced

Yeah if it still doesn't work I will, right now I've copies over the files I think I missed and am running checksur again, and its already repaired a few more things, so hopefully this is the last of the corrupted files:


Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 17.0
2013-02-15 12:04

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 443
Found 1 errors
Fixed 1 errors
CBS MUM Corrupt Total count: 1
Fixed: CBS MUM Corrupt. Total count: 1
Fixed: CBS Paired File. Total count: 1
[/CODE]

now to try running WU :)

EDIT: yay, it worked :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!