Microsoft releases fix for Windows Update corruption errors

Microsoft releases fix for Windows Update corruption errors

Summary: Non-critical patch addresses problems in the Windows Update system files which could cause errors in future updates.


Microsoft has released a non-critical, non-security update to fix a bug in the Windows Update system in certain versions of Windows.

Microsoft found problems in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This update is a tool which checks the system for these problems and tries to resolve them. Errors in Windows Update with the following codes are addressed by this update: 0x80070002, 0x8007000D, 0x800F081F, 0x80073712, 0x800736CC, 0x800705B9, 0x80070246, 0x8007370D, 0x8007370B, 0x8007370A, 0x80070057, 0x800B0100, 0x80092003, 0x800B0101, 0x8007371B, 0x80070490.

On Windows 7, Windows Server 2008 R2, Windows Server 2008, and Windows Vista the tool is called the System Update Readiness Tool. The various versions of the update may be downloaded directly from KB947821. Installation instructions are on that page.

On Windows 8.1, Windows 8, Windows Server 2012 R2 or Windows Server 2012 you can use the included Deployment Image Servicing and Management (DISM) tool. Follow instructions in KB947821.

This fix may appear at some point in Windows Update itself, but it is not there as of today.

This update was announced on Microsoft's Description of Software Update Services and Windows Server Update Services changes in content for 2014, dated February 25, 2014. A second update scheduled for that date, Update for Windows 7 and Windows Server 2008 R2 (KB2923545), will "resolve issues in Windows", and has not yet gone live.

Topics: Security, Microsoft, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • ...

    It's baffling that updates still require occasional manual cleanup .
    • Me, too!

      Of my 3 Win 7 workstations, one would frequently give me fits trying to update it. I spent a lot of time reading TechNet articles, manually performing many actions to try to rectify the problem(s). Even their Windows Update "fix-it" tool would not resolve the issue. This would go on for a month or two, then suddenly updates would work again. For a while. Later, the issue would return.

      I really think the update system is GOOD, but in many cases NOT GOOD ENOUGH. Microsoft should make it MUCH easier for home users to get all of the patches for manual installation.
  • Microsoft needs to get their act together.

    Over the past year they've had several problems with updates and those problems do not inspire confidence to patch.
  • Just restored an older i3 Toshiba notebook w/ Windows 7...

    Took a whole day! After the clean install, checked windows update. 1 2 8 UPDATES! Took hours, several reboots... THEN after that it decides to update to service pack 1... and a few more updates/reboots. sheezuz! Now I have to look forward to more updates and reboots.
    • That isn't so bad concidering....

      Windows 7 came out 4.5 years ago. Any other OS that is that old would probably have as many if not more updates.
      Test Subject
      • The problem

        is that with other OSes, most notably OS X, you get combo updates, so you don't need to patch the same files 20 or 30 times, you get a new version of the file with all previous updates patched in one go.

        It means that the patch is huge (gigabytes sometimes), but at least you only need to download and install one patch, one/two restarts and you are ready to go.

        I can understand it for corporates, they want to check each patch, before deploying, but for a consumer or small business install individual PCs, it can be a pain.
      • First thing...

        The first thing you always want to do is to install the most recent service pack.
        • Windows 7 SP2

          should be released to reduce post-SP1 updates. Where is it?
          Sean Foley
          • In their INFINITesimal wisdom,

            MS has decided that there will be no more service packs. It's all part of some obscure plan to make people update the entire OS every year, instead of the usual 3-5 year cycle.
      • R: Windows 7 came out 4.5 years ago

        If you compare the same age Mint or Ubuntu re-install you will see exactly how messed up the Windows install/update procedure really is. One can spend the better part of a day on the Windows re-install/update while someone re-installing Mint or Ubuntu spends the majority of the day working on a fresh install that has been updated to current status.
        • You Sure You Meant...

          ...'majority of the day' on a current up to date Linux/Unix Install? While only 'better part of a day', on Microsoft?
          Wouldn't it be 'minority part of...' for a current FOSS Install?
          Or same for a slipstreamed current MS OS?
    • An issue with OEM restore

      I wish the OEMS would slipstream the sp into the recovery partition to prevent this issue. I typically install the OS, then I apply the current SP, then update from that point.
  • updates

    I don't mind all the updates, I am used to them, but it would be nice if Service Pack 1 would install on my Windows 7 PC. It keeps failing, and there doesn't seem to be any fix for it.
    Paul on the Mesa
    • If you have not already

      May try these steps listed in link.

      Troubleshoot problems installing a service pack for Windows 7 or Windows Server 2008 R2
  • The two KB286**** patches for USB security will cause update crashes

    Had to undo them and go without them, and I doubt that this new Windows Update patch would solve the problem with those two USB security updates. They are simply flawed code to begin with.
  • Get it right first time!

    If Microsoft could write an OS and get it right first time, we wouldn't need updates! OK, I know from experience that it's impossible to get software right first time, but Microsoft could at least make a better job of writing the OS than they do - like consulting users on what they want.

    Back in 1982, I had a computer where the OS was in ROM - yes ROM, not flash, not upgradable, so if you wanted an update, you had to open the case, unplug the old ROMs, get an update, plug the new ROMs in and put the case lid back on. Guess what - we never had a single update!

    If Microsoft were to release Windows in ROM, it would be much more difficult and expensive for MS to provide updates, so they'd take a lot more care before releasing a new OS. There are 2 fundamental advantages to having the OS in ROM:
    1) It can't be corrupted - unless the ROM is physically damaged
    2) Startup is fast, because the OS can be run from ROM so there's zero OS load time.

    On a serious note, it would be practical to put the kernel of the OS in ROM and the boot sequence in ROM thus eliminating the possibility of rootkits. I wonder if this simple approach will ever be implemented.
  • Latest Windows 7 Update Corrupts Startup

    Okay it started within the last month, still going through the last couple of updates trying to work out which one it is. Anyway, it initially started when the boss's wife turned on her laptop after an update and it came up with a Realtek Ethernet cant find media message. So disabled the lan. Next shows no operating system.

    First step throw in a new HDD reload windows from recovery then do the million and one updates, until it arrives at the last 39. In amongst these were Office updates etc.

    Had been running the computer for the past 5 days on the previous updates no issues whatsoever and yesterday installed the last 39 updates. And you guessed it, up came the same problems on a brand new harddrive, that has been checked and checked for errors.

    I managed to get it to finally reboot by using recovery and f8 to start it. On the first couple of times found no sign of a system restore, and the update history was empty. Other things started showing up that implied information had been corrupted and hidden. On checking further every service had been disabled. Restarted all of them with normal startup saved then restarted, still no joy, however on a restart managed to get it to restore to last week rebooted, and bother, still warnings. Again good old recovery boot, then this time managed to get a full check disk scheduled for start up. Now it is back to running and I have been slowly putting the updates on bit by bit. Down to updates 11/02/2014 and suspect culprit is there. However I have just installed an update for December rebooted an now computer has started checking disk on its own. Great start to my day will let you know of the outcome.
  • updates-patch-for-windows8

    Yes there is a microsoft fix which will not fix all the issues related to updats.
    For any more support reach us on
  • Still does not work....

    The hot fix to fix the corruption problem installs and ends up complaining cannot install due to the same problem in the first place. Microsoft is a bunch of morons, I'm going back to turning the update off again and not waste anymore time on this. I thought about going to Windows 8 but that's piece of junk 7 was fine in the beginning but after time it becomes sluggish. Maybe in Windows 15 (Fifth-Teen), about 20+ years from now, they will figure it out and get right.