AstroSkipper

I think this key is obsolete. Save this registry key by exporting and then delete it! Restart your system and have a look! That's what I would do. If problems occur (I don't think so), restore it by applying saved reg file.

As always: You're welcome! Of course!

Hi @maile3241, create a new shortcut and insert following command in field "Target" or for you "Ziel": "C:\Programme\Internet Explorer\iexplore.exe" "http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=de&g_sconsumersite=1" and in field "Execute in" or for you "Ausführen in": "C:\Programme\Internet Explorer". All entries with quotes. The English names of the fields can deviate. And I forgot to say in English versions of Windows Programme has to be substituted by Program Files.

Hi @VistaLover, you provided interesting facts about ProxHTTPSProxy REV3e. Maybe you missed my request addressed only to you: You know I was kind enough to let you know of the reason(s) the original binary broke and what measures I actually took to restore intended functionality of cacert Updater. You see questions should lead to answers. Perhaps you'd be kind enough to let me know what your point of view is to my request. As I pointed out it is rather a theoretical question than a practical one. Kind regards, AstroSkipper

hpqddsvc.dll is described as HP CUE DeviceDiscovery Service. Therefore it belongs to a HP device installed in Windows XP and is part of the program HP Digital Imaging. If the problem of hanging process and long delay persists, I would recommend a reinstallation of your HP software. Furthermore in the past I had similar problems with long delays of nearly two minutes and a disabled firewall while starting my system. A solution for that was in defragmenting pagefile and system partition.

Hi @Dave-H, What's a shame? BTW I've found out which OpenSSL version is used in HTTPSProxy. As guessed it's OpenSSL 1.1.0i, so no support of TLS 1.3 in HTTPSProxy.

And what about my suggestion? A hard reset or repair? There is nothing to loose!

That's right. The packages of HTTPSProxy and ProxHTTPSProxy are totally different. In HTTPSProxy there is one main executable, whereas in ProxHTTPSProxy a small executable is calling up the actual main executable in subfolder application. Last version of HTTPSProxy bases on pyopenSSL 18.0.0, a rather thin wrapper around (a subset of) the OpenSSL library, whereas ProxHTTPSProxy REV3e bases on pyopenSSL 19.1.0, a more recent one. Current version of pyopenSSL is 22.0.0. I couldn't find any information about HTTPSProxy's openSSL version, but I think it is a bit older than 1.1.1d, probably 1.1.0. Therefore only ProxHTTPSProxy REV3e has TLS 1.3 capabilities. I'm curious what @VistaLover has to say about it. Unfortunately HTTPSProxy's launcher can't be used in ProxHTTPSProxy as it is. The launcher.exe would have to be decompiled, modified and recompiled to get it fully working or a new launcher has to be created. But you know I do things my way which means that I have already created a systray menu for better control and more comfortable use of ProxHTTPSProxy, but the launcher of HTTPSPoxy is simply outstanding and a class of its own.

Beside a fresh installation there are two other options for you: 1. Checking Internet Explorer Options, Internet Zone settings. Here especially all entries relating to ActiveX. 2. A complete reset of Internet Explorer and reregistering of all components which can be done by a special script or by a Microsoft Fixit Tool. If wanted, I can upload. PS: BTW, be aware of typos! @mina7601 found a lot of mine in the past. Maybe a link in Trusted Zone has one too.

Hi @VistaLover, we know by now that openSSL 1.1.1d supports TLS 1.3. So what do you think? What would it take to activate the already present capabilities of openSSL 1.1.1d in @heinoganda's ProxHTTPSProxy REV3e relating to TLS 1.3 and its ciphers to get them working in Windows XP? First of all, it is rather a theoretical question than a practical one.

No, "missing my mouse" means that I always miss my computer mouse for copy and paste while writing on my tablet, like now. But sometimes my head is a bit messing too.

For inserting links I'll use my computer instead of my tablet next time. Especially at the end of a sentence! And by the way, missing my mouse all the time! Truth be told I prefer totally the "old school" way of life.

Thanks for your hint! It's a problem I have very often when writing posts on MSFN using my tablet. The line of a link grabs the dot at its end. But when pasting a link, we all know, at the end of a link there isn't a dot in any case! Anyway, MSFN in combination with my tablet is a "dot grabbing monster"! PS: I've corrected it, of course.

That's not the way. You have to compare by performing a binary comparison. Read my guide! Step 11.

And in which way did you check the correct version of wuaueng.dll?

@mina7601 If I understood correctly, you did all from scratch, just for testing purpose?

And that's exactly what I prefer to do in most cases: manually as much as possible to gain full control. Unfortunately it's not possible in all cases. One can say a bit "old school" but I take it rather than a compliment. AIO packages can be great but they are not my favourites.

In step 4 of my guide I wrote: Therefore @maile3241's tip should work. BTW I made a shortcut in my start menu targeting this url: http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1

No problem. Do it when you are able to! Furthermore I have updated my guide completely and now it should be in a final state. The biggest change is in adding new steps at the end of my guide, but I think you have to compare it to your last version completely. Kind regards, AstroSkipper

It's the same with me! But there are users who have to unblock wuauclt.exe, for example like @mina7601, otherwise MU won't work for whatever reason.

@cc333 Unfortunately I had to update my guide once again. Just as info for you! Kind regards, AstroSkipper

When I was assisting @Dave-H in restoring access to MU web site, I found a lot of users in different forums (actually it should be called fora) reporting that only unblocking of wuauclt.exe would help fixing several error codes relating to MU, but there were many users too without any success. Therefore sometimes it may help, sometimes not. I will test that next time on my old computer without MU patch. So my preliminary answer is rather no.

Most of all Windows XP users using the POSReady trick had already installed these 4 updates in the past like me, for example. So it can be verified only using a clean install without any POSReady updates.

As requested I added "credits to @maile3241" to step 4, 6 and 7. Applying PosReady.reg in step 5 is generally mandatory for installing POSReady updates and logical, just as updating of Root Certificates. Therefore no credits in these two steps. In fact, credits in step 5 should go to whoever discovered the POSReady trick and to no one else. Same in step 8. Or are you the developer of rootsupd.exe from Microsoft? Generally, credits will be added where something of another person has been done or created. Kind regards, AstroSkipper

You're welcome, indeed! In your case it was fun helping you. Unfortunately I can't say that in all cases. You really read my guide carefully. And therefore you did it! Anyway, I have already updated my guide due to the experiences while assisting you. You can have a look at step 16 if you want. Greetings, AstroSkipper