KB2839299_2003 derived fltMgr upgrade that it is not...

[MilkChan]

1 hour ago, modnar said:

Thank you, @MilkChan for these two builds. 7-zip and WinZip here says the second, SSE2 update is corrupt - would you mind updating the archive, please?

Thank you, @Multibooter for testing.

The funniest thing now is upon re-configuration of my mini-filters, my system works better than ever before with the 5512 XPSP3 fltmgr and filter cascade. I also put TimeOutValue = 3c (60) (s) DWORD before minifilter re-config in my "disk" service (CurrControlSet) that for some reason did not exist in my harkaz-updated SP2 (to uSP4) XP. That might have had the most to do with it...

Nothing was damaged. This is because I use the same SFXCAB installer that Microsoft uses when distributing Updates.
The file is still normal.
7z or WinRAR are not useful because I create compressed files.

[Multibooter]

I have now installed fltmgr.sys build 5107 also under WinXP SP3 on my i7 desktop computer, by booting into Win10 and then copying fltmgr.sys onto the WinXP partition. fltmgr.sys build 5107 works fine on the 3.4GHz i7 desktop under WinXP SP3 and WinXP feels a little crisper

The updated fltmgr.sys is a must-have for slow computers under WinXP, and a nice-to-have for WinXP on fast computers.

The remaining question now is: Which build of fltmgr.sys is the best one for WinXP SP3?

Edited December 23, 2025 by Multibooter

[modnar]

On 12/23/2025 at 5:09 PM, MilkChan said:

Nothing was damaged. This is because I use the same SFXCAB installer that Microsoft uses when distributing Updates.
The file is still normal.
7z or WinRAR are not useful because I create compressed files.

I'm sorry, somehow I thought I'd just normally decompress them instead of installing them. :-)

Quote

...The remaining question now is: Which build of fltmgr.sys is the best one for WinXP SP3?

Since MilkChan has built those fine update packages, I'd say SSE (b5107) for slower computers and SSE2 (b6912) for faster. Could you please test both and see which is faster. I think b5107 might be faster (it is also the last build in non-ESU fully updated Server 2003 x86).

Edited December 24, 2025 by modnar

[user57]

well technical speaking actually it would be possible to make a check what technology in the XMM registers are possible

there was recently a problem like that with a microsoft file (in the supermium posts) where actually SSE4.1 instructions are used

more professional programms (and useally you would expected something like that from a very big money concern like microsoft) check what instructions are available

(the x265 encoder/decoder does so for example)

after that then the right routine is called up

often it is a compiler setting problem 

one method to avoid this one would be to create an .obj file (what contains the functions without SSE/MMX ect.)

then at first you make the check if SSE can be done

if not you call up that .obj file´s function

if you have SSE you call up your normal function

 

thus you can avoid creating multiple complies like having a SSE version and a non SSE version

[Multibooter]

On 12/24/2025 at 7:52 PM, modnar said:

Could you please test both and see which is faster. I think b5107 might be faster (it is also the last build in non-ESU fully updated Server 2003 x86).

Besides speed, system stability could be another criteria for deciding between fltmgr.sys build 5107 and build 6912 under WinXP.

eMule could be used for comparing system stability/uptime when running with fltmgr.sys build 2180 [WinXP SP2] vs build 5107 vs build 6912.

eMule, installed under WinXP SP2 and running 24/7 on a dedicated old Inspiron laptop (500MHz, SSE-only, 512MB RAM), tends to crash with the original fltmgr.sys build 2180 after downloading for 7-14 days.

Build 5107 has been installed to see whether it can increase eMule uptime, i.e. system stability.

Edited December 27, 2025 by Multibooter

[modnar]

The WorkAround for WinXP SP3 fltMgr (build 5512) with Tag=1 for now is (obeying "Tag" rules and similar to other Windows' configurations):

1.) Go into regedit (Run: regedit), HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/FltMgr, make sure that it has "Tag" [DWORD] value of "1" (0x00000001).

2.) Go into HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Filesystem and make sure only these three settings are in there (factory XP_SP3 settings):

NtfsDisable8dot3NameCreation	[DWORD]		0x00000000 (0)
Win31FileSystem			[DWORD]		0x00000000 (0)
Win95TruncatedExtensions	[DWORD]		0x00000001 (1)

3.) If fltMgr service has Tag=1, you can then go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GroupOrderList/FSFilter Infrastructure and edit it so it reads:

03 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00

.

4.) Restart and enjoy extra responsiveness without any ill-effects.

 

Oh, by the way, @MilkChan you packed the wrong fltMgr in the KB44xxxxxx package, the beta build instead of 6912.

Edited Saturday at 08:12 PM by modnar

[user57]

hmm did you try the code i posted in page 1 ?

for HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/FltMgr, make sure that it has "Tag" [DWORD] value of "1" (0x00000001).

=

"HKLM\0, System\\CurrentControlSet\\Services\\FltMgr\0, Tag\0, %REG_DWORD%\0,01,00,00,00",

others :

"HKLM\0, System\\CurrentControlSet\\Control\\Filesystem\0, NtfsDisable8dot3NameCreation\0,%REG_DWORD%\0,00,00,00,00",

"HKLM\0, System\\CurrentControlSet\\Control\\Filesystem\0, Win31FileSystem\0,%REG_DWORD%\0,00,00,00,00",

"HKLM\0, System\\CurrentControlSet\\Control\\Filesystem\0, Win95TruncatedExtensions\0,%REG_DWORD%\0,01,00,00,00",

 

it would allow you to make a fix directly

[MilkChan]

7 hours ago, modnar said:

The WorkAround for WinXP SP3 fltMgr (build 5512) with Tag=1 for now is (obeying "Tag" rules and similar to other Windows' configurations):

1.) Go into regedit (Run: regedit), HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/FltMgr, make sure that it has "Tag" [DWORD] value of "1" (0x00000001).

2.) Go into HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Filesystem and make sure only these three settings are in there (factory XP_SP3 settings):

NtfsDisable8dot3NameCreation	[DWORD]		0x00000000 (0)
Win31FileSystem			[DWORD]		0x00000000 (0)
Win95TruncatedExtensions	[DWORD]		0x00000001 (1)

3.) If fltMgr service has Tag=1, you can then go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GroupOrderList/FSFilter Infrastructure and edit it so it reads:

03 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00

.

4.) Restart and enjoy extra responsiveness without any ill-effects.

 

Oh, by the way, @MilkChan you packed the wrong fltMgr in the KB44xxxxxx package, the beta build instead of 6912.

WindowsXP-KB4512787-x86-ENU 

build 6912 : https://mega.nz/file/T5gmCYBB#iogwxoD7JCY3-RIbW83J3CfcAKgmZ8zJDbP_k3YicOY

[modnar]

14 hours ago, user57 said:

hmm did you try the code i posted in page 1 ? .........

it would allow you to make a fix directly

I have written it thusly with intent of being a carefully deliberated workaround instead of just a quick fix. And who will find it, will do the effort of going through the four points of implementing it. Besides, points 1.) and 2.) are pre-conditions for even going through with the change. If it has a "Tag" of "4" (unsafe remnant from XPSP2, thanks so much M$, not) abort or change manually even that. Filesystem part should be as mentioned if nothing was added by user.