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: Oldest
  1. 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
  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-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
  4. Anonymous
    2015-03-17T01:33:26+00:00

    @Shodan2k only! =>

    First things first...

    Assuming your problem has not been resolved (or your question has not been answered to your satisfaction), please unmark*michaelp52's* reply as ANSWER then don't mark any other replies as ANSWER unless & until your problems have been resolved. Please do this now, before replying to this post, to avoid confusion. Thank you.

    
    
    
    
    
    
    
    
    1. What anti-virus application was installed prior to 06 March 2015, was your subscription (if any) still current, and did you uninstall it before you installed Avast Free?
    
    
    
    
    
    2. Do you have backups of ALL the changes CCleaner's Registry Cleaner has EVER made to the computer? [1]
    
    
      
    
    ===========================================================  
    
    [1] Injudicious use of registry cleaners may be playing a role here. TIP: If you ever again think your Registry needs to be cleaned, repaired, boosted, tuned-up, cured, tweaked, fixed, maximized, "swept" or optimised (it doesn't), read
    **[this article](http://www.bleepingcomputer.com/forums/t/407147/answers-to-common-security-questions-best-practices/?p=2853053)** (and related links cited therein) then draw your own conclusions. Also related =>
    [http://support.microsoft.com/kb/2563254](http://support.microsoft.com/kb/2563254)
    
    
    
    
    
    

    First thing first. I unmarked the post as Answer as suggested since I do not dual boot.

    1. I have been using Avast Free all along. I uninstalled Avast prior to 6 March 2015 because they released a new version and from experience installing a new version on the top of the old is just asking for trouble. Now I have uninstalled it all together to see if Avast was causing the trouble. It did not help.
    2. I ran the backup to all the changes CCleaner had done to the registry database. None related to Windows.
    3. I ran the (KB947821) (Fix Windows corruption errors by using the DISM or System Update Readiness tool) and went through the log. No problems found and it did not help.
    4. Ran a SFC /SCANNOW and got 100%. No problems found.
    5. Ran MicrosoftFixIt50123.msi. Did not help either.
    6. I changed the services Windows Installer and Windows Modules Installer from Manual to Automatic startup. Did not help either.
    7. Made a resetting of Windows Update components (KB971058). Did not help either.

    I have uploaded the logs from the most recent attempt to install the update. I have trimmed the file so they only contains the the installation attempt or else you would be looking at 400+ MB txt file :)

    CBS log Txt (170 MB)

    http://1drv.ms/1Elg2FQ

    WindowsUpdate log txt (114 KB)

    http://1drv.ms/1Elgq7d

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-03-17T07:50:37+00:00

    @Michaelp52

    Your suggested fix worked* on my machine and t he bootloader seems to be the problem! My machine that dual boots "Manjaro Linux" and "Windows 7 64-bit" consistently fails to install Microsoft Security Update KB3033929 so long as GRUB2 is my boot loader. Once I reconfigured the MBR and Windows' partition boot record to use the Windows 7 boot-loader the update installed without errors ^_^

    *I have a dual boot setup with both operating systems in different partitions of the same HDD so instead of switching which physical drive I booted from, I had to replace my original boot-loader GRUB2 with Windows 7's bootloader:

    1. Set the Windows drive to be the boot drive in the BIOS.

    Replace GRUB2 code in MBR with Windows 7's "bootmgr" compatible code by running:

    bootrec.exe /fixmbr

    1.33 Update the partition boot record of the bootable Windows partition by running:

    bootsect.exe /nt60 all /force

    1.66 Make the bootable Windows partition the Active partition using:

    diskpart

    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.

    Use the free EasyBCD program and edit Windows Boot Configuration Data so that Windows' "bootmgr" provides the option to boot into my linux partition as well.

    5. All working normally and confirmed that KB3033929 has been installed.

    Was this answer helpful?

    0 comments No comments