KB3033929 fails to install and cause a minor "infinite" loop

Anonymous
2015-03-11T13:12:48+00:00

I'm having problems with the KB3033929 update from the latest run of Tuesday patches. After installation the PC reboots, but during the boot up configuration of the patch it fails and Windows starts reverting the configuration and reboots. And then it starts all over again a couple of times until it eventually boot into Windows. I looked into Windows' setup logs and found the following:  

  • A reboot is necessary before package KB3033929 can be changed to the Installed state.
  • Package KB3033929 failed to be changed to the Installed state. Status: 0x80004005.
  • Initiating changes for package KB3033929. Current state is Invalid Installed. Target state is Staged. Client id: WindowsUpdateAgent.
  • Package KB3033929 was successfully changed to the Staged state.

So what is wrong?

https://support.microsoft.com/kb/3033929

System information:

Windows 7 Home Premium x64 (ver. 6.1.7601)

HP Envy 14-1090eo Core i5 14.5"

Software running in the background:

CrashPlan 3+ Backup

Dropbox

Avast!

Secunia PSI

OneDrive

Thermo Scientific control module for a UHPLC System

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

108 answers

Sort by: Newest
  1. Anonymous
    2015-03-16T19:26:20+00:00

    OK - after browsing around I found that the problem appears to be associated with the bootloader. My system is dual boot. I have Windows on one SSD with its original bootloader. Another SSD holds Ubuntu 14.10 with a GRUB bootloader - this is set to boot first in the BIOS. My files are on a separate HDD.

    Here's what worked for me.

    1. Set the Windows drive to be the boot drive in the BIOS.
    2. Reboot into Windows (i.e., avoiding GRUB).
    3. Run Microsoft Update again and allow the install to complete along with restart. It did so without any issues.
    4. Restart computer and reset BIOS to place the Ubuntu SSD first in the boot order.
    5. All working normally and confirmed that KB3033929 has been installed.

    Not sure why the bootloader should be a problem. I have another machine that runs Windows 7 Home and Ubuntu on a partitioned drive - GRUB is the bootloader and yet there were no issues with the update. Could it be that the 64 bit update is the problem??

    Yes, this worked for me. I believe it's the avoidance of the non-windows drive that is the trick. I didn't change bios settings but used the F8 key during boot to bring up a boot drive selection menu where I always picked the Windows disk (for both update install and the required reboot to finalize). THANKS!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-03-16T11:44:58+00:00

    no luck for me too

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-03-15T21:50:44+00:00

    I solved this Problem in this way:

    Run MicrosoftFixIt50123.msi

    Looked fpr Updates (Manualy)

    Installed Updated (INCL. KB3033929)

    NO Problem (Windows 7 Home)

    CY

    I tried this as I stated in my first post to this thread and it also did not work.  In fact when I ran the manual update for KB3033929, it gave an error that it was for a different version of Window or something to that affect, don't really remember exactly as I tried so many suggestions to resolve the issue.

    The Fixit I ran was from a window directly on a M/S support web site. so I don't know if it was the same that you ran as I don't remember the numbers you have listed with it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-03-15T20:23:02+00:00

    I solved this Problem in this way:

    Run MicrosoftFixIt50123.msi

    Looked fpr Updates (Manualy)

    Installed Updated (INCL. KB3033929)

    NO Problem (Windows 7 Home)

    CY

    No luck for me.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-03-15T20:15:31+00:00

    Run Microsoft FixIt 50123

    FixIt 50123 addresses registry corruption. How did your registry become corrupted (damaged)?

    cf. http://www.bleepingcomputer.com/forums/t/407147/answers-to-common-security-questions-best-practices/?p=285305

    Was this answer helpful?

    0 comments No comments