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

Hello!

I had the same problem with KB3033929 on a Dell Inspiron 1545 notebook running Windows 7 and found a way to solve it.

Configuration:

• Host: Dell Inspiron 1545
• BIOS: A14, latest from 2009, pure BIOS, no UEFI
• OS: Windows 7 Home Premium 64 bit english
• HDD: 320 GB (good old motor driven storage device, no SSD :-)
• Partition table:

  - Partition #1:  40 MB, primary, FAT32, "Dell Utilities", contains realmode tools for hardware diagnostics

  - Partition #2:  15 GB, primary, NTFS,  "Recovery", marked as bootable, contains MS bootmanager, WinRE, Dell recovery software and the Dell factory image of the OS

  - Partition #3: 300 GB, primary, NTFS,  "OS", contains the Windows 7 operating system

  - Partition #4: unused

Situation:

• OS has been restored to the Dell factory image (without SP1) from the Dell recovery partition
• Windows 7 SP1 has been installed manually
• Windows Update has been configured to install all missing updates for the OS and all other MS products

Problem:

• KB3033929 and KB3133977 cannot be installed. During phase 3 of the installation process both updates will be reverted.

Cause:

• Windows OS seems to get confused by the existence of the "Dell Utilities" partition
• the "Dell Utilities" partition must be "not existent" for the OS when running Windows update

Solution:

• Delete the "Dell Utilities" partition or at least temporarily delete the partition table entry of the "Dell Utilities" partition

Example:

• boot with WinPE 3 from an external storage device; a disk editor is required
• make a backup copy of the BCD store that resides in the directory "\boot" on partition #2
• use the disk editor to create a backup of the Master Boot Record located at LBA=0
• use the disk editor to "hide" the "Dell Utilities" partition. Fill all 16 bytes of the corresponding partition table entry with binary zeroes.
• run "DISKPART" and enter the command "RESCAN" (without quotes) to force WINPE to recognise the modified partition numbering
• "EXIT" from "DISKPART"
• run "BOOTREC /REBUILDBCD" to force the BCD store to use the modified partition numbering required for the boot process of WinRE and the OS
• reboot the PC with the regular Windows 7 OS
• run Windows update
• this time both KB3033929 and KB3133977 should install without problems
• reboot with WinPE and restore the previously backed up Master Boot Record and the BCD store
• be happy
• wait until Microsoft releases another update that makes use of sophisticated partition analysis (SCNR)

I had the same problem, but in my case, I only have 1 SSD on my notebook (Asus M50VM).

So I realize that the partitions on the SSD have 2 bootable flags (don't know why). I entered Ubuntu, removed the bootable flag from the 1st partition (Ubuntu) and rebooted. Even with GRUB loading, I managed to install the update without problems then.

I did some investigating and discovered that for me, after checking all the other tips in this and other forums, the PC (Dell Dimension 9100) with this problem is TOO OLD (about 7 years)! It lacks the Data Execution Prevention instruction that is in the newer Intel chips. So this update, a pre-cursor to Windows 10, cannot run.

My old PC will have to remain at Windows 7 or maybe upgrade to Win 8.1 (which can USE that instruction, but does not REQUIRE IT). But Windows 10 is not possible. So I just "hid" that update and ignore the "get Windows 10" prompts.

Microsoft just sucks on this issue! This is a joke. This has broken so many systems. So very disappointed.

I know it's late in the game, but I ran into this issue today on my work laptop (Windows 7 Pro x64, just issued to me a few days ago)...

Searched Google extensively and couldn't find a fix that applied, since this is a pure Windows 7 machine, not dual boot.

I dug through the CBS.log file and found this error:

2015-09-16 21:44:22, Error      [0x018009] CSI    00000017 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK

    Process exit code 193 (0x000000c1) resulted in success? FALSE

    Process output: [l:99 [99]"BFSVC: Failed to validate boot manager checksum (C:\Windows\boot\PCAT\bootmgr)! Error code = 0xc1

...

2015-09-16 21:44:22, Error      [0x018007] CSI    0000001b (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]

2015-09-16 21:44:28, Info                  CSI    0000001c End executing advanced installer (sequence 39)

    Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

It turns out that the bootmgr file was not present in the C:\Windows\boot\PCAT directory

The fix was to check the assembly directory for a copy of the bootmgr file:

dir C:\windows\assembly\boot\pcat\bootmgr

If if shows a copy present, copy it to where the patch expects it to be:

copy c:\windows\assembly\boot\pcat\bootmgr c:\windows\boot\pcat\bootmgr

Then I retried installing the patch via Windows Update, and it worked the first time, even though it had failed several times prior to that.

The main thing here is to review the CBS.log file and look for the failure reason.  It seems some are due to dual boot, some are due to insufficient space on the restore partition and this was the answer for mine.