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

This article does a pretty good job of explaining what went wrong with Microsoft's "Patch Tuesday"

Reboot loop! Microsoft update to fix an old update ends up breaking a new update...

It seems that KB3033929 and KB3035131 had to be applied in that specific order. It isn't entirely clear why some machines did so properly, and some did not. But, when KB3035131 was applied first most following patches failed too.

The solution seems to be turning off Windows Update, rolling back to a System Restore point prior to 3/9/2015, then manually installing KB3033929 first and KB3035131 second. Then, turn Windows Update back on and auto-install all the others

Hopefully, this will work........

I previously did basically that.  I uninstalled the KB3035131 patch and applied the KB3033929, but it still fails and reverts.  So I installed KB3035131 again without any problems. 

For now I will wait for someone to answer the last post I made concerning my CBS log file.

Thanks anyway.

This article does a pretty good job of explaining what went wrong with Microsoft's "Patch Tuesday"

Reboot loop! Microsoft update to fix an old update ends up breaking a new update...

It seems that KB3033929 and KB3035131 had to be applied in that specific order. It isn't entirely clear why some machines did so properly, and some did not. But, when KB3035131 was applied first most following patches failed too.

The solution seems to be turning off Windows Update, rolling back to a System Restore point prior to 3/9/2015, then manually installing KB3033929 first and KB3035131 second. Then, turn Windows Update back on and auto-install all the others

Hopefully, this will work........

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]

This is a Consumer-specific, peer-to-peer support forum. You will find appropriate support in the Win7 IT Pro-specific forums: http://social.technet.microsoft.com/Forums/windows/en-US/home#category=w7itpro 

Will do, thanks for the tip

Just looked and boards are burning up with this one

All 14 machines in our office are Win 7 Pro Dells of similar vintage, only one is caught in this infinite loop of KB3033929 AND KB3035131 SINCE 3/12/2015...This is a major problem because it is on the company CFO's desktop. A Win 7 re-install is a no-go because this PC has old accounting/ERP software to which we no longer have licenses. All that data is needed in case of an audit.

This is a Consumer-specific, peer-to-peer support forum. You will find appropriate support in the Win7 IT Pro-specific forums: http://social.technet.microsoft.com/Forums/windows/en-US/home#category=w7itpro

The above notwithstanding, tell your CFO to stop running Disk Cleanup with the "Windows Update cleanup" option disabled & see if the behavior continues to persist.