AstroSkipper

I do not use Windows 2000 but afaik MU can be restored there too. Go some pages back and read the conversation between @maile3241 and @WULover.

What shall I say? You're welcome! Of course! BTW I assume the button "Check for Updates" worked for me in the past because automatic ActiveX download was present at that time. What do you think? I did not have such problems which have been reported here.

Hi @maile3241! You know my installation of XP is a very old one. So in the past there was no need to install XP freshly or to reinstall and therefore no chance for me to confirm your solution relating to automatic ActiveX download. But that's what I usually do before posting. Anyway I have updated my guide and linked your solution with reference to you. As we have seen some posts above it works and that's what matters.

Thanks a lot for replying! Therefore the winner is @xpandvistafan ! Ok, just a joke. I assume it is caused definitely by VM (Microsoft!). I have seen these connections in @mina7601's screenshots some posts above too. She lets XP running in a VM either.

No, thanks a lot. I'm just thinking about your connections coloured green in ProxHTTPSProxy's log window. I assume it is caused by running XP in a VM but I need a confirmation of someone using VMs too. And the winner is @maile3241

@maile3241 Once more. I wonder why in @sunsetsansyy's log window green connections exist to urls outlook.live.com and login.live.com. Is that due to the fact that Windows XP is running in a VM? I do not have these connections, I have a real installation of XP. You are running VMs too. So why these connections?

Congrats! You did it.

Is that due to the fact that Windows XP is running in a VM? I do not have these connections, I have a real installation of XP.

Check your settings relating to ActiveX in IE Options, tab Security, Internet Zone. Verify whether ActiveX is enabled or set it to low..

And are you now able to access MU successfully?

There are different ways to do that: Disable SFC by patching a system file. Or stop the service wuauserv and try to replace file. Finally you can try replacing from outside of your installation.

Now you've got error code 0x80244004 which means you "failed connecting to server". Please upload your WindowsUpdate.log now!

POSReady updates have to be installed logically after applying POSReady.reg in any case.

Well done! Exact description what you did. No need to apologize. I wonder why in your log window green connections exist to urls outlook.live.com and login.live.com.

If you did that on on 3 different installs with the same error every time, then you either missed three times a step or your systems are misconfigured generally. More information about your "3 different installs", please!

And importing the proxy settings of IE by proxycfg -u wasn't necessary for me too. When I did all steps I had listed in my guide, it works immediately.

When I restored access to MU, I could click this button without any problems. Very strange by the way!

@mina7601 Hi. If you still stuck on Microsoft Update error code 0x80072F78 or you are not able to click the button "Check for Updates", then there are a few things to check additionally. Here a short list: 1. Go to Internet Explorer Options, Advanced. Check if TLS 1.2 is enabled. Disable in this tab "Check for server certificate revocation". Now configure in tab Security Internet Zone to standard, 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 (Do it by copy and paste to avoid misspelling). 2. Go to Windows Services. Three system services are absolutely important for MU: bits, wuauserv and cryptsvc. These services should have been started and set to automatic. 3. If the button "Check for updates" doesn't work on MU, close Internet Explorer, open MU from Start Menu again and in most cases it will load successfully. This is step 14 of my guide. Check step 15 too if you have a fresh installation. (I've numbered all the steps for better reference). 4. Please upload a screenshot of ProxHTTPSProxy's log window. Your uploaded screenshot shows no connection to MU. At first the log window has to be empty. Then take a screenshot after calling up MU via http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1. All other browsers or connections to internet should to be closed. 5. Now try to go on and make a second screenshot. Here are two screenshots of ProxHTTPSProxy 1.5 REV3e taken from my Windows XP system while accessing MU, just for the purpose of comparing: First screenshot after calling up MU before searching updates: First screenshot after calling up MU after searching updates: Kind regards, AstroSkipper PS: I have updated the content of my "Complete guide for restoring Microsoft Update in IE". So if you still have problems, read the whole guide again and perform all steps once more by keeping the order of them!

@mina7601 Now I am online again. Are you still there? Any success? Ok, maybe too late today. We will see tomorrow. So long.

Unfortunately I have to go offline for 30 minutes. If it is not too late for you, I will come back. Anyway, the best idea solving your error code is to do all the steps in my guide once more by verifying each step. Sometimes one has to do these steps more times to be successful.

And by the way did you restart your system after patching? If not, I would do that first and in next step a check of correct patched "wuaueng.dll" in folder system32.

Total Commander or other file manager does these kind of comparison too. They compare the checksum of two files.

You have to compare the file "wuaueng.dll" in folder system32 with the patched one from archive Restore_WU_XP.7z. The version number of unpatched and patched file are the same. So it can't be used for comparing. Therefore try a binary comparison! You have to be sure that the patched version of archive Restore_WU_XP.7z has been copied definitely to these folders. Or do it manually!

Check if the correct patched version of "wuaueng.dll" exists in both folder system32 and system32\dllcache. In a lot of cases SFC (System File Protection) replaces the patched version by an original one. And what about config.ini of ProxyHTTPSProxyMII? Did you use my provided file?

Go to system panel, Automatic Updates and switch to "Automatic". Then try again and as an alternative this url: http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1