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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2015-05-25T15:52:18+00:00

    I faced the same problem and was able to solve as follows:

    The installation of KB3033929 seems to fail because on rebooting Windows expect that the boot partition will be the Windows one. However, when Grub is installed the boot flag (the bit that says which partition has the boot code) is not in the Windows boot partition.

    You will then have to remove the boot flag from the Grub partition and attribute it to the Windows boot partition. This can be easily done following the process below:

    1. Go to gparted.org, download the live gparted CD/USB (http://gparted.org/livecd.php)
    2. Build the bootable  CD or USB (instructions on doing this are on the site)
    3. Boot the PC with this CD/USB and start Gparted (if it was not already started)
    4. Determine which is the partition that contains Windows (the partition that should be booted next time)
    5. Select the one partition (click on it with mouse) at a time and click on menu item "Partition" and on it click on "Manage Flags". If the boot flag is checked, this is the partition from which the PC will boot (This means that Grub is installed in this partition). Take note of this partition. Uncheck the boot flag of this partition.
    6. Select the partition where Windows is installed, click on the "Partition" menu and in it click in the "Manage Flags" and put a check mark (mouse click) on the "boot" checkbox.
    7. Remove the CD/USB and reboot the PC, It should reboot directly in Windows. Then install the KB3033929 update. Reboot the PC to finish the update installation.
    8. Reinsert the CD/USB and reboot the PC into Gparted. Uncheck the boot flag in Windows partition and attribute it to the partition it was before you started.
    9. Reboot the PC. It is done.

    There is a catch to this process. If Grub was installed in the MBR, you will need to reconstruct the original Windows MBR by using the Windows installation or recovery CD. Also, if installed in the MBR, the "Boot" checkbox may not be checked.

    Should you run into problem, you may resort to "Parted Magic" (https://partedmagic.com/) and download their .ISO which has a lot of tools to help recover (it even offer Gparted).

    You must be careful and make backups of your data before proceeding to follow the above process.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-31T14:17:43+00:00

    Hi Paulo,

    Thank you very much for the update.

    It is good to note that your issue is resolved. The steps you updated might help other community members to resolve their similar issues.

    Thanks again for sharing!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-05T18:39:16+00:00

    I have the same issue with a Chameleon boot loader. A 32 bit Windows by the way.

    Was this answer helpful?

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

    Did you tried the process in my reply above?

    Was this answer helpful?

    0 comments
  5. 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