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-04-01T08:30:40+00:00

    Seeing is believing.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-01T08:17:08+00:00

    MY Fix

    Leave the DVD draw open also this worked for me on two separate occasions

    After reinstalling the backup disc’s on son’s laptop for a fresh OS install, then deleting some of the bloatware and Microsoft live mesh.

    I continued with M-soft update’s 172 of them

    I kept on getting the Message “failure configuring windows updates reverting changes”

    After following M-soft help pages and installing them in Clean boot mode the updates have worked.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-01T07:55:55+00:00

    In my experience using Win 7.

    Win 7 does not like " used " HDD's.

    If you are experiencing...freakish...system start up.

    I would suggest.

    Purchase a brand new System C:/drive.

    I use 2-desktops.

    Both Win 7.

    Both are SSD 120-GB's minimum total capacity.

    I would say...320-GB should be your minimum capacity.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-03-31T21:25:34+00:00

    Below is an extract of the CBS log file after a KB3033929 manual installation failure.  With my limited knowledge, it appears it fails to copy (C:\Windows\boot\PCAT\bootmgr) to the System Reserve partition which when I installed Windows 7, created a 100 MB partition.  I believe the error 0x70

    indicates there is no space available on the partition. 

    This may the reason some Windows 7 updates fail the KB3033929 installation, while some have no problem.

    Can you or anyone shed any light on the log entries and how I might fix the problem, or is this a M/S problem caused by installing Window 7 SP1 and only creating a 100 MB partition that should have been larger?  Is there a way I can expand the partition size without destroying my Windows 7 system ?

    CBS LOG FILE EXTRACT:

    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 60 of 60) Last Error = 0x70BFSVC:

    Error copying boot files from C:\Windows\boot\PCAT to \\?\GLOBALROOT\Device\HarddiskVolume1\Boot! Last Error = 0x70"][gle=0x80004005]

    2015-03-20 14:34:01, Info                  CSI    0000002c Calling generic command executable (sequence 2): [24]"C:\Windows\fveupdate.exe"

        CmdLine: [35]""C:\Windows\fveupdate.exe" /memtest"

    2015-03-20 14:34:01, Info                  CSI    0000002d Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK

        Process exit code 0 resulted in success? TRUE

        Process output: [l:248 [248]"BitLockerUpdate: Running.BitLockerUpdate: Service request is for memtest.exe.BitLockerUpdate: BitLocker Drive

    Encryption is not turned ON on the OS volume.BitLockerUpdate: No servicing was performed on the OS volume.BitLockerUpdate: Done."]

    2015-03-20 14:34:01, Info                  CSI    0000002e@2015/3/20:19:34:01.770 CSI Advanced installer perf trace:

    CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Version = 6.1.7601.18741, pA =

    PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral,

    PublicKey neutral;34776454

    2015-03-20 14:34:01, Error      [0x018007] CSI    0000002f (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-

    794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the

    installer queue are completed; installer is reliable (2)[gle=0x80004005]

    Based on the results of my CBS.log file, I decided to spend some time to re-visit this issue today.  My failure seems to point to the update being unable to write a file to the system reserve partition as it was full.  It was set up for 100 MB when I installed Windows 7.  Using Partition Wizard (free), I expanded the system reserve partition from 100 MB to about 400 MB.  I again ran the manual installation file for KB3033929 and it installed without any problems.

    After it was completed, I again plugged in my second HD with Windows XP, reset my boot loader with EasyBCD and all is now back to normal with dual boot menu to either Windows 7 or Window XP.

    Finally....hope this might work for others that are having a problem.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-03-31T14:47:33+00:00

    Finally was able to break the loop and access bios.  Changed boot order to cd/dvd first.  This allowed me to boot from a system disk.  I ran the repair and it said it could not repair the error but allowed me to do a controlled shut down.  Started system and it booted normally.  Immediately created a Windows repair disk.

    Thanks for assistance!

    Was this answer helpful?

    0 comments No comments