How To Fix Windows Update Client Failed To Detect With Error 0x8024400a (Solved)

Home > Windows Update > Windows Update Client Failed To Detect With Error 0x8024400a

Windows Update Client Failed To Detect With Error 0x8024400a

Join Now I just recently installed WSUS 3.2.7600.226 on a Windows Server 2008 R2 Standard. PASS Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . Don't know why.. When computers with products related to Office 2003 talk to such a server, the web service is unable to process the approvals resulting in the detection failure. have a peek here

For more reference: http://blogs.technet.com/b/sus/archive/2009/05/05/resolving-the-duplicate-susclientid-issue-or-why-don-t-all-my-clients-show-up-in-the-wsus-console.aspx As you said,after some time, the SusIDs reset on the client, which indicates to me that it's talking to WSUS.Did you test for patch deployment?Make sure that First make sure the update is declined. Also, are there any other web-based apps or services installed on the WSUS server? If the update is not yet declined, right click on the update and decline it.

thanks. I was thinking maybe a bad tz issue but not sure.as far as gpupdate its usually used there to set the wsus settings so that it speeds up reporting in. · The clients are Windows XP.Every time I try to update Windows XP, I get errors in the WindowsUpdate.log file. Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free.

  • It won't approve for me as it is superseded by SP2 and 3.
  • i.
  • If you run WBEMTEST on the machine and unable to connect to the root means an issue with WMI on the workstation.
  • In short I'm thinking that there HAS to be something not right on the server side.
  • I have changed the port  number that the client is looking for on the WSUS server (from 80 to 8530 as suggested in a few forms Changed this back being that
  • Here's their workaround from the MS tech: Thank you for the log.
  • really odd.
  • Cloned PCs not appearing in WSUS?

I still need to test this further to make sure that all clients can communicate with the WSUS server, but over all i think im good to go! However, I ran through the steps a couple of times & then manually resynchronized the WSUS server. Here is a script I often use to get troublesome clients working, remember for 2008 to run it as administrator.@echo onnet stop "automatic updates"net stop "Windows Update"net stop "bits"REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" NONE User IE AutoConfig URL Proxy . . . . . . . . .

Setting the wrong port on the URL should return an HTTP 404 error! That's not an option at this point. Please let me know if you need further info from me. Click All Computers again and change selection to "Not Approved", Click OK. 4.

Click All Computers again and change selection to "Not Approved", Click OK. 4. Greetings Friday, May 11, 2012 10:49 AM Reply | Quote 0 Sign in to vote I believe I found my issue and it was indeed port related. Another possible issue I also found is that you set (http://wsusservername:8050). The error you see repeated in the log, 0x8024400E, is consistent with an issue that has been appearing recently.

Just tried something: I changed the WSUS for this one, just told him to report to the old one we used before. The necessary procedure is documented in KB903262. Forgive me. Edited by Clarence ZhangModerator Thursday, May 10, 2012 7:53 AM Marked as answer by K_Mart Friday, May 11, 2012 4:00 PM Thursday, May 10, 2012 7:22 AM Reply | Quote Moderator

Thank you for taking the time to post back your resolution. http://sysgsm.com/windows-update/windows-update-client-failed-to-detect-with-error-0xc8000408.html I'm a Newbie. codeDom posted Oct 13, 2016 SBS 2003 Sharepoint Database... Creating your account only takes a few minutes.

If it is declined, you cannot Approve the Office 2003 Service Pack 1 because it is experied. In the Approve Updates dialog that opens, just click OK without making any changes to the approval settings. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Check This Out The official documents indicate it should be 8530(If 80 is used.) Pls don't use any other ports to see whether it works.

Google just disclosed a major Windows bug - and Microsoft isn't happy [Security] by andyross271. When computers with products related to Office 2003 talk to such a server, the web service is unable to process the approvals resulting in the detection failure. Decline it. 2.

SMF 2.0.11 | SMF © 2015, Simple Machines Page created in 0.103 seconds with 24 queries.

Read this thread! 0 Back to top of the page up there ^ MultiQuote Reply #7 MadsBen Newbie Group: Regular Members Posts: 3 Joined: 23-Jun-08 Posted 23 Jun 2008, 04:01 It's also mandatory for the new version of MBSA, 2.0.1. NOTE: the workaround below didn't work at first because the problem update was expired. Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More...

Rate Changes 12/1/16 [OptimumOnline] by dm145360. Note: If you have a hierarchy of WSUS servers, these steps must be performed on each server, starting with the top-level server. i. this contact form Dismiss the Approval Progress dialog that appears.

Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL Next, decline the update. Sign Up Now! I've posted some root cause information and steps to resolve below.

Right click on the update and select the 'Approve...' option in the context menu. The necessary procedure is documented in KB903262. Forgive me.