Jump to content

On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019


Mcinwwl

Recommended Posts


6 minutes ago, xpandvistafan said:

This is without extended kernel right? 

Yes. Unfortunately, ProxhttpsProxy v1.3 cannot be opened in W2k either. I have ProxhttpsPoxy running outside my vm. That's why it works. To open it directly in W2k we need an even older version of ProxhttpsProxy.

Link to comment
Share on other sites

Windows Update for Xp x64 edition and W2k3

I found a new opportunity. Cr to @whenever by Tuopf https://www.prxbx.com/forums/showthread.php?tid=2172. This version of ProxhttpsProxy creates a Sha1 certificate and is compatible with most Windows versions. With this version of ProxhttpsProxy, it is possible to update Windows Server 2003 (not tested) and Win Xp x64 edition. IE6 is sufficient.

download link: https://www.mediafire.com/file/ftq6dnsccuq54p4/ProxHTTPSProxyMII_1.3a.zip/file

WU-patch: http://www.mediafire.com/file/1ontv0vkh0ghfbi/Restore_WU_XP_2003.7z/file

I have already edited the Config.ini so that you can work directly with ProxhttpsProxy. When opening ProxhttpsProxy a new certificate is generated. This certificate must be stored in the local computer's trusted certificate store.

Make sure TLS 1.0 and Http 1.1 is enabled via proxy and the Windows Update patch is installed! It works without additional updates!

It is also suitable if the CPU does not support SSE2.

@AstroSkipper What do you say? Is it a good option?

4DlZmCp.png

Edited by maile3241
Link to comment
Share on other sites

17 minutes ago, maile3241 said:

Update:

I found a new opportunity. Probably the best solution. Cr to @whenever by Tuopf https://www.prxbx.com/forums/showthread.php?tid=2172. This version of ProxhttpsProxy creates a Sha1 certificate and is compatible with most Windows versions. With this version of ProxhttpsProxy, it is possible to update Windows Server 2003 (not tested) and Win Xp x64 edition. IE6 is sufficient.

download link: https://download.ru/files/d4uaSsgD

I have already edited the Config.ini so that you can work directly with ProxhttpsProxy. When opening ProxhttpsProxy a new certificate is generated. This certificate must be stored in the local computer's trusted certificate store.

Make sure TLS 1.0 and Http 1.1 is enabled via proxy and the Windows Update patch is installed! It works without additional updates!

@AstroSkipper What do you say? Is it a good option?

4DlZmCp.png

Wait, is that the same version I gave you? Since the file is signed using SHA-1, it might even work on XP RTM!

Link to comment
Share on other sites

36 minutes ago, xpandvistafan said:

Wait, is that the same version I gave you? Since the file is signed using SHA-1, it might even work on XP RTM!

Yes it is the same version. It may well work on Win Xp Rtm. Maybe I'll try it.

Link to comment
Share on other sites

38 minutes ago, maile3241 said:

Yes it is the same version. It may well work on Win Xp Rtm. Maybe I'll try it.

I had to run it from another VM. It is missing a function. I think the minimum for it to run natively is either SP1 or SP2. 

Link to comment
Share on other sites

1 hour ago, maile3241 said:

@AstroSkipper What do you say? Is it a good option?

Just to clarify. You are using ProxHTTPSProxyMII 1.3a to access  Microsoft Update in Windows XP 64 Bit and guess it could work in Windows Server 2003 too. In Windows 2000 it doesn't work, you have to let ProxHTTPSProxy run in your host system to connect to your Win 2000 VM. And you need to apply the same Windows Update patch which is used in Windows XP. Is that correct? Anyway, if it is working then it will be an option, of course. I do not use these OSs, therefore I can't say more about that. I thought @heinoganda's ProxHTTPSProxy would run in Windows XP 64 Bit. I'm not particularly interested in the other OSs. But sometimes the route is the goal. :)

Link to comment
Share on other sites

5 minutes ago, AstroSkipper said:

Just to clarify. You are using ProxHTTPSProxyMII 1.3a to access  Microsoft Update in Windows XP 64 Bit and guess it could work in Windows Server 2003 too. In Windows 2000 it doesn't work, you have to let ProxHTTPSProxy run in your host system to connect to your Win 2000 VM. And you need to apply the same Windows Update patch which is used in Windows XP. Is that correct? Anyway, if it is working then it will be an option, of course. I do not use these OSs, therefore I can't say more about that. I thought @heinoganda's ProxHTTPSProxy would run in Windows XP 64 Bit. I'm not particularly interested in the other OSs. But sometimes the route is the goal. :)

Yes that is correct. ProxhttpsProxy from @heinoganda works without any problems under Win Xp x64, unfortunately you cannot access the WU website because you cannot install the necessary PosReady updates. The version V1.3 is even more "flexible".

Link to comment
Share on other sites

2 hours ago, maile3241 said:

Update:

I found a new opportunity. Probably the best solution. Cr to @whenever by Tuopf https://www.prxbx.com/forums/showthread.php?tid=2172. This version of ProxhttpsProxy creates a Sha1 certificate and is compatible with most Windows versions. With this version of ProxhttpsProxy, it is possible to update Windows Server 2003 (not tested) and Win Xp x64 edition. IE6 is sufficient.

download link: https://download.ru/files/d4uaSsgD

I have already edited the Config.ini so that you can work directly with ProxhttpsProxy. When opening ProxhttpsProxy a new certificate is generated. This certificate must be stored in the local computer's trusted certificate store.

Make sure TLS 1.0 and Http 1.1 is enabled via proxy and the Windows Update patch is installed! It works without additional updates!

@AstroSkipper What do you say? Is it a good option?

4DlZmCp.png

I don't think IE6 is a good idea, even before the XP EOL, it was mandatory to install IE8 and it's latest monthly update if you didn't want to wait one hour for each scan.

Link to comment
Share on other sites

39 minutes ago, maile3241 said:

The version V1.3 is even more "flexible".

What does that mean? There is nothing "flexible". ProxHTTPSProxyMII 1.3a is an older version and does not have the modifications of @heinoganda's releases . I assume WU does not work with modern ciphers in IE, especially IE6, of a Win XP 64 Bit system and TLS 1.2 is not supported. Therefore TLS 1.0 is probably sufficient. What do you know about the ciphers of ProxHTTPSProxyMII 1.3a?

Link to comment
Share on other sites

11 minutes ago, AstroSkipper said:

What does that mean? There is nothing "flexible". ProxHTTPSProxyMII 1.3a is an older version and does not have the modifications of @heinoganda's releases . I assume WU does not work with modern ciphers in IE, especially IE6, of a Win XP 64 Bit system and TLS 1.2 is not supported. Therefore TLS 1.0 is probably sufficient. What do you know about the ciphers of ProxHTTPSProxyMII 1.3a?

This means that no additional updates are required to call up and search for updates. When I tried the version from @heinoganda, I got the error 0x80072F78 (with IE8) when checking for updates, which was usually fixed with the 4 PosReady updates. With IE6 I could not open the page at all. The ciphers look like this:

etSZojI.png

Edited by maile3241
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...