Leaderboard

RPO (repo.palemoon.org) is a server owned and paid-for by Moonchild himself; Gitea is just the version control software deployed on that private server to manage source development for UXP, Pale Moon and related projects; it's what is called a "private (self-hosted) Gitea instance" ; on the Anubis test page itself, one can read: ... so I believe MC is mainly concerned with excessive bandwidth consumption; please also note that he had already implemented geolocation-based ACLs (access-control-lists) to counter automated DDoS attacks and, as a consequence, in Hong Kong (where our own roytam1 lives ) RPO is blocked ...

something like this

I have a lot more run-ins with Cloudflare than I do Anubis. Both of them can get stuck in an infinite validation loop. Cloudflare can get insanely aggressive, it will quite happily lock your browser into an irretrievable Loop of Death (who would write code like that?). At least Anubis can easily be stopped. I think the thing I object to the most is that they focus on the way a browser looks rather than what it is actually doing. In civil society this is characterised as profiling rather than being intelligence led. All that will happen is that the bots will better disguise themselves and their behaviour will go unchecked. Ben.

The contents of the updroots.sst file have been changed; the contents of the other * .sst files are unchanged.

... This only means further/wider proliferation of such MITM anti-crawler "services", with the web becoming even more "unpleasant" as time moves on (with a greater impact, of course, on older browser engines, on old/weak H/W); what's the point of having 500 (or more) Mbps fiber internet speeds when every tab you open in your browser will need additional time to pass complex JS tests? FTR, I keep, for historical purposes, a "portable copy" of NM27 (not the last one published, though), which isn't able to pass the Anubis test (e.g., on RPO Gitea repos); and even Serpent 52 struggles passing that test, especially if I don't disable "security/privacy"-oriented solutions (extensions and/or userscripts); privacy also falls victim here, because you're given no other choice on such web-policing "services": either "open" your "privacy fences" or be denied access to the site you're after ... This is all depression-inducing ...

The thing that hath been, it is that which shall be. Been here before Dave, we covered this back in 2017. Simple fix with a Server 2003 version of USBPORT.SYS. daniel_k's solution appears to be the best of the various different packages that address the PAE limit.

The alternative forum is now available. It is located here: https://tripredacus.net/forum/index.php This forum is actively managed by myself and has public status sections for the three websites that I am providing temporary forums for. The fallback boards are not visible to the public and are not segregated, meaning if you can see a board, you can post in it if you want. The sections will always be open, even if the hosted site has an Up status such as MSFN currently does. This forum is not intended to, nor can it replace MSFN. It is also not meant to be a replacement for other unmanaged or unofficial meatup destinations such as any Discord channels, Steam or Facebook groups. It simple is a place to go in case there is a problem or you want to get info about whatever might be happening. This is not an indication that there is any longevity issue with MSFN. The forum rules are not MSFN's rules, with the exception that discussion about circumventing MSFN rules 1 are not allowed. UK/EU members make sure you read the end of the Registration Agreement. Whether you decide to register on it or not is up to you. This post is just to make you aware that it exists. You choose your own level of involvement. If you decide to register, you should edit your profile to put your MSFN name as it explains in the appropriate profile field. Doing so will cause a MSFN icon appear on your info card if you post in a thread.

How MSFN prohibition is relevant? Read the topic title again, please. 1 - MSFN board is not available in Russia without VPN! 2 - VPN is illegal in Russia. 3 - Checkmate. So - we shouldn't see any Russians here at all. But they are here, so - they break their own law and going towards criminal prosecution (with FSB at their doors, according to their own law cited by Saxon).

Tell us, will that "territory" include the recently occupied neighbours ? Legal explanations from a lawyer : The territory of Russian Federation was internationally recognised only in the borders of 1991. Since your Russian Federation illegally annexed territories from its neighbours, it has no recognised borders anymore.

Fix Russia's behaviour on the international arena.

Of course. Sleep well!

So here is the official instruction from Microsoft how to reset Windows Update. I've crossed out instructions that aren't referring to Windows XP or 2000. Furthermore I've added steps I found that they are missing. Make a backup if you want to perform this. In any case read carefully! Manually reset Windows Update components (KB971058) Important: Follow the steps in this section carefully! Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur! To reset the Windows Update components, follow these steps: 1. Open a command prompt. To do this, use one of the following methods, depending on your version of Windows: Windows 8.1 and Windows 8: From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click Command Prompt, and then select Run as Administrator. Windows XP and earlier versions: Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator. 2. Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. net stop bits net stop wuauserv net stop appidsvc net stop cryptsvc 3. Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter: Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" 4a. If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.). Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak Ren %systemroot%\system32\catroot2 catroot2.bak 4b. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) 5. At a command prompt, type the following command, and then press Enter: cd /d %windir%\system32 6. Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. regsvr32.exe atl.dll regsvr32.exe urlmon.dll regsvr32.exe mshtml.dll regsvr32.exe shdocvw.dll regsvr32.exe browseui.dll regsvr32.exe jscript.dll regsvr32.exe vbscript.dll regsvr32.exe scrrun.dll regsvr32.exe msxml.dll regsvr32.exe msxml3.dll regsvr32.exe msxml6.dll regsvr32.exe actxprxy.dll regsvr32.exe softpub.dll regsvr32.exe wintrust.dll regsvr32.exe dssenh.dll regsvr32.exe rsaenh.dll regsvr32.exe gpkcsp.dll regsvr32.exe sccbase.dll regsvr32.exe slbcsp.dll regsvr32.exe cryptdlg.dll regsvr32.exe oleaut32.dll regsvr32.exe ole32.dll regsvr32.exe shell32.dll regsvr32.exe initpki.dll regsvr32.exe wuapi.dll regsvr32.exe wuaueng.dll regsvr32.exe wuaueng1.dll regsvr32.exe wucltui.dll regsvr32.exe wups.dll regsvr32.exe wups2.dll regsvr32.exe wuweb.dll regsvr32.exe qmgr.dll regsvr32.exe qmgrprxy.dll regsvr32.exe wucltux.dll regsvr32.exe muweb.dll regsvr32.exe wuwebv.dll And following added by me (@AstroSkipper): regsvr32.exe mssip32.dll 7. Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter: netsh winsock reset 8. If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter: proxycfg.exe -d If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter: netsh winhttp reset proxy 9. Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command. net start bits net start wuauserv net start appidsvc net start cryptsvc 10. Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter: bitsadmin.exe /reset /allusers 11. Install the latest Windows Update Agent. 12. Restart the computer. Article ID: 971058 - Last Review: 12/08/2015 06:57:00 - Revision: 42.0 Applies to Microsoft Windows Update Here is a link of the original document: https://web.archive.org/web/20160307084624/https://support.microsoft.com/en-us/kb/971058 And here is the the latest Windows Update Agent: http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe. It's version 7.6.7600.256. Supposedly all these steps should be done by a Microsoft Fixit Tool. No guarantee! Not tested! Here is the link: https://www.mediafire.com/file/r98pvby076rub6j/Mats_Run.WindowsUpdate.exe/file Although I am not a friend of automatisms, I also offer a another tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to backup your system partition completely at first. This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk. The last XP compatible version is 10.5.3.7: https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file and a less recent version 10.5.3.4 with a help file included: https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file There are many steps in this article that I was going to suggest anyway. Only if previous steps don't help. So have a lot of fun! PS: This posting will no longer be maintained. It will stay here just for historical purpose. The new, maintained and up-to-date version can be found here:

Of course the Windows Update Agent with file version 6.3.21.0 has to be installed. This is the version I have. Install it with command option: WindowsUpdateAgent-7.6-x86 /WUforce. Then install Restore_WU_XP_2003 again. No reboot at this time. Then do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary but injecting wuaueng.dll in any case. Then reboot your computer. Try MU again. P.S. No more further editing. I swear!