AstroSkipper

There are a lot of clean installations using a CD including SP3 and IE8. If I had to install from scratch I would use a version which contains all updates until 2014 and therefore including IE8.

Of course,. I said to @Dave-H some posts above the more the better and he agreed by replying the more the merrier.

But does anyone still use IE6 in Windows XP seriously? IE8 is crap but IE6...No way!

Very strange! WSUS server + WUMT was the first method which worked without any problems from the first time I tried. Yes, it's the same.

My version of 11/12/2019 is probably the same that you have used from November 2019. Then it works offline with this version but using WSUS server + WUMT doesn't work in your system. Is that correct?

I assume it depends on the version of wsusscn2.cab file you have used for offline scanning. My version is of 11/12/2019 and works like a charme.

Yes, you have to use two DataStore.edb files, one for WSUS server and one for MU web site. One for all didn't work in my system either.

Thanks for commenting! And now I have a mathematical statement for you: @Windows7fan = @xpandvistafan I think after evaluation the boolean truth value has to be set to true. What do you think? PS: I hope today is my day!

I haven't tested Option 3 in my system (no need to do) but Option 1 works perfectly too such as Option 2. What's the problem with WSUS server + WUMT in your system?

I think the more the better. Now we have three working methods to access MU or WU. 1. WSUS server + WUMT method 2. Method using ProxHTTPSProxy or HTTPSProxy + patch made by @Windows7fan 3. Method using Windows Update website patch based on nginx for XP Service Pack 3 Absolutely great! And as @maile3241 already said the third method works with CPUs lacking SSE2 instruction set. By the way the first one too.

This thread is about Root Certificates and Revoked Certificates for Windows XP. You can update your Root Certificates automatically by using the Certificate Updater 1.6 or manually by using the Root Certificate and Revoked Certificate Updater of 02/24/2022 created by me in section Downloads It works perfectly and is intended to keep your system as recent as possible regarding your Root Certificates. Kind regards, AstroSkipper

Thank you for providing a download link of ProxHTTPSProxy REV3e! I have added your link to my article above in section Downloads so that the reader has a better overview.

@WULover This thread is a support thread about Microsoft Update (MU) or Windows Update (WU). So we have reached a point where everything regarding hardware extensions is unfortunately off-topic. If you have further questions relating to your hardware, you must open your own thread with a topic of your choice. Here we can only discuss problems accessing MU. I hope I could help you and if so, I would be pleased about any reactions. Kind regards

Of course, if you can change it, do it! It should be a SSE2 capable CPU But more RAM would be important too. But be aware, your mainboard meaning the onboard socket and the current BIOS have to support the new CPU! Does the WSUS method work in your system?

I think you mean archive instead of folder. muweb.cab and mucltui.cab are cab archives actually.

Ok, give it a headline so it can be better classified! I took it to help @WULover. Sorry!

Ok, you've already corrected it.

Without ProxHTTPSProxy only a few sites and a lot of errors. Even with ProxHTTPSProxy not much better. IE is outdated and, sad to say, crap. You have to use Firefox 45 SSE or New Moon SSE releases.

You need an OS which supports modern browsers to surf the WWW. Windows 2000 is outdated like Windows ME either. As I told you twice before the best choice for your computer is a lightweight Linux Distribution such as Q4OS (Trinity Desktop). This OS supports older hardware, 32 Bit processors and more recent browsers. Otherwise you have to stay at Windows XP having very slow speed, missing some features and accepting to get system freezes from time to time.

Your computer is too old. If 320 MB is the maximum size of RAM, then any upgrading does not make sense at all. Windows 2000 is no option too. Use your Windows XP installation and try the WSUS server method which uses WUMT to get access to MU. You can find it in this thread or here: https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/ No need then to run ProxHTTPSProxy at all!

Why do you want to install Python? You don't need that. Try the WSUS server method which uses WUMT to get access to MU. You can find it in this thread or here: https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/

You try to run ProxHTTPSProxy REV3d built by pyInstaller. Therefore the Python version used is decisive whether your CPU is supported or not. I assume the lacking of SSE2 is probably the cause of the problem. Try the WSUS server method instead! It is working fine too.

I do think so, unfortunately. But have you tried WSUS server method to update your installation? This method doesn't require ProxHTTPSProxy. Moreover I assume the proxy is probably incompatible to your hardware. And please provide the exact type of Intel Celeron. There are a lot of them. I need to know the full specification.

But maybe exactly that is the problem. A fresh install means a lot of functions and patches are missing. Or your cpu is the problem due to the lack of certain, necessary features. What CPU is working in your computer? Please provide the exact type! And you said you've expanded your RAM. Did you perform a memory test?

Insall .NET Framework from 1.0 to 4.0 and all Microsoft Visual C++ Redistributable versions from 2005 up to 2019. And Onepiece Update Package too. ProxHTTPSProxy is working in Windows XP without any problems basically. My system is fully updated POSReady updates included, and I never had a problem relating to ProxHTTPSProxy. I think in your system something is missing. But anyway, in your case the best choice is a lightweight Linux distribution due to existing hardware limitations. In my opinion, Windows XP is too demanding especially relating to RAM consumption.