Уведомление об ошибке с кодом 0x80072ee5 обычно возникает в двух случаях. Во-первых, она может появиться в Outlook после обновления до Windows 10. Во-вторых, при обновлении серверных версий Виндоус через WSUS. В обоих случаях причиной является некорректность настроек.
Пути решения для каждой ситуации отличаются:
- Для Outlook. Убедитесь, что все существующие апдейты установлены на компьютер. Запустите Аутлук. Удалите оттуда все имеющиеся аккаунты. Перезапустите ОС. Добавьте новый почтовый аккаунт, но он обязательно должен не от почтового сервиса Майкрософт.
- Для WSUS. Проверьте, что установлен верный URL в значении «Specify intranet Microsoft update services location» для групповой политики. Возможно, в конце адреса был случайно вставлен пробел, который и вызывал ошибку 0x80072ee5.
- Remove From My Forums
-
Question
-
I have a Windows Server 2008 R2 which should get the updates from a WSUS runnung on Windows Server 2012 R2 Standard
trying to update returns the erroe Code 80072EE5.At the WSUS Management Console the server shows up with 0% and no status report.
The WindowsUpdate.log ist as follows:
2015-08-11 11:40:15:485 900 289c AU Triggering AU detection through DetectNow API
2015-08-11 11:40:15:485 900 289c AU Triggering Online detection (non-interactive)
2015-08-11 11:40:15:485 900 32f8 AU #############
2015-08-11 11:40:15:485 900 32f8 AU ## START ## AU: Search for updates
2015-08-11 11:40:15:485 900 32f8 AU #########
2015-08-11 11:40:15:486 900 32f8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:486 900 101c Agent *************
2015-08-11 11:40:15:486 900 101c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-08-11 11:40:15:486 900 101c Agent *********
2015-08-11 11:40:15:486 900 101c Agent * Online = Yes; Ignore download priority = No
2015-08-11 11:40:15:486 900 101c Agent * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1
or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
2015-08-11 11:40:15:486 900 101c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-08-11 11:40:15:486 900 101c Agent * Search Scope = {Machine}
2015-08-11 11:40:15:486 900 101c Setup Checking for agent SelfUpdate
2015-08-11 11:40:15:487 900 101c Setup Client version: Core: 7.6.7600.320 Aux: 7.5.7601.17514
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: DownloadFileInternal failed for
http://10.90.229.193:8530 /selfupdate/wuident.cab: error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Setup FATAL: DownloadCab failed, err = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Setup WARNING: SelfUpdate check failed to download package information, error = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Setup FATAL: SelfUpdate check failed, err = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent * WARNING: Skipping scan, self-update check returned 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent * WARNING: Exit code = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent *********
2015-08-11 11:40:15:487 900 101c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-08-11 11:40:15:487 900 101c Agent *************
2015-08-11 11:40:15:487 900 101c Agent WARNING: WU client failed Searching for update with error 0x80072ee5
2015-08-11 11:40:15:488 900 31c8 AU >>## RESUMED ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:488 900 31c8 AU # WARNING: Search callback failed, result = 0x80072EE5
2015-08-11 11:40:15:488 900 31c8 AU # WARNING: Failed to find updates with error code 80072EE5
2015-08-11 11:40:15:488 900 31c8 AU #########
2015-08-11 11:40:15:488 900 31c8 AU ## END ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:488 900 31c8 AU #############
2015-08-11 11:40:15:488 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:15:488 900 31c8 AU AU setting next detection timeout to 2015-08-11 14:40:15
2015-08-11 11:40:15:488 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:15:489 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:20:487 900 101c Report REPORT EVENT: {ABC3ACB3-9744-49B2-B123-463938BDE442} 2015-08-11 11:40:15:487+0200 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee5 SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x80072ee5.
2015-08-11 11:40:20:495 900 101c Report CWERReporter::HandleEvents — WER report upload completed with status 0x8
2015-08-11 11:40:20:495 900 101c Report WER Report sent: 7.6.7600.320 0x80072ee5 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2015-08-11 11:40:20:495 900 101c Report CWERReporter finishing event handling. (00000000)
2015-08-11 11:54:07:839 900 101c PT WARNING: PTError: 0x80072ee5
2015-08-11 11:54:07:839 900 101c PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
2015-08-11 11:54:07:839 900 101c Report WARNING: Reporter failed to upload events with hr = 80072ee5.
2015-08-11 12:19:41:859 900 2748 PT WARNING: PTError: 0x80072ee5
2015-08-11 12:19:41:859 900 2748 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
2015-08-11 12:19:41:859 900 2748 Report WARNING: Reporter failed to upload events with hr = 80072ee5.Can somebody give me a clue?
Answers
-
Try this thread:
Windows 2008 update error 80072EE5
Basically that error is caused by an incorrect url in the «Specify intranet Microsoft update services location» GPO, like in the thread above; a trailing space.
Rolf Lidvall, Swedish Radio (Ltd)
-
Marked as answer by
Tuesday, August 11, 2015 1:25 PM
-
Marked as answer by
check
Best Answer
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
Was this post helpful?
thumb_up
thumb_down
View Best Answer in replies below
6 Replies
-
Can you telnet from the problem 2012 servers to the port and IP of your WSUS server?
Also, from a quick search that error states that «The 0x80072ee5 error is caused by an invalid URL in the «Specify intranet Microsoft update services location» policy. While you may not have setup WSUS yet, apparently the policy configurations have told the clients that’s where they should get updates from — and the URL configured is invalid.»
Have you double checked the «Specify intranet Microsoft update services location» for these machines to make sure they are getting the correct WSUS url?
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
Can you telnet from the problem 2012 servers to the port and IP of your WSUS server?
Also, from a quick search that error states that «The 0x80072ee5 error is caused by an invalid URL in the «Specify intranet Microsoft update services location» policy. While you may not have setup WSUS yet, apparently the policy configurations have told the clients that’s where they should get updates from — and the URL configured is invalid.»
Have you double checked the «Specify intranet Microsoft update services location» for these machines to make sure they are getting the correct WSUS url?
Not sure if I need to download telnet or not but it is not a feature available by default in Server 2012 at least not from the command line.
Also All of my other clients have to go to the same URL and they do not have a problem. Just the 2012 client has this issue. The settings are the same either way. The URL is http://Servername:8530
Was this post helpful?
thumb_up
thumb_down
-
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
BSOD’D wrote:
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Edit: The sad part is I have been working on trying to resolve this issue on my own for a couple of hours now
I cannot believe I did that.
1 found this helpful
thumb_up
thumb_down
-
VericomITguy wrote:
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Someday, somewhere someone is going to write a parody about this issue. It could go something like this.
We have the backslash, the frontslash and the pipe.
Which one do I use?
This is why I gripe.
Should the backward one be forward or the forward one be back?
Or maybe it’s the pipe?
These decisions make me crack.
Well, you get my drift. I’ll be going back to work now!
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
SteveFL wrote:
VericomITguy wrote:
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Someday, somewhere someone is going to write a parody about this issue. It could go something like this.
We have the backslash, the frontslash and the pipe.
Which one do I use?
This is why I gripe.
Should the backward one be forward or the forward one be back?
Or maybe it’s the pipe?
These decisions make me crack.
Well, you get my drift. I’ll be going back to work now!
Bravo sir! Bravo.
Was this post helpful?
thumb_up
thumb_down
I cannot believe I did that. - Remove From My Forums
-
Question
-
I have a Windows Server 2008 R2 which should get the updates from a WSUS runnung on Windows Server 2012 R2 Standard
trying to update returns the erroe Code 80072EE5.At the WSUS Management Console the server shows up with 0% and no status report.
The WindowsUpdate.log ist as follows:
2015-08-11 11:40:15:485 900 289c AU Triggering AU detection through DetectNow API
2015-08-11 11:40:15:485 900 289c AU Triggering Online detection (non-interactive)
2015-08-11 11:40:15:485 900 32f8 AU #############
2015-08-11 11:40:15:485 900 32f8 AU ## START ## AU: Search for updates
2015-08-11 11:40:15:485 900 32f8 AU #########
2015-08-11 11:40:15:486 900 32f8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:486 900 101c Agent *************
2015-08-11 11:40:15:486 900 101c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-08-11 11:40:15:486 900 101c Agent *********
2015-08-11 11:40:15:486 900 101c Agent * Online = Yes; Ignore download priority = No
2015-08-11 11:40:15:486 900 101c Agent * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1
or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
2015-08-11 11:40:15:486 900 101c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-08-11 11:40:15:486 900 101c Agent * Search Scope = {Machine}
2015-08-11 11:40:15:486 900 101c Setup Checking for agent SelfUpdate
2015-08-11 11:40:15:487 900 101c Setup Client version: Core: 7.6.7600.320 Aux: 7.5.7601.17514
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: WinHttp: Initialize failed with 0x80072ee5
2015-08-11 11:40:15:487 900 101c Misc WARNING: DownloadFileInternal failed for
http://10.90.229.193:8530 /selfupdate/wuident.cab: error 0x80072ee5
2015-08-11 11:40:15:487 900 101c Setup FATAL: DownloadCab failed, err = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Setup WARNING: SelfUpdate check failed to download package information, error = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Setup FATAL: SelfUpdate check failed, err = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent * WARNING: Skipping scan, self-update check returned 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent * WARNING: Exit code = 0x80072EE5
2015-08-11 11:40:15:487 900 101c Agent *********
2015-08-11 11:40:15:487 900 101c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-08-11 11:40:15:487 900 101c Agent *************
2015-08-11 11:40:15:487 900 101c Agent WARNING: WU client failed Searching for update with error 0x80072ee5
2015-08-11 11:40:15:488 900 31c8 AU >>## RESUMED ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:488 900 31c8 AU # WARNING: Search callback failed, result = 0x80072EE5
2015-08-11 11:40:15:488 900 31c8 AU # WARNING: Failed to find updates with error code 80072EE5
2015-08-11 11:40:15:488 900 31c8 AU #########
2015-08-11 11:40:15:488 900 31c8 AU ## END ## AU: Search for updates [CallId = {9D6F312B-28CE-4DDF-9B8B-033A566D25CF}]
2015-08-11 11:40:15:488 900 31c8 AU #############
2015-08-11 11:40:15:488 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:15:488 900 31c8 AU AU setting next detection timeout to 2015-08-11 14:40:15
2015-08-11 11:40:15:488 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:15:489 900 31c8 AU Successfully wrote event for AU health state:0
2015-08-11 11:40:20:487 900 101c Report REPORT EVENT: {ABC3ACB3-9744-49B2-B123-463938BDE442} 2015-08-11 11:40:15:487+0200 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee5 SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x80072ee5.
2015-08-11 11:40:20:495 900 101c Report CWERReporter::HandleEvents — WER report upload completed with status 0x8
2015-08-11 11:40:20:495 900 101c Report WER Report sent: 7.6.7600.320 0x80072ee5 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2015-08-11 11:40:20:495 900 101c Report CWERReporter finishing event handling. (00000000)
2015-08-11 11:54:07:839 900 101c PT WARNING: PTError: 0x80072ee5
2015-08-11 11:54:07:839 900 101c PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
2015-08-11 11:54:07:839 900 101c Report WARNING: Reporter failed to upload events with hr = 80072ee5.
2015-08-11 12:19:41:859 900 2748 PT WARNING: PTError: 0x80072ee5
2015-08-11 12:19:41:859 900 2748 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
2015-08-11 12:19:41:859 900 2748 Report WARNING: Reporter failed to upload events with hr = 80072ee5.Can somebody give me a clue?
Answers
-
Try this thread:
Windows 2008 update error 80072EE5
Basically that error is caused by an incorrect url in the «Specify intranet Microsoft update services location» GPO, like in the thread above; a trailing space.
Rolf Lidvall, Swedish Radio (Ltd)
-
Marked as answer by
Tuesday, August 11, 2015 1:25 PM
-
Marked as answer by
Уведомление об ошибке с кодом 0x80072ee5 обычно возникает в двух случаях. Во-первых, она может появиться в Outlook после обновления до Windows 10. Во-вторых, при обновлении серверных версий Виндоус через WSUS. В обоих случаях причиной является некорректность настроек.
Пути решения для каждой ситуации отличаются:
- Для Outlook. Убедитесь, что все существующие апдейты установлены на компьютер. Запустите Аутлук. Удалите оттуда все имеющиеся аккаунты. Перезапустите ОС. Добавьте новый почтовый аккаунт, но он обязательно должен не от почтового сервиса Майкрософт.
- Для WSUS. Проверьте, что установлен верный URL в значении «Specify intranet Microsoft update services location» для групповой политики. Возможно, в конце адреса был случайно вставлен пробел, который и вызывал ошибку 0x80072ee5.
Are you currently experiencing problems with Windows Update? One of the most common error codes of Windows Update is error ‘0x80072EE5’.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
On this page, you will find more information about the most common causes and most relevant solutions for the Windows Update error ‘0x80072EE5’. Do you need help straight away? Visit our support page.
Error information
How to solve Windows Update error 0x80072EE5
We’ve created a list of solutions which you can follow if you want to solve this Windows Update problem yourself. Do you need more help? Visit our support page if you need professional support with Windows Update right away.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
Have you found a solution yourself, but it is not in the list? Share your solution in the comments below.
Need more help?
Do you need more help?
Tech experts are ready to answer your questions.
Ask a question
check
Best Answer
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsUpdate
Was this post helpful?
thumb_up
thumb_down
View Best Answer in replies below
6 Replies
-
Can you telnet from the problem 2012 servers to the port and IP of your WSUS server?
Also, from a quick search that error states that «The 0x80072ee5 error is caused by an invalid URL in the «Specify intranet Microsoft update services location» policy. While you may not have setup WSUS yet, apparently the policy configurations have told the clients that’s where they should get updates from — and the URL configured is invalid.»
Have you double checked the «Specify intranet Microsoft update services location» for these machines to make sure they are getting the correct WSUS url?
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
Can you telnet from the problem 2012 servers to the port and IP of your WSUS server?
Also, from a quick search that error states that «The 0x80072ee5 error is caused by an invalid URL in the «Specify intranet Microsoft update services location» policy. While you may not have setup WSUS yet, apparently the policy configurations have told the clients that’s where they should get updates from — and the URL configured is invalid.»
Have you double checked the «Specify intranet Microsoft update services location» for these machines to make sure they are getting the correct WSUS url?
Not sure if I need to download telnet or not but it is not a feature available by default in Server 2012 at least not from the command line.
Also All of my other clients have to go to the same URL and they do not have a problem. Just the 2012 client has this issue. The settings are the same either way. The URL is http://Servername:8530
Was this post helpful?
thumb_up
thumb_down
-
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsUpdate
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
BSOD’D wrote:
Telnet is built in you just need to enable it
Also check the resgitry settings to see if these server got the URL for your WSUS server
I think it is here — HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsUpdate
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Edit: The sad part is I have been working on trying to resolve this issue on my own for a couple of hours now
I cannot believe I did that.
1 found this helpful
thumb_up
thumb_down
-
VericomITguy wrote:
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Someday, somewhere someone is going to write a parody about this issue. It could go something like this.
We have the backslash, the frontslash and the pipe.
Which one do I use?
This is why I gripe.
Should the backward one be forward or the forward one be back?
Or maybe it’s the pipe?
These decisions make me crack.
Well, you get my drift. I’ll be going back to work now!
Was this post helpful?
thumb_up
thumb_down
-
OP
Sajiin
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
SteveFL wrote:
VericomITguy wrote:
ARRRGGGHHHH!!!!! F me. I could kick myself in the face. I had the damn slashes the wrong way. I had http:\ not http:// . Don’t ask me why that happened. Must have just been out of it the day I set it up. Thanks for all the help BSOD’D.
Someday, somewhere someone is going to write a parody about this issue. It could go something like this.
We have the backslash, the frontslash and the pipe.
Which one do I use?
This is why I gripe.
Should the backward one be forward or the forward one be back?
Or maybe it’s the pipe?
These decisions make me crack.
Well, you get my drift. I’ll be going back to work now!
Bravo sir! Bravo.
Was this post helpful?
thumb_up
thumb_down
 svpr15 |
|
|
Статус: Новичок Группы: Участники
Зарегистрирован: 07.02.2018(UTC) |
При создании подписи произошла ошибка: Не удалось создать подпись из-за ошибки: The URL is invalid (0x80072EE5) |
 |
|
|
Михаил Селезнёв |
|
|
Статус: Сотрудник Группы: Участники
Зарегистрирован: 05.04.2017(UTC) Сказал «Спасибо»: 3 раз |
Добрый день! |
|
|
|
| Пользователи, просматривающие эту тему |
|
Guest |
Быстрый переход
Вы не можете создавать новые темы в этом форуме.
Вы не можете отвечать в этом форуме.
Вы не можете удалять Ваши сообщения в этом форуме.
Вы не можете редактировать Ваши сообщения в этом форуме.
Вы не можете создавать опросы в этом форуме.
Вы не можете голосовать в этом форуме.
Are you currently experiencing problems with Windows Update? One of the most common error codes of Windows Update is error ‘0x80072EE5’.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
On this page, you will find more information about the most common causes and most relevant solutions for the Windows Update error ‘0x80072EE5’. Do you need help straight away? Visit our support page.
Error information
How to solve Windows Update error 0x80072EE5
We’ve created a list of solutions which you can follow if you want to solve this Windows Update problem yourself. Do you need more help? Visit our support page if you need professional support with Windows Update right away.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
Have you found a solution yourself, but it is not in the list? Share your solution in the comments below.
Need more help?
Do you need more help?
Tech experts are ready to answer your questions.
Ask a question