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've had this problem happen on two computers (Win7x64) on which I'm running GRUB; one of those is at work, and one of those is at home. In my case, though, I only have one hard drive. Although I don't object to backing up my GRUB MBR, installing a W7 bootloader, and then restoring my GRUB MBR later after I've successfully installed KB3033929... to hell with that. I'll just disable the update, and let it install later on once everything is fixed, unless Micro$oft wants to reimburse me for my labor at the $50/hr rate that my company thinks I'm worth. Hey, Microsoft, there are plenty of us out here who multi-boot! Why would you possibly think it's cool to create an update that refuses to function unless we're running a 100% Microsoft system?! What does the MBR - WHICH EXISTS OUTSIDE OF MY WINDOWS PARTITION have anything to do with an update that takes place *within* my Windows partition?!

You, this thread...and this issue. Is a crock of ****. You're talking poopness.

Your computer building--sucks. I've built four...no issues. I purchased two--full of junk and issues. Wow you've built four PC's good for you, meanwhile I'm on my two hundredth PC build of which all are still running as good as the day I built them!. Oh and by the way the PC I built for my mum was fixed in about 20 mins the time it took to re-image it, I allowed the update to download then hid it from updates to install, it is now running as it should have been doing before the **** update from MS... I'd still like to know why it was complaining about grub when the HDD was brand new and has never had Linux anywhere near it though if you have some info to share please do otherwise stop posting rubbish

<removed> I've built four...no issues. I purchased two--full of junk and issues.

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. Stupid Much My moms new PC (which I built by the way) was using a brand new HDD duh the only OS to ever be installed on it was Windows 7 X64 so tell me now why is it stating it has a problem with GRUB ????

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-04-10T18:23:40+00:00
I've had this problem happen on two computers (Win7x64) on which I'm running GRUB; one of those is at work, and one of those is at home. In my case, though, I only have one hard drive.

Although I don't object to backing up my GRUB MBR, installing a W7 bootloader, and then restoring my GRUB MBR later after I've successfully installed KB3033929... to hell with that. I'll just disable the update, and let it install later on once everything is fixed, unless Micro$oft wants to reimburse me for my labor at the $50/hr rate that my company thinks I'm worth.

Hey, Microsoft, there are plenty of us out here who multi-boot! Why would you possibly think it's cool to create an update that refuses to function unless we're running a 100% Microsoft system?! What does the MBR - WHICH EXISTS OUTSIDE OF MY WINDOWS PARTITION
- have anything to do with an update that takes place *within* my Windows partition?!
Was this answer helpful?

0 comments No comments
Anonymous

2015-04-02T23:14:41+00:00

You, this thread...and this issue.

Is a crock of ****.

You're talking poopness.
Was this answer helpful?

0 comments No comments
Anonymous

2015-04-02T21:31:43+00:00

Your computer building--sucks.

I've built four...no issues.

I purchased two--full of junk and issues.

Wow you've built four PC's good for you, meanwhile I'm on my two hundredth PC build of which all are still running as good as the day I built them!. Oh and by the way the PC I built for my mum was fixed in about 20 mins the time it took to re-image it, I allowed the update to download then hid it from updates to install, it is now running as it should have been doing before the **** update from MS...

I'd still like to know why it was complaining about grub when the HDD was brand new and has never had Linux anywhere near it though if you have some info to share please do otherwise stop posting rubbish
Was this answer helpful?

0 comments No comments
Anonymous

2015-04-01T20:04:30+00:00

<removed>

I've built four...no issues.

I purchased two--full of junk and issues.
Was this answer helpful?

0 comments No comments
Anonymous

2015-04-01T18:50:21+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.

Stupid Much

My moms new PC (which I built by the way) was using a brand new HDD duh the only OS to ever be installed on it was Windows 7 X64 so tell me now why is it stating it has a problem with GRUB ????
Was this answer helpful?

0 comments No comments