AstroSkipper

@Dave-H I have compared your log to mine. In your log you can see: 2022-01-29 12:28:25:312 1860 cc4 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0000) =========== 2022-01-29 12:28:25:312 1860 cc4 Misc = Process: D:\WIN-NT\System32\svchost.exe 2022-01-29 12:28:25:312 1860 cc4 Misc = Module: D:\WIN-NT\system32\wuaueng.dll 2022-01-29 12:28:25:312 1860 cc4 Service ************* 2022-01-29 12:28:25:312 1860 cc4 Service ** START ** Service: Service startup 2022-01-29 12:28:25:312 1860 cc4 Service ********* 2022-01-29 12:28:25:343 1860 cc4 Agent * WU client version 7.6.7600.256 2022-01-29 12:28:25:343 1860 cc4 Agent * Base directory: D:\WIN-NT\SoftwareDistribution 2022-01-29 12:28:25:343 1860 cc4 Agent * Access type: Named proxy 2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy: https=127.0.0.1:8079 2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy bypass: <local> 2022-01-29 12:28:25:343 1860 cc4 Agent * Network state: Connected In my log you see a difference: 2022-01-29 14:26:34:093 1128 b38 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-29 14:26:34:109 1128 b38 Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-29 14:26:34:109 1128 b38 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-29 14:26:34:093 1128 b38 Service ************* 2022-01-29 14:26:34:109 1128 b38 Service ** START ** Service: Service startup 2022-01-29 14:26:34:109 1128 b38 Service ********* 2022-01-29 14:26:35:140 1128 b38 Agent * WU client version 7.6.7600.256 2022-01-29 14:26:35:140 1128 b38 Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-29 14:26:35:234 1128 b38 Agent * Access type: No proxy 2022-01-29 14:26:35:578 1128 b38 Agent * Network state: Connected Here are my IE LAN-Settings: HTTPSProxy switched off: https://imgur.com/TRquakL HTTPSProxy switched on: https://imgur.com/w19OXo2 https://imgur.com/iuu80if So switch to HTTPSProxy and do the same settings. You can do it by clicking Inet_CurUser_ProxySettings.reg Switching on and off by SysTray icon. Important first screenshot. Automatic Configuration both options are unchecked. And check your hosts file if it is clean related to MU. And in background ProxHTTPSProxy may not be loaded. Post your Windows Update Log once again.

@Dave-H Well, now we are at the same time and your Windows update Agent works as it should be. Microsoft Update error code 0x80072F8F means ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong. Maybe this can help you: Check in your registry if the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate doesn't exist otherwise delete it. Open system panel, click Automatic Updates and check if it is not greyed out. Then select Turn off Automatic Updates. Open Internet Explorer on the Tools menu, click Internet Options. Under Advanced check if check for server certificate revocation is unselected. Then click the Content tab. Under Certificates, click Clear SSL State. Click OK when you receive the message that the SSL cache was successfully cleared. Under Personal information, click AutoComplete. Under Clear AutoComplete history, click Clear Forms. Click OK when you are prompted to confirm the operation. Click Clear Passwords. Click OK when you are prompted to clear all previously saved passwords, and then click OK two more times. Close Internet Explorer. Start ProxHTTPSProxy and then Internet Explorer. Try to access Microsoft Update one more time. Post your Windows Update Log again.

Yeah, in your posted link there is a second link to a Microsoft site https://docs.microsoft.com/en-us/archive/blogs/win7/windows-update-error-80072f8f and setting "time.windows.com" as time server was the recommendation. Anyway try Windows time service for a next short time and try other time servers. I use "ptbtime2.ptb.de" or use one located in your country. Your log shows you have synchronization errors. The good news your WU Agent works properly we have fixed it. The "WARNING: Unable to establish connection to the service. (hr=80004002)" is blown away.

@Dave-H Damn! Quick view of your Windows Update Log shows your Windows Update Agent is working correctly now. That's fine. Ok, which time server do you use for time synchronization? And is your computer part of a domain?

Here you can have a look: https://ryanvm.net/forum/viewforum.php?f=25&sid=56abd568c7cb0f44bc3764c209527f9a

Hi, try looking for old Windows Update Packs for Windows XP and extract them. Maybe some of these updates are included. I have nearly all updates since Service Pack SP3 but only for German version of Windows XP. Some of your requested updates are very old so I don't think they are offered via Microsoft Update but. you can give it a try:

@Dave-H After performing all steps from post do the following steps: 13. Install Restore_WU_XP_2003 again. No reboot at this time. 14. Do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary and injecting wuaueng.dll in the case you find wrong version in folders system32 or system32\dllcache. 15. Reboot your computer. 16. Switch on ProxHTTPSProxy. 17. Try accessing MU again. 18. Post your Windows Update Log. Hope it will work at last.

Of course. Sleep well!

So here is the official instruction from Microsoft how to reset Windows Update. I've crossed out instructions that aren't referring to Windows XP or 2000. Furthermore I've added steps I found that they are missing. Make a backup if you want to perform this. In any case read carefully! Manually reset Windows Update components (KB971058) Important: Follow the steps in this section carefully! Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur! To reset the Windows Update components, follow these steps: 1. Open a command prompt. To do this, use one of the following methods, depending on your version of Windows: Windows 8.1 and Windows 8: From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click Command Prompt, and then select Run as Administrator. Windows XP and earlier versions: Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator. 2. Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. net stop bits net stop wuauserv net stop appidsvc net stop cryptsvc 3. Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter: Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" 4a. If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.). Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak Ren %systemroot%\system32\catroot2 catroot2.bak 4b. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) 5. At a command prompt, type the following command, and then press Enter: cd /d %windir%\system32 6. Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. regsvr32.exe atl.dll regsvr32.exe urlmon.dll regsvr32.exe mshtml.dll regsvr32.exe shdocvw.dll regsvr32.exe browseui.dll regsvr32.exe jscript.dll regsvr32.exe vbscript.dll regsvr32.exe scrrun.dll regsvr32.exe msxml.dll regsvr32.exe msxml3.dll regsvr32.exe msxml6.dll regsvr32.exe actxprxy.dll regsvr32.exe softpub.dll regsvr32.exe wintrust.dll regsvr32.exe dssenh.dll regsvr32.exe rsaenh.dll regsvr32.exe gpkcsp.dll regsvr32.exe sccbase.dll regsvr32.exe slbcsp.dll regsvr32.exe cryptdlg.dll regsvr32.exe oleaut32.dll regsvr32.exe ole32.dll regsvr32.exe shell32.dll regsvr32.exe initpki.dll regsvr32.exe wuapi.dll regsvr32.exe wuaueng.dll regsvr32.exe wuaueng1.dll regsvr32.exe wucltui.dll regsvr32.exe wups.dll regsvr32.exe wups2.dll regsvr32.exe wuweb.dll regsvr32.exe qmgr.dll regsvr32.exe qmgrprxy.dll regsvr32.exe wucltux.dll regsvr32.exe muweb.dll regsvr32.exe wuwebv.dll And following added by me (@AstroSkipper): regsvr32.exe mssip32.dll 7. Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter: netsh winsock reset 8. If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter: proxycfg.exe -d If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter: netsh winhttp reset proxy 9. Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. net start bits net start wuauserv net start appidsvc net start cryptsvc 10. Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter: bitsadmin.exe /reset /allusers 11. Install the latest Windows Update Agent. 12. Restart the computer. Article ID: 971058 - Last Review: 12/08/2015 06:57:00 - Revision: 42.0 Applies to Microsoft Windows Update Here is a link of the original document: https://web.archive.org/web/20160307084624/https://support.microsoft.com/en-us/kb/971058 And here is the the latest Windows Update Agent: http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe. It's version 7.6.7600.256. Supposedly all these steps should be done by a Microsoft Fixit Tool. No guarantee! Not tested! Here is the link: https://www.mediafire.com/file/r98pvby076rub6j/Mats_Run.WindowsUpdate.exe/file Although I am not a friend of automatisms, I also offer a another tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to backup your system partition completely at first. This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk. The last XP compatible version is 10.5.3.7: https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file and a less recent version 10.5.3.4 with a help file included: https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file There are many steps in this article that I was going to suggest anyway. Only if previous steps don't help. So have a lot of fun! PS: This posting will no longer be maintained. It will stay here just for historical purpose. The new, maintained and up-to-date version can be found here:

Of course the Windows Update Agent with file version 6.3.21.0 has to be installed. This is the version I have. Install it with command option: WindowsUpdateAgent-7.6-x86 /WUforce. Then install Restore_WU_XP_2003 again. No reboot at this time. Then do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary but injecting wuaueng.dll in any case. Then reboot your computer. Try MU again. P.S. No more further editing. I swear!

I agree. You are on the right way.

@Dave-H I agree to @maile3241. Only the three mentioned sites may be listed in your Trusted Zone. Otherwise http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en will be blocked. "Trusted Zone to high with only these three urls related to MU: http://www.update.microsoft.com, https://www.update.microsoft.com and http://update.microsoft.com. Disable in IE settings "Check for server certificate revocation"." And once again your problem is most likely caused by a not properly working Windows Update Agent. I will post a more detailed procedure published by Microsoft later.

Of course you'll lose your update history. My suggestion was to make an image of your OS partition to revert back at any time you want. I can restore my whole system in less than a half hour (very old computer, very slow). Your Windows Update history is located in "DataStore.edb". So you can backup this file at first. In your Windows Update Log you can see clearly: 2022-01-27 12:28:48:824 1860 1560 Agent *********** Agent: Initializing Windows Update Agent *********** 2022-01-27 12:28:48:824 1860 1504 Report WARNING: Reporter failed to upload events with hr = 80240004. I guess there is a problem with your Windows Update Agent. I have added a link of "winUpdRestore!v28" right down at the bottom, a more recent version of "winUpdRestore!v23". I used it first. Then you have to reinstall Windows Update Agent. Resetting of SoftwareDistribution folder is not the same. I suggested you: After this procedure you have to reinstall "Restore_WU_XP_2003". Here you have to check if "install.cmd" did its job properly i.e. all commands in "install.cmd" have to be performed properly. Check the correct version of "wuaueng.dll" in both folder system32 and system32\dllcache. Check if all registry entries have been added. If not do it manually by creating a reg file for importing necessary entries from "install.cmd" and copying wuaueng.dll first in folder system32\dllcache and then in folder system32. And what about some posts before where So a lot to do! https://www.mediafire.com/file/xn2a1rlriapkhym/winUpdRestore%21v28.zip/file

Alright, here is the Windows Update Log from my flawlessly MU accessing system: https://www.mediafire.com/file/iflfdi6ncoceop8/Windows_Update_2022_-_AstroSkipper.7z/file @Dave-H Comparing my log file to yours you can see what entries you have to have access MU successfully: 2022-01-27 11:49:29:484 1128 b48 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-27 11:49:29:625 1128 b48 Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-27 11:49:29:625 1128 b48 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-27 11:49:29:484 1128 b48 Service ************* 2022-01-27 11:49:29:625 1128 b48 Service ** START ** Service: Service startup 2022-01-27 11:49:29:625 1128 b48 Service ********* 2022-01-27 11:49:30:812 1128 b48 Agent * WU client version 7.6.7600.256 2022-01-27 11:49:30:812 1128 b48 Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-27 11:49:30:843 1128 b48 Agent * Access type: No proxy 2022-01-27 11:49:30:875 1128 b48 Agent * Network state: Connected 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing Windows Update Agent *********** 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing global settings cache *********** 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS server: <NULL> 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS status server: <NULL> 2022-01-27 11:50:21:562 1128 b48 Agent * Target group: (Unassigned Computers) 2022-01-27 11:50:21:562 1128 b48 Agent * Windows Update access disabled: No 2022-01-27 11:50:21:562 1128 b48 DnldMgr Download manager restoring 0 downloads 2022-01-27 11:50:21:593 1128 b48 AU ########### AU: Initializing Automatic Updates ########### 2022-01-27 11:50:21:593 1128 b48 AU AU setting next sqm report timeout to 2022-01-27 10:50:21 2022-01-27 11:50:21:609 1128 b48 AU # AU disabled through User preference 2022-01-27 11:50:21:609 1128 b48 AU Initializing featured updates 2022-01-27 11:50:21:625 1128 b48 AU Found 0 cached featured updates 2022-01-27 11:50:21:625 1128 b48 AU AU finished delayed initialization 2022-01-27 11:50:22:890 1128 b48 Report *********** Report: Initializing static reporting data *********** 2022-01-27 11:50:22:890 1128 b48 Report * OS Version = 5.1.2600.3.0.65792 2022-01-27 11:50:23:078 1128 b48 Report * Computer Brand = MICRO-STAR INTERNATIONAL CO., LTD 2022-01-27 11:50:23:093 1128 b48 Report * Computer Model = AWRDACPI 2022-01-27 11:50:23:109 1128 b48 Report * Bios Revision = 6.00 PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Name = Award Modular BIOS v6.00PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Release Date = 2002-10-24T00:00:00 2022-01-27 11:50:23:109 1128 b48 Report * Locale ID = 1031 2022-01-27 12:50:23:968 1128 b48 AU AU received policy change subscription event 2022-01-27 12:50:33:703 1128 b48 AU AU received policy change subscription event There are no "warnings" related to wuident.cab as show in your log file: 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup FATAL: IsUpdateRequired failed with error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80072EFE 2022-01-27 12:29:26:261 1860 1504 Agent * WARNING: Skipping scan, self-update check returned 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent * WARNING: Exit code = 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent ********* 2022-01-27 12:29:26:339 1860 1504 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2022-01-27 12:29:26:339 1860 1504 Agent ************* 2022-01-27 12:29:26:339 1860 1504 Agent WARNING: WU client failed Searching for update with error 0x80072efe So my first quick conclusion is you have to reset your Windows Update client and install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead.

Sometimes a reboot is necessary especially after changing system settings and configurations. And delete the Internet Explorer cache. By the way have you ever tried reregistering following components in the command prompt? Here if not: regsvr32 Softpub.dll /s regsvr32 Wintrust.dll /s regsvr32 Initpki.dll /s regsvr32 Mssip32.dll /s Your system is a brainteaser but a hard nut has to be cracked!

@Dave-H You was too quick in replying! But I agree. Delete it!

You're absolutely right. My screenshot belongs to current user. When you compare yours to mine there is one thing strange and this is your Microsoft Root Cerificate Authority 2011. You have twice and I don't know why. If it were my system I would delete the one with "Friendly Name" <none>.

@Dave-H Once again I have reflected what additional steps I'd performed to solve MU related error codes. And the winner is: flushing the DNS cache which means clearing the DNS cache. Reasons for doing this: "It's important to flush a DNS cache for a few reasons. The first is the cache may contain outdated information. You might experience this as difficulty accessing websites or applications. If the domain name in the cache points to an old or incorrect IP address, the website won't return the correct information." quoted from https://www.google.de/url?sa=t&source=web&rct=j&url=https://www.dnsstuff.com/clear-flush-dns-server-cache-windows&ved=2ahUKEwjpz-K4utD1AhWO3KQKHdpBCWoQFnoECAUQBQ&usg=AOvVaw1UbhoAs53jSD5-BeNl42B4. Command in cmd console: ipconfig /flushdns Don't know if it can help in your case but I did it definitely.

@Dave-H This is bit disappointing. So @Mathwiz's guess has been disproved and my suggestion doesn't help too. At next I've made a screenshot of my Root Cerificate Authorities in my system beginning with "Microsoft". So you can compare if one or more are missing. There is less German so I think it won't be a problem to read. https://imgur.com/hX3nGr4

The only thing I can say in your case you have to check systematicly and seriously what is missing or going wrong. When I had all error codes someone can get and yours too I did all from scratch i.e. you have to reinstall the mentioned updates although they already exist in your system or you have to check deeply if "Restore_WU_XP_2003" has been installed actually properly and so on. It will cost more time but for me it was the only way. By the way I can't see where you come from. There is no flag in your profile but your screenshot tellls me from Asia so maybe it is country related too. And here is a link with information to your error code from Microsoft: https://web.archive.org/web/20130316104325/http://support.microsoft.com/kb/836941 And a bit older version of this article I attach below. There you can find your error code 0x80072F78 "ERROR_WINHTTP_INVALID_SERVER_RESPONSE". https://www.mediafire.com/file/gu3q9b8gtpxwblr/q836941.htm/file

@Jonuarl Reden Hi, the suggestion you've quoted is related to error code 0x800072F8F so different to yours. Have you already read the whole thread? I have made a little guide to get MU working. Look here:

I think it's not unimportant to have only one ProxHTTPSProxy CA certificate in your system. If regenerating a new one leads to getting two of them then something is going wrong. Maybe your system restores this second old one. So delete all ProxHTTPSProxy CA certificates, make a reboot at first and have a look if your system has restored the old one before regenerating a new one. And only if you want try my suggestion two posts above: "Now I have two suggestions for you. First delete both ProxHTTPSProxy CA certificates and generate a new one from 2017 to 2027 following the guess of @Mathwiz. Delete all certificates in your ProxHTTPSProxy certs folder and let ProxHTTPSProxy generate new certs for all MU related sites (www.microsoft.com, download.windowsupdate.com, fe2.update.microsoft.com, www.update.microsoft.com, update.microsoft.com and so on; you can use Wireshark or more simple NirSoft's HTTPNetworkSniffer for finding all connected sites) by using New Moon browser or Mypal. Then try to access MU using IE and look if it works. Check your settings in Internet Zone too (relevant for accessing http://fe2.update.microsoft.com). The idea is letting a new browser generate these MU relevant certificates. If that doesn't work for you you can go back to ProxHTTPSProxy CA certificate valid until 2025 which was the one originally provided. Of course you can do this all using HTTPSProxy at first too."

@Dave-H Ok, your screenshot was a bit misleading. The certificate to the right is in your ProxHTTPSProxy's certs folder and the one to the left is your system root certificate. Therefore you have two ProxHTTPSProxy CA certificates due to the fact that you haven't deleted the old one before installing regenerated certificate. Is that right? Now I have two suggestions for you. First delete both ProxHTTPSProxy CA certificates and generate a new one from 2017 to 2027 following the guess of @Mathwiz. Delete all certificates in your ProxHTTPSProxy certs folder and let ProxHTTPSProxy generate new certs for all MU related sites (www.microsoft.com, download.windowsupdate.com, fe2.update.microsoft.com, www.update.microsoft.com, update.microsoft.com and so on; you can use Wireshark or more simple NirSoft's HTTPNetworkSniffer for finding all connected sites) by using New Moon browser or Mypal. Then try to access MU using IE and look if it works. Check your settings in Internet Zone too (relevant for accessing http://fe2.update.microsoft.com). The idea is letting a new browser generate these MU relevant certificates. If that doesn't work for you you can go back to ProxHTTPSProxy CA certificate valid until 2025 which was the one originally provided. Of course you can do this all using HTTPSProxy at first too. Due to the fact that HTTPSProxy and ProxHTTPSProxy is working flawlessly for me and for other members it will work for you too. There is one thing or more you have missed and you have to find it. Don't give up!

The old trick to avoid long searches of MU was reinstalling latest cummulative IE update. Resetting of datastore.edb can help too. By the way my search lasts only seconds.

@Dave-H I am a little bit confused. In your list of Trusted Root Certification Authorities I can see two ProxHTTPSProxy CA certificates. But why is your new one issued to *.update.microsoft.com as well as to ProxHTTPSProxy CA? I do not have that. That's no good I think. The dates look as expected. But I assume you can't have both due to the fact that only one instance of ProxHTTPSProxy should use its certificate. Comparing to my ProxHTTPSProxy CA certificate I would delete the "right one" with "Issued to: *.update.microsoft.com". The ProxHTTPSProxy CA certificate belongs to ProxHTTPSProxy and not to MU website. Truth be told I would rather delete both (make a backup before incl. Certs folder) and let ProxHTTPSProxy create a new one (e.g. from 2020 to 2030 or 2018 to 2028). The idea is before generating a new certificate by ProxHTTPSProxy you have to delete its old one. One instance of ProxHTTPSProxy, one ProxHTTPSProxy CA certificate. For me it looks like a bit messed up. But maybe @Mathwiz could tell us more.