I can DM it to you if you want, so please let me know if you are interested in that. It has not been released because it is unfinished, with x64 compatibility not yet working. However, it is a major upgrade from 1.2.2.
i know the issue and it seems to be that the version of proxhttpsproxy included within restore_wu_xp from windows7fan has issues with ie6, installing ie8 and the other updates fixes this. the proxhttpsproxy tls 1.3 popmenu from msfn does not have this issue but i recall it has an issue with genuine advantage aka legitcheckcontrol.dll freezing IE 6 but can be fixed by using ie8. for the 0x80072F78 issue: you'll need to install ie8 then you'll need to apply posready.reg and then install KB4493435, KB4019276, and KB4467770. you can delete the posready key after the updates are installed if you dont want posready updates but do that before you restart otherwise you may not be able to delete the key easily. you'll then have to apply tls 1.2.reg as its very crucial for this to work otherwise windows update with all versions of proxhttpsproxy would give you the same 0x80072f78 error including proxhttpsproxy v1.3a until you finally uninstall kb4019276. you'll then need to restart after applying tls 1.2.reg for it to properly take effect. if you are not in need of the proxy and you only want to get windows update working then i suggest you use wu_nginx (ie6 works just fine with wu_nginx), you'll get less issues with it compared to proxhttpsproxy and you wouldnt have to install any updates.
@ward201185 We are testing for NT 5.2 not NT 5.1 none of those updates are available for Server 2003 / XP x64, only IE8 the point of using proxhttpsproxy or other HTTPS projects should be to compensate for the lack of modern TLS support (v1.2 or strong ciphers) i think NT 5.2 don't require WGA update, so IE6 + ProxHTTPSProxy 1.3 should be enough for WU
oh, i didnt know that. thought you had issues with it in general. i also forgot that windows server 2003 sp2 x86/x64 and xp sp1/sp2 x64 doesnt have sha256 support by default so its either if you can install KB2868626 or KB3072630 update for sha256 then you can use proxhttpsproxy tls 1.3 or the version bundled with popmenu from msfn without issue as long as you dont get the wga update otherwise IE might freeze again. i also noticed that for windows xp sp1 x64 that KB2868626 claims it requires sp2 but i was able to get it working for sha256 without the need for sp2 by simply replacing the four files (both crypt32.dll and w03a3409.dll to system32 and from the files inside the wow folder to syswow64 and renaming wcrypt32.dll from wow folder to crypt32.dll before replacing) from the update. you can also install sp2 instead of doing this.
Hello, I wanted to ask: Should I setup this? Because Windows XP is unsupported and doesn't receive updates any more anyway, right?
I've found to have saved on my pc 2.5G of XP SP3 windows update from 2013 to 2017 dont' konw if anybody could be interested.
ProxHTTPSProxy : Interesting project, too bad there is way too much information on first page/post for someone who just want to bring back WU on an old system. Having a clear short guide would help people like me. I'm certainly missing something, but it doesn't work on a fresh install of WIndows XP SP3 French on a real physical computer, even with IE8 installed. Windowsupdaterestored website doesn't work either. At least Windows Update MiniTool worked, so I already have another drive with a fully updated OS (even POSReady updates) in my native language but I wanted to try this. EDIT : I'm trying Legacy Update, I should have had a look at this option, it seems wayyyy easier/user friendly.
Yes it is even easier to use than the original windows update in the last years it was still up and running. ProxHTTPSProxy is easy providing you use it with WUMT. Windowsupdaterestored, was aimed to older windows not XP, recently they became more ambitious, aiming to NT5.x, but it's still not mature as Legacy Update
just as a note, windows update restored is more intended for pre-windows 2000 sp3 but it can be used in windows versions up to windows xp sp2 x32 and maybe even windows xp sp1 x64 but i would recommend you use v6 for the versions of windows that support it. im not sure about windows xp sp3, you'll prob not get any updates for that platform as that is too new for windows update v4 in windows update restored and you should prob be using v6 for that instead. windows update restored is still a bit unfinished.
Welcome to MDL. If you cannot follow the simple "how to" provided by abbodi1406 you might need to work on your skills. No offence
Thanks. I used the legacy update for Windows XP Pro. It works well. Found so many .netframe work updates