Hi
You may refer to the following article and check if it helps:
You may also refer to the article and try the steps provided:
Temporary connection-related errors may occur when you use Windows Update or Microsoft Update
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After getting a new computer (Lenovo) just a couple of weeks ago, set it up last weekend (Sunday, 24 June), performed a number of Windows Updated to make it current, then on Tuesady (26 June), I started getting the error 80072ee2. Initially contacted manufacture but got directed to the problem as a SW issue...... Am doing a bit of research but cannot find the smoking gun fix in the forum. If someone has the right shortcut to the right solution, please let me know. Some further detail:
I reconnected the machine the old machine, which is a VISTA OS (eMachines), to get files from it to transfer to the new machine. It had been powered down about 7 to 9 days, so it had to go through some anti-virus/network security suite updates (ESET):
I found this coincidence/timeframe interesting and wondered if the occurrence of the error may have a common problem (corrupt download or something in the download that was not supposed to be). I am more interested in the W7 solution as the VISTA is being retired after the new machine is reliably and securely up and running.
As mentioned earlier, if someone has the right shortcut to the right solution, please let me know. Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi
You may refer to the following article and check if it helps:
You may also refer to the article and try the steps provided:
Temporary connection-related errors may occur when you use Windows Update or Microsoft Update
Tried to paste the text file into the window but is much larger than the 60,000 characters allowed. If i can email it or place it into a dropp box, let me know.
I do not know the full details of what it alll means but I can identify when "things changed" from working very well to not working.
By the way. I did find a text file titled Windows update that appears to be a log of the attempts I have tried. Around 9:30 PM on the 26th of June is when the errorcode appeared. I can send a copy if you like.
Observation and attempts over the past few days have been unsuccessful in connecting to Windows Update. As far as I can tell the conditions in your response on July 2nd have been accomplished with no resolution. Here is an update in the change of configuration on the machine and actions taken:
Observations:
So. What's next?
Just a question or 2:
I did not start the effort outlined above right away. I took a little time to do some observations and see if all looked OK before I got to deep. I did have an occurrence where I was able to get to Windows Update on both machines but not on a consistent basis.
So, just now got into looking at this again. I was about to discount the FixIt (because I ran it before with no apparent fix) but seemed prudent to cover all the bases and run again (may have been a different version - I did not think to capture that version data). It appears to have accomplished the task. Have initiated Windows updates twice and both ran (one with updates and the other to tell me I was current).
I also wondered just how much of the error may be related to the fires here out west. Not sure where the servers are but with all the activity in supporting and conducting fire fighting operations, just how much bandwidth got used up, and what was there was degraded because some redundant paths may have been down.
So for now, I will claim a conditional success. I will take some time to observe some more and determine if the machine's behavior warrants declaring the issue resolved in a few days. Will report back and let you know the results. Thanks.