The patch in question is KB3081424 (ironically enough a roll-up of bug fixes) and during its update process affected users find it fails and triggers the message: “We couldn’t complete the updates, undoing the changes.” Undoing them results in a mandatory system reboot, but as soon as the user logs back on Windows 10’s update process kicks in and tries to install KB3081424 again.

I’m sure you’re way ahead of me here, but since Windows 10 updates cannot be stopped KB3081424 tries to install over and over again which leaves systems caught in endless reboot loops.

Why wouldn’t KB3081424 eventually install correctly? Because the initial failed install has been found to create a bad entry in the Windows 10 registry which stops its subsequent attempts to reinstall from working correctly.

http://www.forbes.com/sites/gordonkelly/2015/08/08/windows-10-forced-updates-causing-endless-crash-loop/

I was able to download it with no problems :P

Yes Windows ten seems great but I am glad I waited, i don't like the forced updates.

I seem to have no issues either! But you can "Defer updates" for months if you have the pro version

Watch this be a marketing tactic by MS in order to get home users to upgrade :P

I'll be letting the betatesters bugtest W10 properly before I use my free upgrade After all, I have a year.

W8 works just fine for me, my only gripe with it was the lack of a start menu, but then I downloaded the classic start plug-in, which gives you a W7-esque start menu, and since then, I've never had any issues with W8 :-3

While Microsoft has released a tool that you can use to block bad updates, it doesn’t seem to work in this case. Fortunately there is a workaround.

The problem appears to be caused by the failed install writing a bad entry to the Windows registry, and this, in turn, prevents the update from installing the next time it tries. To get around this issue you have to delete some registry keys.

Click Start, type regedit, and hit enter to launch the Windows registry editor.

You should backup the registry before proceeding, just in case making the following changes causes you problems. Highlight ProfileList, right-click, select Export and enter a backup name.

Once backed up, navigate to: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList

With that done, Scan through the ProfileList IDs. Ignore the ones ending in 18, 19, and 20. If you have two or more entries starting with S-1-5-21, then this fix may work for you. If you only have one entry that begins with S-1-5-21, then this fix won't work, and you'll have to try something else. Click on ProfileImagePath for each of the S-1-5-21 entries, and look for users that no longer exist in the registry. If you're not sure which users are valid, click Start, type Computer Management and hit enter. Under Local Users and Groups browse the list of Users. Delete any of the S-1-5-21 keys which shouldn't be there. As with any registry editing, make sure you only delete something if you're comfortable it's safe to do so.

Close regedit and reboot.

Afterwards (or instead of) you can try manually installing the update from:

x86

x64

You can find out more about the error, and possible solution here.

http://betanews.com/2015/08/10/windows-10s-forced-cumulative-update-kb3081424-causing-endless-reboots-but-there-is-a-solution/

Easy solution!

Yep, still glad i haven't upgraded from Windows 7.

So, people have been telling me that the general user is too dumb to realize how important it is to update their systems , yet the solution offered for the problem at hand is supposed to be easy for them?

and how hilarious is it that the friendly method MS offered to stop some updates from being installed, which lots of you argued it was a good enough solution, doesn't even work in this case? Very funny.

Hmm, that's concerning.

I still plan to upgrade later this week.

I upgraded to Win 10 within the first 4 days of it being released and i've had zero problems with it. Guess it depends on what kind of computer you have? :/