Receiving a 0x8024402f error after restoring Windows 10 from a backup.

[Moondoggy]

I'm hoping that someone can help me out as I have been unable to find a solution to my problem.


I upgraded to Windows 10 from Windows 7 back on 8/6 and when everything was looking good I backed up my HD with Acronis TrueImage 2015. Unfortunately, my wife was doing something on the PC that caused the machine to go into a booting loop and I was forced to restore the HD from my 8/7 backup. It appeared that the restore worked well until I tried to re-apply all of the patches and updates to Windows 10 and Office. Each time I have tried Windows Update it returns a 0x8024402f error that only says that something bad happened during the update. So far I've been unable to find a solution on the internet for this problem and I was hoping someone has had this problem before and was able to get it fixed. So far.....


I've run the Windows Update troubleshooter and it fixed Windows Update components, however this does not resolve the issue. I have also ran the internet connection troubleshooter and the network adapter troubleshooter and neither found an issue. I don't believe that this is an internet problem however as I can receive and send mail from Outlook 2010 and I can successfully upload and download files from cloud storage and other websites. I have scanned my system files using the SFC /SCANNOW command and it found nothing wrong. I have also performed a DISM command and it didn't find anything either. I have also cleared the files from the SoftwareDistrubtion folder and I've re-registered a bunch of DLL's from a list I found but that hasn't resolved anything either. I have also downloaded and have run the Windows Repair tool from wee.tweaking.com and it didn't fix the problem either. Part of the problem here is that this is Windows 10 and most of the past posts have been in regards to Windows 7 and Windows 8.x. My gut is telling me that this is some sort of permisisons issue or some registry issue that's causing this issue to exists.


So.... Has anyone seen this issue on Windows 10 and has been able to fix the problem? If so can you share with me what you did to get it working again? Thanks.

 

[Moondoggy]

I hate it when this happens.....


I've been fighting this 0x8024402f error for days now and today we turned on our computer and, on it's own, the machine decided to check in with the update server on it's own and downloaded 14 updates on the first pass and then after the first restart it downloaded yet another patch on it's own. I compared the patches that were downloaded on this machine against my laptop who also downloaded several patches today and all 15 patches I have are also on my laptop. I don't know if, in trying certain suggestions to fix the 0x8024402f error I triggered something that required a cold boot but now things are working and I don't know why. I would hate it if this whole time the PC was unable to ask for updates until the update server contacted the PC first to establish an update relationship but I guess that might be possible as I don't believe that there were any new updates until today. Anyway, this is still a mystery and I'm unhappy that I don't have an answer why.

 

[Digerati]

I hate it when this happens.....

I think it is one of Murphy's Laws that says things will screw up over and over again - until you seek help. Then it works just fine.

It is hard to determine what should be when comparing two different computers because of different drivers, different MS apps, and different user customizations. It is even more so between a notebook and PC because the OS, even if the same version, must be configured differently - especially with power management.

Maybe it just needed one more reboot, or one update needed to be installed before another. I don't know but I am glad it seems to have sorted itself out and we appreciate you coming back with your followup post. :thumbsup2:

BTW, how do you have Windows Update set to deliver updates? There are two options. In addition from Microsoft, the default also is to get and send updates to PCs on your local network and PCs on the Internet. That setting scares many of us who may be a bit paranoid about security and outside influences. The other option is to also get and send updates to PCs on your local network only.

The latter is how I have all mine set. That may mean it will take a little longer for all my systems to get updated, but I at least feel safer believing a badguy outside my network cannot send me a compromised update.

 

[Moondoggy]

I hate it when this happens.....

I think it is one of Murphy's Laws that says things will screw up over and over again - until you seek help. Then it works just fine.

It is hard to determine what should be when comparing two different computers because of different drivers, different MS apps, and different user customizations. It is even more so between a notebook and PC because the OS, even if the same version, must be configured differently - especially with power management.

Maybe it just needed one more reboot, or one update needed to be installed before another. I don't know but I am glad it seems to have sorted itself out and we appreciate you coming back with your followup post. :thumbsup2:

BTW, how do you have Windows Update set to deliver updates? There are two options. In addition from Microsoft, the default also is to get and send updates to PCs on your local network and PCs on the Internet. That setting scares many of us who may be a bit paranoid about security and outside influences. The other option is to also get and send updates to PCs on your local network only.

The latter is how I have all mine set. That may mean it will take a little longer for all my systems to get updated, but I at least feel safer believing a badguy outside my network cannot send me a compromised update.

Thanks for the reply and I appreciate the thumbs up on the fact that I posted something about my mystery fix~. Personally, I think it's a disservice to post a problem in the hope of getting an answer and then not replying with an outcome as some other needy individual maybe looking for a solution to the same issue.

In answer to your question about the setup of Windows Update, I have mine setup to update from the local network and PC's on the Internet which I believe is the default setting as my laptop is setup the same way. When I was having the problem I tried switching the settings but it didn't have any impact so I reverted back to the default. I guess I'm not as paranoid as some of my peers.

 

[Digerati]

Personally, I think it's a disservice to post a problem in the hope of getting an answer and then not replying with an outcome as some other needy individual maybe looking for a solution to the same issue.

It is often referred to as "poor forum etiquette". Forums are places for learning so as you noted, no one else has an opportunity to learn. This is a common problem when people "shotgun post" or "cross-post" their problem on multiple sites and forums, then fail to go back to each one of them after finding a solution and posting the resolution.

As for the Windows Update setting, yes, as noted above "and the Internet" is the default setting.

I guess I'm not as paranoid as some of my peers.

No doubt the idea is to relieve some of the bandwidth demands on Microsoft's servers and I understand that. And because keeping our computers current is, by far, one of the best ways to keep our systems secure, I understand Microsoft wanting to update all computers as quickly as possible too. But many users have contracts with their ISPs where they "pay as they go" for their service. And so it is not just paranoia, but donating some of their bandwidth to others they don't know without their permission or knowledge is not something many want to do. IMHO, donating the bandwidth we paid for is NOT something we should be tasked to do without our permission first.

But to the paranoid side, I have NO DOUBTS badguys right now are trying to reverse engineer those protocols to figure out a way to use that exchange of data to distribute their malware. Maybe they won't succeed, but they are a patient bunch and sure are trying.