Home > Windows Update > Send Failed With Hr = 80072efd

Send Failed With Hr = 80072efd

Contents

This will give you the exact >> policies that are actually applying on that client, and if you dont find >> the update policy pointing to your WSUS that might be PASS                Winhttp local machine access type                                        Winhttp local machine Proxy. . . . . . . . . .  NONE                Winhttp local machine ProxyBypass. . . . . . Mar 6, 2015 at 6:05 UTC That's why.  The port didn't change until 2012.  You don't need to specify it on 2008 or lower.  Remove that from the GPO and you Stay logged in Welcome to Windows Vista Tips Welcome to Windows Vista Tips, your resource for help for any tech support and computing help with Windows Vista.. his comment is here

error 0x80072efd 2013-01-3015:21:58:153 772a54MiscWARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. This patch has been applied to the server. Augusto Alvarez wrote: > You have a different GPO applied to the domain besides the Default > Domain Policy? > > Enforce the WSUS GPO, this way you'll be certain that TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server SharePoint Products Skype for Business See all products

Send Failed With Hr = 80072efd

PASS VerifyWUServerURL() failed with hr=0x80072efd A connection with the server could not be established     2008-04-15 18:28:38:330  924 22ea4 AU #############2008-04-15 18:28:38:330  924 22ea4 AU ## START ##  AU: Search for updates2008-04-15 18:28:38:330  924 22ea4 AU #########2008-04-15 18:28:38:330  924 22ea4 AU <<## SUBMITTED ## AU: Search myers78 posted Jul 3, 2015 ADMT 3.2 Source domain access issue stives1974 posted May 6, 2015 Loading... Also, ensure FIPS-140 compliant algorithms are disabled on the WSUS server, as they do not appear to be supported by the WU clients.

Let’s see the procedure for; Resolving at the Client Side. You may see this error on SUS Server in Synchronization Log as well as on the client in C:\Windows\Windows Update.log or C:\Windows\WindowsUpdate.log(without space) Error Description: This error means "cannot connect to Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>2008-04-15 18:28:38:611  924 2275c Misc WARNING: WinHttp: SendRequestUsingProxy failed for . Fatal: Selfupdate Check Failed, Err = 0x80072efd I'll wait for someone else's answer >> 2008-04-21 19:55:54:653 784 c9c PT Initializing simple targeting cookie, >> clientId = 86412d27-3723-41ee-bc9f-d8652aa20c57, >> target group = "Workstations", >> DNS name = pc1.test.com The

Proxy List used: <10.86.130.130:8887> Bypass List used : > > <> Auth Schemes used : <> > > 2008-04-21 19:41:29:281 784 c9c PT + Last proxy send request failed > > Clientdiag Tool I have tried the following steps: Reset the WSUS Client (steps at the bottom of this post). I've changed the address in the default domain policy and searched for any other policies that might contain the old address and have found nothing. WinHTTP does not support auto-discovery and configuration script-based proxy settings.

Well, in some cases the situation is even worse; the clients do not have proxy server in their environment

I see you use a public website address. –Jak Nov 24 '09 at 16:12 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up Scan Failed With Error = 0x80072efd No, create an account now. After you run proxycfg.exe you need to restart Automatic Updates Services. PASS Winhttp local machine access type Winhttp local machine Proxy. . . . . . . . . .

Clientdiag Tool

share|improve this answer answered Aug 26 '09 at 22:47 dmoisan 43726 Existing clients (i.e ones that were build and configured to use the old WSUS server) appear in the Also possibly reinstall WUA on one of the workstations to see if this corrects the issue. Send Failed With Hr = 80072efd I've run gpupdate /force and wuauclt /detectnow on all the problem clients and despite the fact that they indicate the gp has been applied successfully the old address still shows up Windows Update Client Failed To Detect With Error 0x80072efd Wsus I'll wait for someone else's answer > > >> 2008-04-21 19:55:54:653 784 c9c PT Initializing simple targeting cookie, > >> clientId = 86412d27-3723-41ee-bc9f-d8652aa20c57, > >> target group = "Workstations", > >>

Without being hands-on, I can only speculate.  I think that you may have something blocking your inbound ports on the SCE server itself.  Presuming that 'FQDN' was your way of masking I checked the Windows Update Log file and got the below. To do this I populated a list of all computers in the domain using the DSQUERY tool. I then had the user replace wsus with the actual server IP address and this also failed which tells me its not a DNS issue. Failure Software Synchronization Windows Update Client Failed To Detect With Error 0x80072efd

Proxy List used: Bypass List used : 2009-08-27 12:45:05+0100 1012 6ac Send failed with hr = 80072efd. 2009-08-27 12:45:05+0100 1012 6ac SendRequest failed with hr = 80072efd. Proxy List used: Bypass List used : <(null)> Auth Schemes used : <> -------------------------------------- To resolve this,

(1) In your computer's Local Area Network (LAN) settings, the automatically I put in the actual IP address in the URL and it connected. 0 Poblano OP Brock3810 Mar 6, 2015 at 5:57 UTC DNS issue maybe? 0 Reboot then from a command prompt run wuauclt.exe /detectnow. (and you say you can use IE to get to the sites, so I'm assuming that's from one of the clients?

I went through the WSUS configuration, all was correct. 80072efd Windows Update error 0x80072efd2008-04-15 18:28:38:627  924 2275c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages

Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2009-04-21 15:45:25:553 836 e00 Misc WARNING: WinHttp: SendRequestUsingProxy failed for .

Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily. You may see this error on Automatic Update Client or on the SUS Server itself while synchronizing with Microsoft Update Server.

Resolution: I have found a workaround to troubleshoot this Elegant zebra striping for Grid? Kb836941 Privacy statement  © 2016 Microsoft.

Windows 8 Won't Shutdown Dell Wireless Driver Citrix Gateway 3.0 - The server certifiate specifi... It seems that if you have any other web site running on port 80 on your WSUS server then you HAVE to create a virtual directory called selfupdate and point it Join & Ask a Question Need Help in Real-Time? PASS  Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . .

Are you able to get into the WSUS console on the server? This can be found under the following URL: http://support.microsoft.com/kb/2720211 I then wanted all computers in my domain to attempt to detect new updates using the wuauclt.exe /discovernow, to ensure the WSUS PASS Background Intelligent Transfer Service is running. . . It's showing that the >system is getting the policy with the old address, but indicates it's the >same policy, "default domain policy" under "Winning GPO".

About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up PASS        Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . codeDom posted Oct 13, 2016 SBS 2003 Sharepoint Database... But newly installed pc has no probleam to connect wsus and get patch.

I tried http://wsus/selfupdate/wuident.cab   without the port and it connected. 0 Mace OP LarryG. NOTE: For Outlook 2016 and 2013 perform the exact same steps. connect to WSUS Server Andrey, Mar 2, 2006, in forum: Update Services Replies: 1 Views: 367 Lawrence Garvin \(MVP\) Mar 2, 2006 Some clients not connecting to WSUS with error Error: Looking into that now. –Richard Slater Aug 27 '09 at 11:29 add a comment| up vote 1 down vote Try this on the client: Stop the Automatic Updates service.