One of our client reported an issue performing windows update on a Windows 2012 Server, it failed with the following error
Windows could not search for new updates with Error Code- 8024402C
I begin with the standard windows update troubleshooting as listed below
1) Restarted Windows update service.
2) Validated the Server is not pointing to a WSUS server (follow the steps below)
open registry editor and navigate to following location
Make sure USEWUSERVER is set to 0, if not make it 0 and reboot the server
As the server is backup, ensure that the value is still 0, if it turns back to 1 then most likely its being pushed by a group policy. You would want to lookup the policy and disable the setting.
Now you can try to Update your Windows. If this helps then great, otherwise go for Next step.
3) Open your Cmd prompt as Administrator and perform the following command
wuauclt /resetauthorization /detectnow
Note- When you run the comands, You’ll not receive any output, but the comands will work.
now again try to Update your Windows. Still error is generated, no problem, just move to next step.
4) Rebuild windows update catelog with below steps
Stop the Windows Update service. Open My Computer. Go to C:\Windows here you can see a folder named SoftwareDistribution. Rename this folder as SoftwareDistribution.old . Now get back to services snap-in and Start the Windows Update services.
In most of the case, rebuilding windows update catelog takes care of the issue, However if you are the special one like me follow the below steps.
Lets check the windows update log file at %systemroot%\WindowsUpdate.Log . This files explains what happens in the back ground when you see the update wheel spinning in front of you.
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>|
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: Send request failed, hr:0x80072ee7|
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-wuredir.cab>. error 0x8024402c|
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c|
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c|
|2015-07-15||17:29:32:687||940||1738||Misc||WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c|
Now it is clear that system is trying to download the cab file from http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-wuredir.cab
but for some reasons, the location isn’t reachable. I tried to open the same URL on my PC and it worked just fine, but when I try to open this url in problem Server then it was not accessible.
I quickly did an nslookup for ds.download.windowsupdate.com, as seen the below screen shot, the server wasn’t able to find it.
If the server is not a member of domain, then you may want to point it to another public DNS server like 126.96.36.199 or 188.8.131.52. However in our case this server was a domain controller and was pointing to itself for DNS.
Obviously this request wasn’t getting resolved by the internal DNS server, it was being forwarded to its forwarder.
We opened the DNS management snap in on the server.
Right Click on the name of the server and select properties.
Then click on “Forwarders” tab.Y ou will see the forwarding IP address here. In our screenshot the IP remains same (184.108.40.206) but it was set to somathing else but we do nothave any screenshot for that.
Put Ip of some well know DNS server like 220.127.116.11 or 18.104.22.168
click ok and ok again.
Now again try to update the Windows, this resolved my issue and hopefully yours as well. Still if the issue persist, then feel free to contact us.
We are always happy to help 🙂
Latest posts by Arshdeep Singh (see all)
- Asus Zenfone 2 Laser- NTFS issue - December 7, 2016
- Change Password for Soonr account in just 3 steps - November 3, 2015
- Windows Update error Codes, Description & Solutions - August 20, 2015