Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/11/2022 in all areas

  1. Final fix of error code 0x80072f8f while accessing WU or MU web site @Dave-H, @RainyShadow, @maile3241 and all other interested people, I have definitely solved the problem getting error code 0x80072f8f. I've done a second ProxHTTPSProxy installation just due to testing purpose. I let ProxHTTPSProxy generate a new CA.crt valid until 2032 by deleting old CA.cert file in ProxHTTPSProxy's program folder and opening ProxHTTPSProxy.exe afterwards. Then I installed this root certificate. But it didn't work either. I got error code 0x80072f8f too. I analyzed what had happened and found out it was installed in Trusted Root Certification Authority but for current user only. And that's the cause of the problem. It has to be installed in Trusted Root Certification Authority of local computer anyway. How is it done? Open console by typing mmc, add a snap-in for certificates, then choose for local computer and import your recently generated ProxHTTPSProxy CA certificate to Trusted Root Certification Authority. Finished. First a screenshot of MU using ProxHTTPSProxy along with recently generated ProxHTTPSProxy CA certificate valid until 2032: And here is a screenshot of my Trusted Root Certification Authority - local computer: Hope this will be the final solution to get rid of error code 0x80072f8f forever! PS: More detailed information relating to ProxHTTPSProxy and HTTPSProxy you can find in this article: Kind regards, AstroSkipper
    3 points
  2. The XP ACPI driver has been patched already and is working on AMD Ryzen desktop and Ryzen Threadripper. To get it to work for Windows 2000 I'll first need to resolve some missing imports in ntoskrnl InterlockedPopEntrySList InterlockedPushEntrySList ExfInterlockedCompareExchange64 HeadlessDispatch _aulldvrm Wish me luck.
    2 points
  3. I see you're using ProxHTTPSProxyMII too, as I was originally. I'm now using HTTPSProxy, but the result is the same. This seems to prove to me that it doesn't matter which of those programs you use, the error can still happen. Assuming that all other settings and configurations are correct, I think the proxy server is very likely the cause of the certificate error, but we need to diagnose why it works for some people and not others, with apparently the same setup. For anyone who hasn't already noticed, the PM system is fixed BTW!
    2 points
  4. Sorry, this sounds totally insane, classic menus are in the kernel. Most likely your hook has stopped working, as SAB IATHook's that too. Download test version http://startisback.com/StartAllBack_setup.exe and create HKCU\SOFTWARE\StartIsBack (DWORD)ImmersiveMenus = 0 (0 - classic, 1 - acrylic, 2 - shell)
    1 point
  5. Welcome to the selected members troubleshooting error code 0x80072F8F! Which proxy do you use? If you are using ProxHTTPSProxy you have two choices of config.ini files. The one file is mine: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file., the other is the config.ini of @maile3241: https://msfn.org/board/applications/core/interface/file/attachment.php?id=49135&key=c915b3197ea8b62e406422ccfec16ea4. Each of them is working in their system but they are different. Try them and report if one of them does the trick or not!
    1 point
  6. You need to add these three websites to Trusted Sites: http://www.update.microsoft.com https://www.update.microsoft.com and http://update.microsoft.com And set the level to high. If it is not available, press reset first.
    1 point
  7. That's a very good question. In my real Windows XP system the MU web site fix is working perfectly too.
    1 point
  8. Let's forget that for now. I'll explain again once we find the certificate error. I think we're all talking past each other now. I have the program from ThomasS. It runs directly in the Xp Vm.
    1 point
  9. When the issue is resolved I will revisit the other topic to avoid confusion.
    1 point
  10. Both proxies base upon same source. So both have to work as they do in my system. But you said ProxHTTPSProxy would work. So use it in your host system and configure your vm to access to it only for https as @RainyShadow suggested.
    1 point
  11. It was already entered because I'm using your config file. P.S. Sorry. I actually made a mistake. I meant that Xp is fully activated on my Vm.
    1 point
  12. Windows 10 is my host system. I've done your steps, unfortunately it doesn't work. For whatever reason.
    1 point
  13. @maile3241 Run ProxhttpsProxy on the host (real) system - Win10/7/whatever that is (your answers were kinda contradicting...). Set the VMs to use it for HTTPS proxy only - leave HTTP, FTP, SOCKS blank. Also, update cacert.pem in the ProxhttpsProxy folder.
    1 point
  14. The certificate error photo is of my vm and is enabled because it worked with ProxhttpsProxy, only with httpsproxy I get the error. The photo with the validation is from a real computer.
    1 point
  15. I did exactly the steps that were shown to me. I also replaced the configuration file. I can access all websites except check for updates. Certificates are also installed. Same problem in Win 7 too:
    1 point
  16. Both HTTPSProxy as well as ProxhttpsProxy are working flawlessly in my Windows XP Professional system. If HTTPSProxy doesn't work for you properly then you'll have done something wrong. At first read the included documents and check your installation! @Dave-H has both installed in his system and they are working as expected except successfully accessing to MU web site. I think there is a misconfiguration due to whatever. We haven't found the problem yet. My provided config files are used in my system without any problems.
    1 point
  17. @Dave-H Try ProxhttpsProxy and replace the configuration file and start Windows Update or Microsoft Update. Don't forget to install the certificates! http://i430vx.net/files/XP/ProxHTTPSProxyMII_REV3d_PY344.7z config.ini
    1 point
  18. Of course I told you before. Now I have to work. I will come back later.
    1 point
  19. That's in XP. btw W2k still gives an error that it is not a valid Win32 application.
    1 point
  20. Ok, you're right. We can't send him a PM. I'll send you a PM but not now. I'm writing this using my tablet but I need my PC to create a link. But one thing is clear: For personal use only! No sharing! No circulation! Is that ok for you?
    1 point
  21. We have to honor that @Thomas S. hadn't provided a working link of his software. So first send him a PM! If he doesn't answer contemporarily then maybe.
    1 point
  22. I know that he hasn't been here since 02/17/2021. But it doesn't mean he won't answer. First try to send him a PM! The problem is I don't know if I am allowed to provide a link of my copy due to copyright protection. Btw try using the extended kernel. HTTPSProxy won't work either in Windows 2000 without it.
    1 point
  23. @Thomas S. was last online on 02/07/2021. I don't think he will answer.
    1 point
  24. If you've read the post intently you'll have noticed to send a PM if you have trouble or any request.
    1 point
  25. That would be great. I installed W2k on a VM. Do you have instructions for this?
    1 point
  26. @maile3241 If you have another system, you can try running the proxy there.
    1 point
  27. ProxhttpsProxy cannot be opened even with the launcher. Proxomitron is running. btw. I get SSL passthru in Proxomitron.
    1 point
  28. 1 point
  29. 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
    1 point
  30. Too bad they say some of the included updates break non-SSE2 systems... You can try the python version of ProxHTTPSProxyMII. Also HTTPSProxy was mentioned many times about 10(ish) pages back... P.S. guys, you're adding pages here like crazy, lol
    1 point
  31. @AstroSkipper Is there a similar program for ProxhttpsProxy? Since it doesn't run on W2k.
    1 point
  32. I come back again for some updates. The patches provided by _Smoker and me are for different versions of IO.SYS. It is confusing, but essentially the same thing. The patch knocks out a far call instruction to a procedure that install handlers to INT 15H AH=87H/88H and AX=E801, also INT 2FH AX=4300H / 4310H and 4309H, also the source of some GDT entries. This will make HIMEMX.EXE to work. However, if some one has tried our way of patching, some side effects will be found. like wrong mem command output, system hangs in safe mode, running to massive non-sense output in loading some applications. Also, to start the wfwg in enhanced mode, some tricks like I mentioned must be used. To solve all these problem. I made some analysis and developped a small new driver program for the purpose of loading EMM386 and WFWG. I call it IO8EMMOK. it can be downloaded from GitHub https://github.com/pufengdu/IO8EMMOK IO8EMMOK.SYS is a wrapping driver that convert the built-in XMS driver to a generally normal XMS driver. I wrote the tech details in the comments of the source codes. Here is a short summary of the details of technology. In general MS-DOS 8.0 is a DOS always in HMA without any stub below 1MB. The XMS driver is also in HMA. Since XMS driver is in responsible of controling A20, it becomes a key behind the lock case. Therefore, every time an application abitarily disable A20 and try calling DOS or XMS driver, system reboots or hangs. Every time an application rely on the address wrapping mechanism tried to run, the system reboots or hangs. This is also why MS-DOS 8.0 seems so unstable. Its A20 must be kept ALWAYS ON. However, this is an old case for DOS services, but new to an XMS driver. Most programs, including Win3x, thought the XMS driver is some where below 1MB. Therefore, it should work even with A20 off. But, this is not the case on MS-DOS 8.0. My IO8EMMOK driver provide a very simple wrapping layer to the XMS driver, making it callable with A20 off. In this case, the driver tun on A20, forwad the call, then turn off A20 again. This creates the minimal side effects, but not zero. With this driver, no patch is needed to load EMM386.EXE. Just load the IO8EMMOK.SYS as the first driver in the CONFIG.SYS EMM386.EXE will be happly to load as normal, no HIMEMX.EXE nor HIMEM.SYS. I also adapted the W3XStart patch in this case as a hotfix patch, which only modify memory. It can also be downloaded from the same github repo. There is no need to decompress the IO.SYS. The compressed form IO.SYS with the one-byte real-mode patch can be used now. With the IO8EMMOK driver, and my W3XStart hot fix, it would be easy to start WFWG in enhanced mode. The last element of making this happen, is to use a serial mouse, not PS/2. And set mobo option of Gate A20 to "Normal" The WFWG default mouse driver is not going to work in this way. Update it using Microsoft Mouse Driver 9.01. It is easy to find online. I finally achieved the attached effects. WFWG is fully functioning on MS-DOS 8.0, without hanging, without tricks, without decompressing IO.SYS. If someone found bugs of the driver, fixes are welcome.
    1 point
  33. I will forever miss the Bill Gates' Microsoft and the personal computing decade from 1995-2005. Those were happier times for Windows users.
    1 point
  34. @maile3241 Once more, thanks for your great help! Glad it works for you too and I could help a bit. It wasn't easy to find the cause of my error codes (I had a lot of them) but my guess to edit config.ini of HTTPSProxy was correct. I have checked a lot of registry entries and files. Now I have tested Microsoft Update site several times and it works flawlessly. It found one update missing and I could install it from there. See my screenshot https://imgur.com/oAO72vT
    1 point
  35. I have to admit my first impressions of Windows 11 are a result of a customer recently buying a new computer and coming to me after having problems after upgrading to Windows 11... I have no test version of this OS because the only computer I have that can upgrade to Windows 11 is my customer work computer and I point blank refuse to upgrade this computer with another pile of crap from Windows until I have to.... Yes...it makes it hard for me to test Windows 11 which does worry me a bit... Anyway....customer came with Windows 11 and I have to say it is more illogical than ever!! I had a hard time finding things and many of the normal functions "right click" were not available in certain areas..... I just got frustrated with searching for stuff and she asked me to reset it to Windows 10.....YES...probably the only time I will ever be elated about Windows 10....lol Microsoft couldn't even fix the return to Windows 10 without messing up a lot of settings etc.... I fixed the problems and advise her not to upgrade for at least a year....pointed out that Windows 10 has support until 2025 and that was good enough for her..... After doing a search online - I find that more often than not people are returning to Windows 10 because they just couldn't get on with Windows 11.... bookie32
    1 point
×
×
  • Create New...