Anyone having trouble with this update in Windows 10 Pro x64? Released today, 7/24/15. Says it can't be completed (stops at 45%) then does three or four restarts to 'undo' changes. Ran 'chkdsk/f',' now running 'sfc /scannow.' I also ran a fix under Control Panel-->Security and Maintenance-->Troubleshooting-->Fix Problem with Windows Update and it said it fixed something, but did not solve the problem. It's kind of a pain since you can't just hide the update as you could in the past when this occasionally happened. What to do?
I used that login background changer--thought it might have something to do with it since this and one other update knocked it out. The only anti-virus I'm using is Malwarebytes anti-malware. Have you successfully do this update?
the problem is u need all this security updates.....u mite have to do a reset to the OS to fix any corruption u mite have.
Goodness--too much work! The only options are save just your files (no apps) or wipe everything. This happens sometimes--if it becomes a persistent problem I'll examine my options. My philosophy is that I've lived without this patch since Windows 3.0, so I guess I can continue without it in the future. Thanks again for your help!
Maybe there is something wrong when download patch, for example, downloaded file is damaged caused by network, it can not continue to download even re-search, so the patch will stops at 45%.
Just wanted to say you're not the only one with this problem. I've got the same issue with enterprise x64. I upgraded from win 8.1 so I thought maybe that's causing the problem, clean installed w10 ent with format and still the problem persists
I upgraded from 7 and also thought maybe that was the problem. Now, maybe not. I was able to hide it, so it's not the end of the world. Has happened before--just remember, as a client once said to me, "this is Windows."
I got it fixed. I restored a backup that was a big week old from before I had added a bunch of things, thinking it was one of them. The updates kept working no matter what I added, so I was mystified. Then suddenly I ran into the problem again, and realized that I had just deleted a couple of users under the names 'Default.migrated' and 'DefaultAppPool,' maybe some sort of migration from the upgrade. Restored them from the Recycle Bin--problem solved! I'm keeping my fingers crossed nevertheless!