Users across the board are failing Windows 10 Updates with 0x8024002e
TL;DR: Microsoft Updates are failing with 0x8024002e using WSUS or straight from Microsoft. We run Windows 10, and it is affecting most of our 150 workstations.
--------------------------
We have been running (with spotty success) a WSUS server for several years, and it periodically blows up. Fine. This most recent time I set a new one up from scratch, synced and let the GPO do its thing. At some point in time, I'm not sure exactly which Patch Tuesday, people got 0x8024002e error across the board. It wouldn't even try on the workstation, if you hit "Update" it would immediately return the error.
So, I changed the GPO to let people download MS Updates from MS, and eliminated WSUS. Well, people get a list of waiting updates, but they are basically failing with the same error.
I'm familiar with Update blowouts, and all the byzantine steps you're supposed to take to rectify it, and most of the time it fails and I've wasted 45 minutes going through all the various suggestions online...which usually link back to the same two or three solutions (stop the services, rename SoftwareDistribution and catroot2, pray, reset security contexts, blah blah blah). 0x8024002e seems to be a pretty nebulous error. My feeling is WSUS corrupted the updates somehow, and now they can't get the updates from MS either.
So, not only have the solutions really not worked, but even if that were a solution, it would take roughly a week to do that on every workstation. I'm not a Powershell expert, so it would take even longer to script the fix and fire from a GPO
My question is, well, has anybody found a viable solution to updates failing? If there is a solution, can it be done centrally without slogging through the command prompt on 150 computers? We run Windows 10 Enterprise, 1607...because Creator's Update is in the list of backed up failures...
I've attached a screenshot of the error. Yes, for me it's been stuck on this damn Ricoh driver, and ooooh, believe me, I've tried every MS tool to hide it, eradicate it, ignore it, refuse driver updates and it won't stop trying to install it. Other people have varying numbers of failed/stuck updates, or long lists of failures in their history going back about 60 days. Not sure what might have happened that day.
--------------------------
We have been running (with spotty success) a WSUS server for several years, and it periodically blows up. Fine. This most recent time I set a new one up from scratch, synced and let the GPO do its thing. At some point in time, I'm not sure exactly which Patch Tuesday, people got 0x8024002e error across the board. It wouldn't even try on the workstation, if you hit "Update" it would immediately return the error.
So, I changed the GPO to let people download MS Updates from MS, and eliminated WSUS. Well, people get a list of waiting updates, but they are basically failing with the same error.
I'm familiar with Update blowouts, and all the byzantine steps you're supposed to take to rectify it, and most of the time it fails and I've wasted 45 minutes going through all the various suggestions online...which usually link back to the same two or three solutions (stop the services, rename SoftwareDistribution and catroot2, pray, reset security contexts, blah blah blah). 0x8024002e seems to be a pretty nebulous error. My feeling is WSUS corrupted the updates somehow, and now they can't get the updates from MS either.
So, not only have the solutions really not worked, but even if that were a solution, it would take roughly a week to do that on every workstation. I'm not a Powershell expert, so it would take even longer to script the fix and fire from a GPO
My question is, well, has anybody found a viable solution to updates failing? If there is a solution, can it be done centrally without slogging through the command prompt on 150 computers? We run Windows 10 Enterprise, 1607...because Creator's Update is in the list of backed up failures...
I've attached a screenshot of the error. Yes, for me it's been stuck on this damn Ricoh driver, and ooooh, believe me, I've tried every MS tool to hide it, eradicate it, ignore it, refuse driver updates and it won't stop trying to install it. Other people have varying numbers of failed/stuck updates, or long lists of failures in their history going back about 60 days. Not sure what might have happened that day.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh, yeah, I did try that wushowhide.diagcab before and it stubbornly wouldn't go away. Now it did with the change, so looks like we screwed the pooch with the GPO.
Thanks for the update and I was happy to help
Glad to help. Cheers!
ASKER
Thank you for your help, that sent me in the right direction!