Jump to content

xpandvistafan

Member
  • Posts

    279
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by xpandvistafan

  1. It is really strange that it works on your system but not on mine though.
  2. Yes, I did. I already installed the TLS 1.2 update as you can see in my above screenshot. I also did add PosReady to the registry otherwise I would not be able to install the update. Can you send a video of it working though?
  3. Still does not work. Same 500 error. Perhaps you should send us a video with a tutorial since it works for you.
  4. It seems https://catalog.update.microsoft.com is working again on Windows XP with TLS 1.2 updates. It used to be that https://www.catalog.update.microsoft.com was the one that worked. It is working for everyone else too? It also seems that the activex control/plugin is also working again, but on www it did not. https://ssllabs.com/ssltest/analyze.html?d=update.microsoft.com This website seems to only support TLS 1.2, but also supports POSready cipher suites. But, in March, it was like this,
  5. Have you found the update that is missing? This is my ssltest results for IE 8 with TLS 1.2 support.
  6. I think maybe you have root certificates installed on your other pc that make it work. In your image, You have multiple certificates installed that I don't have, such as the fe2.update.microsoft.com certificate and the Microsoft Secure Update Server 2.1.
  7. Installed the new ProxHTTPSProxy certificate and so close now, but not yet. It tries to connect now to https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx But I still get a 500 error response, I am sure this can be fixed, maybe we need more root certificates or ProxHTTPSProxy is sending faulty data.
  8. It seems you have some extra root certificates on your desktop. Maybe it will work if I install them?
  9. Did you make any other modifications to your system? This is what mine says.
  10. Can you send a screenshot? For me it gives a 80072f8f error when searching, saying the date and time is incorrect.
  11. With ProxHTTPSProxy, it gets further, but gives this error when searching for updates.
  12. That tutorial is for Windows 7. I don't think Windows XP has that capability from the group policy editor.
  13. Are you using ProxHTTPSProxy? Windows XP does not support those ciphers and the user agent is IE 9.
  14. Can you send a screenshot? I assume that your system is PosReady fully upgraded. Apparently, he got it to work in December by luck, with max-h's SHA2 patch. I do not know about this patch though.
  15. Yes, it worked for me. I get 80072eff as you said. But mine is vanilla XP with only TLS 1.0.
  16. . How did you get it to work in Windows 10? It would either redirect you or say you need to update your browser.
  17. Yes, that was always an issue, even before the website went down. update.microsoft.com started requiring more secure ciphers and TLS 1.2 in January 2021. Before that, you would get the error 80244019 since the update.microsoft.com page gave a 404. Back then, nobody knew how to redirect update.microsoft.com to fe2.update.microsoft.com. Do you have a log file of when it worked in December 2021? Perhaps something has changed since then.
  18. Yes, I will try it on a real XP machine from 2003 soon. Perhaps you should inform a moderator @Dave-H about your finding. Even though updates through the page does not work at the moment, it is a big step forward, since nobody knew how to see the old website again.
  19. Sorry, my mistake. Yes, it did stop working around that time, I believe April 28, when Microsoft switched update.microsoft.com to an SHA-2 certificate. What SSL and TLS settings do you have?
  20. Well, I got that error to go away last May by installing all PosReady Updates as well as TLS 1.2. I think the Root Certificate Authority 2011 is SHA-1, and it expired last May. What is interesting though is you got it to work after that.
×
×
  • Create New...