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

108 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-07-22T18:17:35+00:00

    this is not just a dual boot issue. I have a regular HD, (not SSD or anything else), single boot, windows 7 Pro 64bit. still does the same error and reverts.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-06-30T15:36:26+00:00

    Hello,

    Thank you for sharing information with us.

    I hope that your knowledge may help other community members to resolve similar issues.

    I appreciate it.

    Thank you

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-28T13:43:33+00:00

    Not sure if others have already posted this, but in case it saves someone some time: I found that I didn't even need to restore the actual Windows Boot Loader (I'm dual booting but with both OSes on the same disk). Instead I only needed to set the boot flag on the Windows partition (rather than it being on the Linux one).

    This still left GRUB as the loader (as it's installed in the MBR), but seemed to do the trick for the update. For reference I triggered the update from windows, then let it reboot and again selected Windows from the GRUB screen.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-06T06:28:31+00:00

    ...not yet. It means a lot of trouble for me, since once i have changed the boot flag, I will not be able address Chameleon any more. I will need to build up a backup boot loader first.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-06-05T20:52:58+00:00

    Did you tried the process in my reply above?

    Was this answer helpful?

    0 comments