Jump to content

maile3241

Member
  • Posts

    545
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by maile3241

  1. I now have httpsproxy and am now getting the same error as @Dave-H. With ProxhttpsProxy it worked without any problems.
  2. @Thomas S. was last online on 02/07/2021. I don't think he will answer.
  3. That would be great. I installed W2k on a VM. Do you have instructions for this?
  4. ProxhttpsProxy cannot be opened even with the launcher. Proxomitron is running. btw. I get SSL passthru in Proxomitron.
  5. Do you have a link to the Python version? Of course, IE 6 can use https. It supports SSL 2, SSL 3 and Tls 1.0.
  6. I was able to open the first version of ProxhttpsProxy. Unfortunately, no https pages can be opened. The contribution to this: https://prxbx.com/forums/showthread.php?tid=1618
  7. @AstroSkipper Is there a similar program for ProxhttpsProxy? Since it doesn't run on W2k.
  8. I'll explain again. The website works on Windows Vista Rtm and SP1. In SP2 I get error 0x80070002. The same error also applies to Windows 7. Strangely, the page works fine on Windows 10.
  9. I've never used it on Windows 7. I think you misread. I was able to work with it on Vista. He also gets 0x80070002.
  10. The 0x80072efe error comes from Windows Update in Control Panel. Not from the site.
  11. I tried it. The file is replaced each time you visit the site. Strange that it works on Windows 10.
  12. @AstroSkipper It says here that this is the user string: https://social.technet.microsoft.com/Forums/lync/en-US/73cc6a2f-f447-4e73-8c9f-174914d6eb30/with-sp1-rc-17128-now-windows-update-problem-missing-wsus3setupinf?forum=itprovistasp&forum=itprovistasp
  13. Wsus3setup.cab contains these files. What I don't understand is that it works in Vista Rtm and Sp1. From Sp2 I get the same error. It also works fine in Windows 10.
  14. Here the program with hidden files. WebSetup folder on the left and SelfUpdate on the right.
  15. No, everything has already been checked. My guess is that the user agent string is wrong. The same problem also occurs in Win 10 when opening the page via Chrome with IEtab. It works fine in Internet Explorer.
×
×
  • Create New...