All Activity

Update notification! As already reported, the Root Certificates have been updated and are now from 29-04-2026. Here again a screenshot: After a long delay, I have just updated my self-created, offline Root Certificate Updaters in the section 11.2.4. Downloads related to Root Certificate Updates (in the first post of this thread). Cheers, AstroSkipper

openssl-3.6.3-x64-dll.7z

It is proving somewhat difficult to find a configuration that satisfies everyone. I have added a shared XP build that includes ffplay in the previous post.

I understand, but if someone doesn't want to, they shouldn't download the file. There are also those who use ffplay and the 'shared' version

Again, autodidact is NOT to blame ; go back some pages in this thread and you'll read (some) users of FFmpeg (on WinXP and elsewhere) declaring they don't want FFplay at all, because they ONLY use dedicated GUI players for playback of media files ; and I don't recall off-hand why the XP shared builds were axed, too, but autodidact simply delivered what (XP) members here asked for ...

@autodidact There is a security update for OpenSSL (3.6.3). Would you be so kind to provide the 64-bit shared libraries for Windows again? 🙏

Okay, but that kind of misses my question. IF this only affects v149, then IT DOES *NOT* EFFECT Supermium. ie, "the sky isn't falling" edit: ie, the "stupidly aggressive" update schedule (that both Chrome and Firefox do!) **CAUSED** the "exploit" so *ONLY* people that "update every d@mn day" (exaggerating for effect) were even effected

It's a bit of a shame you didn't include the ffplay file and the “shared” version for Windows XP.

The only real issue that all browsers in single-process mode as, for example, New Moon 28, have – and which has always been the case with every version of Firefox – is their inability to free up RAM when tabs are unloaded or closed. The amount of memory that is actually released is pitiful compared to the amount that was originally used. It’s a problem that has remained unresolved since the very beginning, so to speak. And these days, developers no longer worry about wasting RAM, because most of them have plenty of it. But my Windows XP computer doesn't. What is particularly pleasing, however, is that GitHub has been running smoothly in New Moon 28 for some time now and, as far as I can tell, is actually running very well at the moment.

It means the exploit exists in the wilderness that google created with their crap, I mean chrome. V 149 (their latest) was patched.

Here's a quick status update on New Moon 28 (32-bit) (2026-06-04) - the current release - under Windows XP running on a single-core 32-bit P4 with 1.5 GB of RAM. I have installed 25 extensions in my profile, 23 of which are enabled, 17 UC.JS scripts, 1 UC.XUL script, 4 USER.JS scripts, and 4 CSS stylesheets. When I launch the browser, it uses 184 MB of RAM, and it takes only a few seconds to load. My browser console shows no errors when the browser starts. If error messages appear, they are caused by websites. The reason for this is that New Moon 28 runs smoothly out of the box – at least as far as the browser console is concerned, thanks to @roytam1 – and I wrote my UC.JS scripts on the premise of running completely error-free. And regarding extensions I either fixed faulty ones myself or, if unfixable, I removed them.

http://sweetlow.orgfree.com/download/esdi_506.zip Fixes: 1. [TBP2.1 - BigHDD] Fixed - data underrun in the initialization procedure of PM Only drives. This resulted in slowdown on booting (sometimes significantly) and caused other problems. 2. [98SE] ATA devices are no longer considered to be in a stopped state (SpinDown) after initialization. 3. [98SE] The CMOS type of a PM Only drive on non-primary ATA channels when added after the boot stage is now consistent with that during boot. 4. [98SE] Fixed the setting of the I/O request call method in the drive initialization procedure. This did not affect functionality in the vast majority of cases, but has been improved nonetheless. Update is recommended due to point 1.

god speed! hope you accomplish this "mission". thx much for trying and caring.. regards....

@Dietmar Yeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaaaaaa I fixed code bootvid - now support: auto detect memory address graphics card auto detect many popular resolutions // Walidator rozdzielczosci BOOLEAN IsValidRes(ULONG w, ULONG h) { if (w >= 800 && w <= 3840 && h >= 600 && h <= 2160) { if ((w == 800 && h == 600) || (w == 1024 && h == 768) || (w == 1152 && h == 864) || (w == 1280 && h == 720) || (w == 1280 && h == 800) || (w == 1280 && h == 1024) || (w == 1360 && h == 768) || (w == 1366 && h == 768) || (w == 1440 && h == 900) || (w == 1600 && h == 900) || (w == 1600 && h == 1200) || (w == 1680 && h == 1050) || (w == 1920 && h == 1080) || (w == 1920 && h == 1200) || (w == 2560 && h == 1080) || (w == 2560 && h == 1440) || (w == 3440 && h == 1440) || (w == 3840 && h == 2160)) { return TRUE; } } return FALSE; } BSOD is displayed always centered screen is not cleared before BSOD detected resolution is displayed in bottom right screen corner

When WildBill investigated the old version of the file "win32k.sys" from Windows XP, he noticed, that the following functions have the problem with the uninitialized variable: "_SetWindowWord", "xxxSetClassData" and "xxxSetWindowLong" When I investigated the new version (5.00.2195.7640) of the file "win32k.sys" from Windows 2000, I noticed, that the following functions have the problem with the uninitialized variable: "_SetWindowWord" and "xxxSetClassData" The function "xxxSetWindowLong" seems to have been fixed somewhen by Microsoft. Now that the update "OTS000004" was released, there was only the following function left to fix: "xxxSetClassData" To fix the remaining function I released another Windows 2000 update: "WINDOWS2000-OTSKB000005-V1-X86-INTL.exe There is more information available about this issue and this update in the article in the knowledge database: OTSKB.chm The patch updates the file "win32k.sys" from the version "5.00.2196.0005" to the version "5.00.2196.0006". Before installing OTSKB000005 it is necessary to have OTSKB000004 installed because every update is a patch that needs the previous version to work with. No update contains a full version of the file "win32k.sys" but only the patching instructions.

Believe me I really didn't want to suspend the lists for Windows 11, but because WUD is so old and I have PM'd Jcarle about this problem and haven't yet gotten a reply. Also managed to decompile the executable to see if I could update WUD myself, but the code is so old that it's difficult to try and update the code with today's internet standards like https and TLS which MS uses now. It's good that you were always downloading the latest lists, and I will try again to see if I can update WUD's code. If not then I might have to code a brand new program to download windows updates, but I can not promise anything as my programming skills is basic and will need to use AI if I do decide to make a new one.

OOOOHHHHHH nnOOOOOOOOO steve I depend on your list every month. how can I get the latest updates like todays, June 9th, 2026 in the future. thx ron PennsylvaniaRon \\\\|//// ~ÖÖ~ ----oOOo-(_)-oOOo----

It's good to hear you're doing well. Have you managed to sort out the GitHub issue?

Yes I am oke and new version will be soon already as usual.

What does "exists in the wild" *REALLY* mean? ie, does it really affect v144? Or does it just affect those that "thought" they were safe by always running the most recent?

You won't get 3D on NT 4.0 using Virtualization software cause developers haven't done that...if you need 3D,then use 86box or PCem...

Looks like there is a new issue to patch: "Google is aware that an exploit for CVE-2026-11645 exists in the wild,...".

Yes indeed! He's done the same edit that I did to the file and bundled a copy of pwrp_k32.dll in the zip file with it.

Not for 3D and Vmware / Virtualbox has some 2D drivers.

... It would appear that Shane is still monitoring this thread ; inside the Supermium-v144-r4_01 release notes, https://github.com/win32ss/supermium/releases/tag/v144-r4_01 this shows up: https://github.com/win32ss/supermium/releases/download/v144-r4_01/supermium_uao.zip Edit: Rather the fix was a consequence of the discussion in: https://github.com/win32ss/supermium/issues/1907 ...