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

I triple-boot Oracle Linux, Android-x86 and Windows 7 on my problem system and don't want to disturb GRUB. I have no intention of rewriting the MBR to install this update. I'd rather blacklist it. I've disabled Windows Update. I'll try again next month.

I found a solution to stop the endless loop. KB3033929 never successfully installed. The last few days, it would try when I shut down, and fail to install when I started my pc in the morning, so it would revert back to the prior configuration. Today, i went to Control Panel, Windows Update, then right clicked on KB3033929, and clicked "Hide". It is still not installed, but the endless loop has stopped, now shut down and start up are back to the normal times. I hope I live long enough to see Microsoft solve the problem.

That's Great!! ,, How about the rest of us who are not using Ubuntu partitions and GRUB bootloaders?

I'd also like to know this answer brand new HDD never had Linux anywhere near it brand new clean install of win7 x64 and this **** makes it unusable

After reading the https://support.microsoft.com/da-dk/kb/3033929 , it got me thinking. Maybe there is something in the newer bioses that restrict some installations, that may try to access the hardware in some special way. A computer here with Asus motherboard got that issue it can not install it. An other computer here from Acer and HP pre builds do not have that issue and already have then installed. Havent been able to test that out yet, but i know on some older computer they had a boot sector protection, so thats why it got me thinking in that direction. As written on that page. Issue 1 workaround To work around that issue, you can either use Windows as the default boot loader or you can change your BIOS settings to enable the Windows boot loader directly when you install this update. So that bios setting can sure have some influence.

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-03-22T16:25:52+00:00

I triple-boot Oracle Linux, Android-x86 and Windows 7 on my problem system and don't want to disturb GRUB.

I have no intention of rewriting the MBR to install this update. I'd rather blacklist it.

I've disabled Windows Update. I'll try again next month.
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-23T22:12:46+00:00

I found a solution to stop the endless loop. KB3033929 never successfully installed. The last few days, it would try when I shut down, and fail to install when I started my pc in the morning, so it would revert back to the prior configuration.

Today, i went to Control Panel, Windows Update, then right clicked on KB3033929, and clicked "Hide".

It is still not installed, but the endless loop has stopped, now shut down and start up are back to the normal times. I hope I live long enough to see Microsoft solve the problem.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2015-03-24T14:42:01+00:00

That's Great!!

,, How about the rest of us who are not using Ubuntu partitions and GRUB bootloaders?
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-24T21:09:20+00:00

I'd also like to know this answer brand new HDD never had Linux anywhere near it brand new clean install of win7 x64 and this **** makes it unusable
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-25T18:03:19+00:00

After reading the https://support.microsoft.com/da-dk/kb/3033929, it got me thinking.

Maybe there is something in the newer bioses that restrict some installations, that may try to access the hardware in some special way.

A computer here with Asus motherboard got that issue it can not install it.

An other computer here from Acer and HP pre builds do not have that issue and already have then installed.

Havent been able to test that out yet, but i know on some older computer they had a boot sector protection, so thats why it got me thinking in that direction.

As written on that page.

Issue 1 workaround

To work around that issue, you can either use Windows as the default boot loader or you can change your BIOS settings to enable the Windows boot loader directly when you install this update.

So that bios setting can sure have some influence.
Was this answer helpful?

0 comments No comments