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

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.

Thanks ataraxy2000, but I am not planning to install Windows 10

Probably not worth worrying about this any more, since it will be solved by Windows 10.

I have just one driver, no dual boot and I still have the same problem I still cannot install the update KB3033929, Windows 7 Pro SP 1-ONLY ONE SYSTEM.

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

Anonymous

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

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

Anonymous

2015-10-07T20:17:25+00:00

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

0 comments No comments
Anonymous

2015-09-17T02:26:02+00:00

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.
Was this answer helpful?

0 comments No comments
Anonymous

2015-08-25T07:18:26+00:00

Thanks ataraxy2000, but I am not planning to install Windows 10
Was this answer helpful?

0 comments No comments
Anonymous

2015-08-25T07:09:01+00:00

Probably not worth worrying about this any more, since it will be solved by Windows 10.
Was this answer helpful?

0 comments No comments
Anonymous

2015-08-24T23:40:57+00:00

I have just one driver, no dual boot and I still have the same problem

I still cannot install the update KB3033929, Windows 7 Pro SP 1-ONLY ONE SYSTEM.
Was this answer helpful?

0 comments No comments