RainyShadow

Well, Python itself can't even be compiled out-of-the-box... In the past i wanted to make an updated single-exe build of ProxHTTPSProxy. Started by getting the source for Python, so i could make it a SSE-only XP version, but immediately got a f!@#-ton of errors. So, after wasting some time digging for clues, i just scrapped the whole thing.

Check your PMs. I'm not sure if we can share this openly, lol. If @Dave-H or another moderator gives permission, feel free to post the link here.

Well, both would work for me As long as it stays away from SSE2/3/4/etc. According to the naming used by Roy - a build compatible with SSE-only CPUs, like my AthlonXP. In the old MyPal repo these were not provided through the releases page. If i remember correctly, the one i have was buried somewhere in the issues.

There is this - https://www.verboon.info/2010/02/pending-filerename-operations/

No SSE build yet?

Check this out, lol https://www.techradar.com/uk/news/windows-11-is-apparently-less-popular-than-windows-xp

Did you check here for tips?

Huh, i kinda don't get the joke here. Maybe i should have said "letters" instead? Or "non ISO-8859-1 letters"? Did you try with paths containing ä, ö, ü or ß? Or you don't have a German keyboard layout installed there? It doesn't matter what you see, but what the programs "see". You didn't get squares in your C:\Prox HTTPS Proxy\ path, but it still failed before, right? - - - Anyways, apologies for interfering with your private party, will try to avoid it in the future.

Maybe you should test also with non-latin characters in path (if you didn't already)

Is it this tool? Page says it needs OS support for TRIM.

The POST screen shows 50MHz, and speed measurement in emulated environments is sketchy most of the time. So, what was the actual speed, huh?! P.S. Maybe i should dig out the 386 i have laying about and test that, lol...

Thumbnail Zoom Plus don't work properly anymore in last builds of both Serpent 52 and NM 27. When set to show a zoomed image by pressing a hotkey (like this), it doesn't work. The hotkey does nothing. When the setting is reversed (like this), it appears to work, but this is not my preferred mode of using it unless i browse some gallery. Any clue if this is caused by some intended change in the browsers, or it's a bug?

No clue. My connection is set as described in that thread i linked earlier. That same log contains an "Online = Yes" entry too though.

Able to download through your browser, or your AU is able to download them? Yes, the one i mentioned here a few times - https://msfn.org/board/topic/183295-web-browser-proxomitron-reborn-ptrongui-a-how-to-guide/ I tried again after cleaning all caches, the certs folder, logs, etc. BFilter still says 0 as size. There is this number 20002 in ProxHTTPSProxy, is it the file size? Have couple logs for your viewing pleasure WindowsUpdate.log ReportingEvents.log (from C:\Windows\SoftwareDistribution) There is an error recorded, but the shield appears regardless. No related errors in the event viewer.

Updated previous post. No browsers running at the time.

C:\WINDOWS\system32\CRYPT32.dll loaded by wuauclt.exe is v.5.131.2600.6459 here. I just set the AU service from disabled to manual, then a wuauclt /detectnow and after few seconds the shield popped. After i stopped the service (followed by killing the wuauclt process as it was stuck stopping), i tried with wuauclt /resetauthorization /detectnow and got the same result. P.S. i got this in the ProxHTTPSProxy log: [22:28] 027 [P] "HEAD https://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071928" 200 20002 [22:30] 027 ProxHTTPSProxyMII FrontProxy/v1.5 [WinError 10054] An existing connection was forcibly closed by the remote host [22:30] 028 [P] "HEAD https://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071930" 200 20002 [22:32] 028 ProxHTTPSProxyMII FrontProxy/v1.5 [WinError 10054] An existing connection was forcibly closed by the remote host [22:34] 029 [P] "HEAD https://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071933" 200 20002 [22:36] 029 ProxHTTPSProxyMII FrontProxy/v1.5 [WinError 10054] An existing connection was forcibly closed by the remote host and this in BFilter: http://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071928 http://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071930 http://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab?2204071933 all three with size 0, probably cached...

Did you try this?

This may be useful https://www.windows-help-central.com/windows-shutdown-script.html

@Dave-H Set the "Automatic updates" and "BITS" services to manual instead of automatic startup. They usually get started anyways, but hopefully this will give more time to your proxy to get running before the first check. In Event viewer logs what is (roughly) the time between the "service entered running state" event for AU and that error you get?

Is this Marionette thing disabled by default in your builds? Any possibility for a malicious site to exploit it and remote-control my browsers?

You don't have to lose your current profile. Just start the profile manager (use the -P command line option) and create a new one. You can switch back to your old profile after you are done testing.

You can also try some cheap USB sound card. Obviously, you will need external speakers/headphones for it. I wonder how it would sound if you connected the output of such USB audio directly to the microphone connector of the built-in audio...

Pfff, this is what i was trying to tell you. After reset the settings are NOT the same on my old XP and a new XP VM! Anyways, just forget about it. I neither need, nor want MU now...

So, found one difference: https://i.imgur.com/V83LmZ0.jpg

It is OFF already. Anyways, i'm not asking about this error. I'm saying, that my "High" security setting is (probably) not the same as yours. When we both do a reset, we get different settings. This is a very old install, it's likely that some tweak/etc. modified the defaults in the past. I may compare it to a fresh XP tomorrow, don't feel like it now