AstroSkipper

Thanks for your complement! But to get manually rid of an addon (remove function doesn't work properly, indeed), the file extensions.json is the most important. The other files prefs.js, extension-preferences.json and extension-settings.json contain only preferences and settings, and do not harm i.e. can be left there. Cleaning these files isn't necessary, and for a lot of people it is simply too complicated, I think. In folder storage\default\moz-extension+++* the symbol * is a string of numbers and letters until ^userContextId=. For example ee6c8d43-8548-44cf-8b7a-f045e5a7edd9 is relating to adblockultimate@adblockultimate.net. Where do I get this information from? Simply open site about:config and search for this string! In Preference Name extensions.webextensions.uuids you'll find the answer. Cheers, AstroSkipper

Here is a tip how to get completely rid of an installed addon in Mypal 68: 1. You have to find out the extension ID of that addon. Click Help -> Troubleshooting Information. In section Extensions you can copy the related ID. 2. Under Tools -> Add-ons remove the problematic addon. 3. Close browser. 4. Go to your profile folder and open the file extensions.json in a good editor like Notepad++ which supports highlighting of brackets. 5. Search for the extension ID and delete its complete string from {"id": to "location":"app-profile"} curly brackets inclusive. Each extension begins and ends with these curly brackets. Between two different extensions may be only one comma. 6. Now delete in subfolder extensions related xpi file and its staged folder if existent. 7. Now start your browser, open Add-ons and you'll see the problematic addon has gone completely. Kind regards, AstroSkipper

In my computer is only a SSE2 cpu working. uBlock Origins fails to install as reported above. I quoted @feodor2's comment to issue #9. In case of uBlock presumeably only people using older computers like me are affected. Generally I think it's an early state of development and addon support is still immature at the moment.

It has already been reported that uBlock Origin doesn't work in Mypal 68 at the moment. I tried several versions and couldn't install any of them too. But I found an interesting alternative adblocker working in Mypal 68. It's AdBlocker Ultimate and works without any problems. I'm fine with that. Here is a link: https://addons.mozilla.org/de/firefox/addon/adblocker-ultimate/ . You can use the latest version 3.7.16. And @feodor2, my compliment for your great work! I am really impressed by the performance on heavy loading web sites in this early state of development. Kind regards, AstroSkipper

Hi @roytam1, good news for you! Using a clean profile, no problems in accesing web site https://sourceforge.net/projects/otter-browser/files/ Furthermore I tried again updating my installation to the latest version. Using my old profile and deleting all sourceforge related cookies, no more crashes. The problematic web site can be accessed without any problems. Therefore thanks for your quick reply and next time I'll try usimg a clean profile first. But such errors are a bit strange in any cases. Cheers, AstroSkipper

Very strange! Never had such problems. My environment is a real installation (no VM) of Windows XP Professional + all POSReady updates. It's a very old computer with a Pentium 4 CPU 32Bit in perfect condition and without any errors or problems. As mentioned before your previous versions never had any problems accessing this web site. For me it was the first time your browser crashed. And I could reproduce this crash. Anyway, I will try using a clean profile for testing purpose.

Hi @roytam1, I updated to your latest Pale Moon release "palemoon-28.10.5a1.win32-git-20220423-ba47fad4d-uxp-059e35a46-xpmod.7z". While trying to access web site https://sourceforge.net/projects/otter-browser/files/, the browser crashed immediately in modul xul.dll. I tried it more times, same result. Here is a copy of Event ID: Type : Error Date : 23.04.2022 Time : 16:52:06 Event : 1000 Source : Application Error Category : None User : N/A Computer : SKIPPERDESKTOP Description: Fehlgeschlagene Anwendung palemoon.exe, Version 4.8.4.8147, fehlgeschlagenes Modul xul.dll, Version 4.8.4.8147, Fehleradresse 0x0130f96c. And here is a copy of data: 0000: 41 70 70 6C 69 63 61 74 Applicat 0008: 69 6F 6E 20 46 61 69 6C ion Fail 0010: 75 72 65 20 20 70 61 6C ure pal 0018: 65 6D 6F 6F 6E 2E 65 78 emoon.ex 0020: 65 20 34 2E 38 2E 34 2E e 4.8.4. 0028: 38 31 34 37 20 69 6E 20 8147 in 0030: 78 75 6C 2E 64 6C 6C 20 xul.dll 0038: 34 2E 38 2E 34 2E 38 31 4.8.4.81 0040: 34 37 20 61 74 20 6F 66 47 at of 0048: 66 73 65 74 20 30 31 33 fset 013 0050: 30 66 39 36 63 0D 0A 0f96c.. The previous version "palemoon-28.10.5a1.win32-git-20220416-ba47fad4d-uxp-30e8509fd-xpmod.7z" does not have any problems accessing this web site. If you need more information, please let me know! Kind regards, AstroSkipper

Update notification: Due to false alarms generated by some virus scanners I had to completely recreate the cacert Updater Fixed. The previous version was just a fixed and modified variant of the original file. My Avast virus scanner was constantly analyzing the file cacert_Updater.exe and generating false alarms, although it was of course virus- and malware-free. Avast did not like this old version at all, probably because of non-matching CRC check sums. Here are the VirusTotal scan results of the old "cacert Updater Fixed" and the recreated "cacert Updater Fixed" file for comparison: Old version of cacert_Updater_Fixed: Recreated version of cacert_Updater_Fixed: Now you can see the success of recreating. Only one unimportant scanner reports a (false) warning. Therefore I provide a new download link of the recreated "cacert Updater Fixed" version. Here it is: https://www.mediafire.com/file/y98gtqf8ewr6zz4/cacert_Updater_Fixed_Recreated.7z/file Kind regards, AstroSkipper

All options of the Automatic Updates (AU) applet are greyed out In Windows XP the configuration of Automatic Updates is done by an applet from Control Panel. In some cases, when you open this AU applet, all of the configuration options may be greyed out and inaccessible for the user. Very often this happens due to any of following reasons: Either you're not logged on as Administrator, or Automatic Updates Policy is enabled which can be caused for example by using WSUS + WUMT method or by individual changes to AU time intervall settings. To recover access to these options you have to delete a few keys and to change some settings in your registry. One of them has been set by using WSUS + WUMT method: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate But there are a few more keys and settings in your registry causing this behavior. I recommend to backup the registry first for safety reasons. If you are not familiar with registry keys, or you do not dare to delete or to change them, you can apply the following reg file which deletes all responsible keys and changes settings automatically. Here is the download link of FixAUOptionsGreyedOut reg file: https://www.mediafire.com/file/uqt1r3d2mz5r30x/FixAUOptionsGreyedOut.7z/file If you want to know which keys and settings are affected, have a look inside the reg file! Kind regards, AstroSkipper

Microsoft Knowledge Base (MKB) and their KB articles For getting information and solving problems in Windows XP, Microsoft Knowledge Base had been an important source for a long time. But unfortunately most KB articles relating to Windows XP were deleted by Microsoft on their servers some years ago. Now we need other sources to get these KB articles. One method is to use a Wayback Machine like archive.org. Here is the link: https://web.archive.org/ Insert the original link of a KB article and in a lot of cases it was already archived in the past. But there are other sources too. Here is the best alternative: https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive And this is an offline database with more than 200000 KB articles: https://archive.org/details/MicrosoftKnowledgeBaseArchive200000Articles Good luck in searching KB articles, AstroSkipper

I totally forgot to mention the main reason why you can't easily put ProxHTTPSProxy in first place. There are three executables relating to heinoganda's proxy, two located in program's root directory and the main executable in a subfolder of it, all with different functIons. In contrast HTTPSProxy has got only one executable. Therefore it's easy to put HTTPSProxy.exe in first place but not in case of ProxHTTPSProxy.

Maybe these 2807 definitions files are the very last. I do not use MSE but perhaps they are working. Link: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1165552 And the (second) ZippyShare Webproxy link of MSE updater 1.9 is still alive: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1122545 But I think the updater does not work anymore. Try it! AstroSkipper

Forget about MSE! AFAIK last definition files are from 2019! Furthermore it has never been a good antivirus and is a RAM waster. Use Avast, Eset , Panda or Malwarebytes instead. In my system I installed Avast years ago and it's working fine until now.

It's just one click more. So, no thing I think! And then you have full control. BTW item labels are editable too. This menu is very stable. As far as I can remember TrayIt! hadn't been such a stable one. And hide and unhide are two functions you can't put in first place with tools like TrayIt!. In that case you need a self-programmed and compiled launcher created by using a higher programming language. I do things in a simple and practical way regarding to my skills.

Thanks! I labelled it due to their messages they have in output. But it can be changed easily. I have to think about it. Anyway, good suggestion! No, the systray icon is not configurable. As I mentioned in my posts before, ProxHTTPSPoxy's systray menu is a synthesis of self-programmed executables and an already existent one. The provided functions corresponding to their labels are generally self-programmed executables and in a very few cases inserted commands. The base structure of the menu is already predetermined. The advantage of this menu is its modular character. Deleting, adding or modifying is no problem and can be done by user either if he is a bit experienced. Toggling ProxHTTPSPoxy's console is controlled by clicking on correspondent menu item. So one left click opens menu, next click executes desired function. Simple and easy. All icons in menu can even be changed by user too.

Just to keep you informed, a short update of progress in development of my ProxHTTPSPoxy's systray menu. At first I provide a new screenshot documenting the current status of development: As you can see, three new items poroviding system proxy related functions have been added: "Check system proxy status", "Set ProxHTTPSProxy to mode System-wide" and "Set System to mode No proxy". I think now it is complete. All necessary functions have been added. Here is the complete list of features implemented in ProxHTTPSPoxy's systray menu: 1. Start ProxHTTPSPoxy 2. Stop ProxHTTPSPoxy 3. Hide ProxHTTPSPoxy 4. Show ProxHTTPSPoxy 5. Check if ProxHTTPSPoxy is running (in RAM) 6. cacert.pem Update 7. Root Certificates Update 8. Open IE Proxy settings 9. Close IE Proxy settings 10. Check system proxy status 11. Set ProxHTTPSProxy to mode System-wide 12. Set System to mode No proxy 13. Edit config.ini 14. Read documentation The test phase is slowly coming to an end. Any further suggestions, opinions or reactions are welcome, of course! So long, AstroSkipper

You're absolutely right. My fault. I've already corrected that. Of course I didn't mean AU service but simply AU. Sorry for misleading!

You shouldn't disable Automatic Updates service, you simply have to disable Automatic Updates in your control panel. @Dave-H Automatic Updates service should always be started and has to be set to auto. My system event log never showed this error and it doesn't show up now either. I just checked that.

You shouldn't disable Automatic Updates service, you simply have to turn off Automatic Updates via control panel.

Hi @Dave-H, I don't know whether you've already tried my fix or not, but just to clarify it, my recommended fix is meant to solve the disappearance of AU notification shield in systray. In my system the fix did its job perfectly. AU notification shield didn't disappear anymore. Additionally I had the hope it would solve the error message with Event ID 16 too. But that does not seem to be the case. It had disappeared in my log, but after two days it came back as in yours. After a bit deeper examination the reason for this error message is totally clear. Case 1: System is set to "No proxy". AU tries to download a file called wuident.cab from link https://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab. But without ProxHTTPSProxy or HTTPSProxy, no chance. This leads to the error 0x80072efe and, after two days of trying, to Event ID 16. Case 2: System is set to use ProxHTTPSProxy or HTTPSProxy "system-wide". Now AU is able to download file wuident.cab, but due to its invalid signature AU can't verify this file which leads to the error 0x80096010 and, after two days of trying, to another Event ID. BTW It would be the wrong version anyway. Unfortunately the address of a matching version is http://download.windowsupdate.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab or http://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab We, you and me, are using the method of patch in combination with one of our proxies. The patch in combination with all additional steps restores successfully access to MU web site using IE8. But the creator of this patch didn't take account of AU's malfunction. Case 3: Same proxy settings as in case 2. Due to download of wrong file version I modified the patch i.e. I changed some registry keys the patch had created. After these changes, AU could download and verify wuident.cab successfully, but wasn't able to download the next file, called wsus3setup.cab. Microsoft had deleted the file on the server which AU wanted to download from, therefore it leads to error 0x80190194. Conclusion: Either the patch will be modified to restore AU's functionality in online searching, or AU will only be able to find updates offline after a successful and cached search of MU. Provided that we use patch plus proxy method, AU notification pop-up shield can only remind us to download and install the updates MU has found in its search before. If you want to get rid of these errors in your system event log in any case, you have to turn off Automatic Updates in AU applet located in control panel. And one thing we know for a long time: What shall AU still find today? In a fully updated system, simply nothing. In other systems where updates are still missing, AU's notification pop-up shield can be taken as a reminder. And installation of updates by using AU is working fine as usual. Kind regards, AstroSkipper PS: In logical consequence, I turned off AU (via applet in control panel) in my fully updated system, as I used to do it before. I don't need AU trying to download a wrong file in background without any success. So bye, bye AU!

Windows Event Logs and their Event IDs Due to the circumstance that eventid.net doesn't exist anymore (shutdown years ago) an alternative source or database is necessary to search for Windows Event IDs in case of system errors and warnings. Best alternative database: https://kb.eventtracker.com/. Others: https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/, https://www.myeventlog.com/, http://www.chicagotech.net/wineventid.htm.

Hi @Dave-H, I'll publish a fix relating to AU and its notification pop-up shield in my new thread tonight. After applying my fix and instructions, these warnings shouldn't appear in your Windows System Log anymore. But one thing has to be mentioned: due to patched wuaueng.dll AU does not seem to be able to connect online with the Microsoft servers anymore. Only in offline mode AU detects updates, which seem to have been found in the last update search via MU website and cached. In my Windows System Log this error 16 doesn't appear anymore. PS: Ready! Here is the link: If you have any problems while applying my fix, please post it in my new thread! https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/ Kind regards, AstroSkipper

Additional resources: 1. Windows Update Error Codes Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217891 2. Windows Event Logs and their Event IDs Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216671 3. Microsoft Knowledge Base (MKB) and their KB articles Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217085 4. My essential tools for solving problems in Windows XP 4.1. My essential tools for solving problems in Windows XP — Part 1 — WU/MU tools Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1220689 4.2. My essential tools for solving problems in Windows XP — Part 2 — File extractors and packers Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1221226 4.3. My essential tools for solving problems in Windows XP — Part 3 — Text, hex, resource, and registry editors Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1226712

Restoring of the AU notification popup shield in Windows XP by @AstroSkipper Last week I was engaged in troubleshooting regarding AU in Windows XP. In my system AU notification popup shield always worked in the past. In February I disabled AU and it disappeared as usual. But last week, after I had enabled AU again, it didn't appear in systray although an important update was found by MU. I could restore it exactly for one Windows session. After restart it didn't work anymore. I had to find out what was going wrong in my system. And I found presumably the cause of this problem, a not properly working Windows system service called BITS. Many Windows users have a lot of problems due to a malfunction of this service. It should be started by system if necessary. But this doesn't happen in all cases. As I already recommended in my "Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP", item 2 of General solutions's list, step 3 system service BITS has to be started for a working WU/MU/AU. But very often Windows doesn't do that. Therefore I created a fix to restore AU functionality and missing notification shield. Here is the link: https://www.mediafire.com/file/6cvbrxg17oth5pz/FixAUWinXP.7z/file. Credits to @AstroSkipper. This fix is no virus and doesn't contain any malware. I know that because I am the creator. If you have problems with your security scanner, add this fix to AV's exclusion list. Scanned by Avast with no results. My fix performs a couple of tasks to eliminate typical problems preventing a popup of notification shield: restoring proper functionality of system services BITS, wuauserv and Cryptsvc, setting system to "No proxy", copying a system file to AU selfupdate, setting AU to "Notify me but don't automatically download or install them", triggering AU to detect updates, improving communication between client and server. Finally it restarts system. Here is a screenshot showing the restored notification shield and a window of an important update offered by AU in my Windows XP system: Fix was tested and is working in my system. Additionally AU can be triggered to show notification shield if it hasn't popped up yet: 1. Check if system service BITS is running. If not, start it. 2. Search for updates using MU website in IE and ProxHTTPSProxy. When searching has been finished, close IE. 3. Uninstall update KB4486463 (2019-02 Security Update for WES09 and POSReady 2009 for x86-based Systems (KB4486463)). 4. Restart computer. 5. After restart check once again if system service BITS is running. If not, start it. 6. AU notification shield should pop up. If not, trigger AU by executing two commands: wuauclt /resetauthorization /detectnow and then wuauclt /reportnow. 7. Now AU notification shield should pop up finally and showing missing update KB4486463. 8. Install offered update KB4486463 via AU. If update KB4486463 doesn't exist in your system or you don't use POSReady trick, choose another unimportant update which was recently installed.

Restoring WU/MU by using the nginx method I didn't test this method but it is said to be working and didn't apparently need ProxHTTPSProxy, This method requires only Internet Explorer 8 and update of Windows Update client. Here is the original link: https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-11#post-1724717. Credits to @owouwu at MDL.