MilkChan
Content Type
Profiles
Forums
Events
Posts posted by 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
1 -
On 12/25/2025 at 10:50 PM, VistaLover said:
Both, very old (end of 2017), links to WindowsXP-KB936235-v2 (EN) and/or WindowsXP-KB944340 (EN) return 404 currently
...
KB936235 : info file newversion
KB955988 Replace the Cimwin32.dll file.KB2676562 Leak Update Version for SP2 Replace all nt kernel & system files
KB944340 : info file newversion
KB2676562 Leak Update Version for SP2 Replace the kernel32.dll file.
You can get all my Source Files Update Packs SP2 here.
I would like everyone to archive them. Because they hotfix share is gone forever.https://drive.google.com/file/d/15B55MqPXmJlbSx3Uc4qNmXpsaUH63oBt/view?usp=sharing
my link backup in archive.org
https://archive.org/details/windows-2000-post-sp4-update-pack
https://archive.org/details/windows-xp-post-sp1-update-pack
https://archive.org/details/windows-xp-post-sp2-update-pack
https://archive.org/details/windows-xp-post-sp3-update-pack
https://archive.org/details/windows-xp-and-server-2003-x64-update-pack
https://archive.org/details/windows-server-2003-x86-update-pack_2025064 -
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.0 -
14 minutes ago, Multibooter said:
Thanks for mentioning fltmgr.sys build 6750/KB4493563 in your posts. Build 6750 works OK on my SSE-only Inspiron 7500. The Properties sheet of fltmgr.sys indicates as File Version: 5.2.3790.6750 (srv03_sp2_qfe_escrow.190315-1901), no idea what "escrow" specifically refers to.
On my Inspiron 7500 with a Pentium IIi ["SSE-only" =Non-SSE2] I have tested/run OK the following versions of fltmgr.sys:
- MS fltmgr.sys v5.1.2600.2180 (WinXP SP2 32bit, 4Aug2004-19Jan2005)
- MS fltmgr.sys v5.1.2600.5512 (WinXP SP3 32bit, 13Apr2008)
- MS fltmgr.sys v5.2.3790.3959 (Win2003 SP2 32bit, 17Feb2007)
- MS fltmgr.sys v5.2.3790.5107 (KB2839229, 7Jan2013)
- MS fltmgr.sys v5.2.3790.6750 (KB4493563, 16Mar2019)
- MS fltmgr.sys v5.2.3790.6912 (KB4512787, 11Jul2019)The above versions of fltmgr.sys work under both Non-SSE2 and SSE2. I don't use a special installer, just a file-copy after booting into another operating system.
"MS fltmgr.sys v5.1.2600.2180 (WinXP SP2 32bit, 4Aug2004-19Jan2005)" is a leftover on my Inspiron 7500 in \$ntservicepackuninstall$\,
after the upgrade from WinXP SP2 to SP3. Its timestamp is 4Aug2004 and its file modificaton date is 19Jan2005info here It states that :
Sometimes Microsoft released builds referred to as “Escrow”. Escrow means the development of a branch gets stopped and the code is being tested. If Microsoft or its testers don’t discover any serious bugs (“showstoppers”), the current build becomes the final milestone (usually RC or RTM, but sometimes there are also beta escrow builds). Escrow builds are usually handed out to TAP (Technology Adoption Program) testers, ISVs, IHVs, etc.http://www.windowswiki.info/2010/01/10/what-does-idsidw-mean-and-what-are-escrow-builds/
2 -
8 hours ago, modnar said:
Exactly! I'm glad you noticed the difference! That is how much filter manager is important for the system (it's a tree that all mini-filters are branches of) and bloody Microsoft scum put such pile of horse manure into WindowsXP_SP3!!! Outrageous! I'm superglad it works out for you.
I'm glad it works well for you too! It's such an important part of the system and really can make a difference. I just don't know how on my multi core and multi partition and multi disk system it can't work right... Sigh.
me have some knowledge of modifying Microsoft installer files.
I've modified the update.inf file to a single file and removed files from Server 2003,
except for fltmgr.sys, because it contains necessary registry entries.
1 -
On 12/21/2025 at 11:14 PM, modnar said:
Indeed. I have the KB4512788 (x86 for Win2003 Server); it contains fltmgr build 6912 and all 4 kernel HALs again and also kernel. This fltmgr works in XPSP3/uSP4, but hitches even more than 5107...
If this thing would work normally in XP, it is a much better experience because it isn't maimed like the XPSP3_fltmgr_build5512 is. When it works, the system feels much more robust as WinNT always used to feel when coming from / dual booting 98 and NT4 and NT5. Now XP just because of this one very low level component feels like Windows 98. But hey, it's all we've got so it'll have to be enough until someone backports a proper fltmgr for it.
KB3045999
There's also fltmgr.sys same version
5.2.3790.5107 (srv03_sp2_qfe.130106-1434)I installed it today as I specified,
and saw the difference compared to Windows XP before the update file.
It's as you said, but didn't have any problems with the ESU Update version KB4493563.
1 -
ESU also has this file that has been updated.
I'll probably try KB4493563 from Server 2003 because it's equivalent to WinXP POSReady 2009 Updates.I might have to try it to see what the benefits are.
Because the latest file from ESU is at KB4512787.
0 -
On 12/12/2025 at 3:42 PM, Start Me Up said:
Hello Windows 2000 fans,
when using vanilla Windows 2000 with a rather new version of win32k.sys, there is a bug in the function "fsg_RunPreProgram" which reduces that drawing quality of some fonts. This bug was fixed with the version 5.00.2195.7610 by Microsoft. However, it was reintroduced into the operating system shortly afterwards, so it still exists in the newest version of win32k.sys (5.00.2195.7640).
To fix this bug there are 2 ways:
- Use Extended Kernel 3.1H or newer. Blackwingcat fixed this bug.
- If you don't like or can't install Extended Kernel, there is now a second option available: WINDOWS2000-OTSKB3037639-V1-X86-INTL.exe
There is an article in the knowledge database available with more information on the nature of this bug.
There is some more auxilliary information available, which I do not plan to distribute among end users: code.htm
---
If someone likes to help with an upcoming Windows 2000 update: I am looking for Windows XP updates which contain a version of win32k.sys. My list of known updates is currently pretty short:
- KB3013455 contains version 5.1.2600.6712
- KB3034344 contains version 5.1.2600.6755
- KB4039384 contains version 5.1.2600.7334
Thank you.
You should go to this link. There will be a txt file containing:
Links to all Microsoft files uploaded directly to the MS Catalog.
In all languages.
So you can find all the files you need.https://msfn.org/board/topic/182599-nt-5x-windows-update-urls-dump-inc-custom-support-updates/
0 -
4 hours ago, jumper said:
I'll look into it.
12 hours ago, assenort said:Thank you, @jumper, for patching the MS Office 2010 MSO.DLL file (x32-bit version).
Can you please do the same for the 64-bit version too? Thanks in advance :-)
Greets!
It seems like abbodi1406 has already done that in
# Office 2010 MSI Upsourcer
You should try it.Link : https://mega.nz/file/LgZyCZxa#ew7SgnszJXa8lX0miZAIQk6qGQJljiRxSunc-ynaSow
2 -
Update to Version Ver20250522
Update rootsupd and rvkroots.Change EXE from WinRAR to Windows Win32Cab
0 -
14 hours ago, NotHereToPlayGames said:
My Office is 2007, so I may not be of much help.
But maybe this will fix your issue (article cites your exact issue but on Windows 2000) -- https://superuser.com/questions/1504407/office-2003-cant-open-newer-office-files
More specifically, solution was to use "version 2" of the compatibility pack (linked in superuser article) -- https://www.malavida.com/en/soft/microsoft-office-compatbility-pack/download
"This is a pre-release version of the Compatibility Pack and can only open pre-release Office 2007 files."
= This is a problem with MSVCRT.DLL in Windows 2000.
I have created Update KB926436-v2 to fix this issue in Windows 2000.You can use the latest version.
MEGA
Thanks for the information from 2013.
https://msfn.org/board/topic/161323-msvcrtdll-without-_resetstkoflw-w2k/0 -
2 hours ago, Start Me Up said:
zip file? Which zip file? I have no zip file with this name. Anyway, I found them on Microsoft's server.
???????
You didn't check these links of mine which have all the files you need
https://archive.org/details/windows-2000-post-sp4-update-pack
https://archive.org/details/windows-xp-post-sp1-update-pack
https://archive.org/details/windows-xp-post-sp2-update-pack
https://archive.org/details/windows-xp-post-sp3-update-pack
https://archive.org/details/windows-server-2003-x86-update-pack_202506
https://archive.org/details/windows-xp-and-server-2003-x64-update-pack0 -
10 hours ago, Start Me Up said:
The update "Windows Server 2003/KB4516665" has been added to the help file. However, I was not able to find any security related reports on this update (like MS12-345 or CVE-1234-5678).
You won't find it because it's a leaked file.
form @abbodi14060 -
9 hours ago, Start Me Up said:
That would be helpful. Thank you.
KB4039384 It's in the Windows XP No SSE2 Patch Rollup.zip that I gave you.
1 -
16 hours ago, Start Me Up said:
Once again: Thank you very much, MilkChan. You deserved yourself a spot in the acknowledgements list of the update "OTSKB000001" and have been added to the help file. I am now able to make the update "OTSKB000001" compatible with Windows XP and Windows Server 2003.
---
Yes, I need to analyse all language editions of the file win32k.sys. Or at least that was necessary in Windows 2000.
---
I noticed, that installing the update "Windows XP/KB4493927" in a vanilla Windows XP system is not possible. To allow installing this update the key "POSready" and the value "Installed" need to be in the registry. So I added the update to the help file and added a note in the subtopic "system requirements" as a help with the installation.
---
things to do:
- add the update "Windows Server 2003/KB4516665" to the help file
- analysis of the updates "Windows XP/KB4493927" and "Windows Server 2003/KB4516665" to check whether there are any changes to the function "CreateXlateObject" and what the offsets are. Then update "code.htm".
- add version 4 of the update "OTSKB000001" to the help file
- write the version 4 of the update "OTSKB000001"
Yes, it is an update for Windows Embedded POSReady 2009 (Base form Windows XP).
That update uses SSE2 instructions, which may cause problems with CPUs without SSE2.I am checking for another version of Windows XP that does not use SSE2.
1 -
2 hours ago, Start Me Up said:
Thank you very much, MilkChan. I already used the file from Windows Server 2008 to verify whether the bug still exists. It does exist even in Windows Server 2025. But knowing which update contains the latest version of win32k.sys allows me to write an update for XP and Windows Server 2003, too. Otherwise I would be patching an old version which has other bugs.
So, yes, I am interested in knowing the latest update which contains the win32k.sys for Windows Server 2003, too.
At the moment I will stick with the 32 bit versions. I do not have much experience in writing 64 bit code. So I don't want to risk messing up someone's system.
for Server 2003 x86/x64 (Extended Security Updates) - KB4516665 (5.2.3790.6946)
When you need multiple languages
Here are all my Update Packs Source Files with update ESU that My friend and I kept it too have uploaded to archive.org
https://archive.org/details/windows-2000-post-sp4-update-pack
https://archive.org/details/windows-xp-post-sp1-update-pack
https://archive.org/details/windows-xp-post-sp2-update-pack
https://archive.org/details/windows-xp-post-sp3-update-pack
https://archive.org/details/windows-server-2003-x86-update-pack_202506
https://archive.org/details/windows-xp-and-server-2003-x64-update-packAnother thing is Windows 7/Windows Vista/Windows 8/8.1 can use
Windows Server 2008(NT6.0)/Server 2008 R2 (NT6.1) /Server 2012(NT6.2)/Server 2012R2 (NT6.3)Update/Patch
because it is Code Base.1 -
On 4/28/2025 at 8:21 AM, Start Me Up said:
Hello Windows 2000/XP fans,
while I was working on a graphics driver, I noticed random crashes (blue screens) which were hard to reproduce. They don't happen often, but when using a display mode with 16 colors (for example 640x480x16 colors) they seem to happen more often than with other color depths.Eventually I was able to narrow down the problem and came to the conclusion, that the root cause is a buffer overrun in the function "CreateXlateObject" in the file "win32k.sys". This buffer overrun sometimes caused a random crash. In the most cases it happened within win32k.sys.
I observed, that this issue is not fixed even in the newest version of win32k.sys from a Windows 2000 update from April 2016. An old version of win32k.sys from Windows XP has the same problem. I don't know which Windows XP update contains the newest version of win32k.sys for Windows XP, so I could not validate whether this issue was ever fixed - and if so: how.
So I thought about what to do and came up with the idea, to write a Windows update of my own to fix this bug.
So far I gathered necessary information and wrote a help file which contains most of what I know about the nature of this issue and how it can be fixed:
OTSKB.chmThere is some more auxilliary information available, which I do not plan to distribute among end users:
code.htmEventually, I fixed the win32k.sys from Windows 2000 manually with a hex editor to test the proposed solution:
5.00.2196.0001.zipThe update, which would do this automatically and then install the new file automatically, is not written, yet.
I would appreciate some feedback before I continue writing the update. Please let me know what you think. Maybe I just got it all wrong, don't know.
Edit: The title has been changed from "request for comment" to "looking for a beta tester".
Edit: The title has been changed from "looking for a beta tester" to "released".
Hi
for Windows XP SP3
KB4493927 (POSReady) Updates 5.1.2600.7684Do you need Server 2003 and XP x64 too?
1 -
@Zorba the Geek Not sure if you should update VC++ 2019
found the final version of Windows XP that installed all dll api correctlyx64
You can downgrade the file and it will work with older versions as
concrt140.dll
vccorlib140.dll
vcamp140.dll
msvcp140.dll
msvcp140_1.dll
msvcp140_2.dll
Not related
msvcp140_atomic_wait.dll
The files are all newer, the rest are loaded in Windows normally.1 -
On 6/9/2024 at 3:30 PM, Zorba the Geek said:
MilkChan I noticed that you released an updated version of YumeYao's WMP11 addon at My Digital Life and you list some corrections of errors in the original version 3.4.5. Could you clarify some points for me so that these corrections can be incorporated into my addon?
- In the registry the build date of KB973540 is shown as 14/07/2009, while the build date shown in the properties of wmpdxm.dll is shown as 13/07/2009. Is this the build date error you were referring to?
- What is the missing security catalog. There were no errors shown in setuperr.log.
- What is the fix for ptpusb.inf required for Windows 2003
- wpd.inf is not included with WMP9 or WMP11. Why was it supplied as a dummy INF file with only the header?
- wmp11.cat appears in OnePiece's AIO update pack and the YumeYao WMP11 addon. Is this the .cat file conflict you were referring to? Is the resolution to rename wmp11.inf?
- mpg4ds32.ax_ and msadds32.ax_ would have the effect of removing these decoders from the system. Is there a reason for this?
- What are the files essential to the system that were deleted in YumeYao's WMP11 addon?
- What was the KB973540 string not working properly?
- What was the issue in version 3.4.1 that prevented mp3 files from playing?
I will remove my version
Because got the original addon version file of v3.5.1 updated by adric.0 -
5 hours ago, Condor.07 said:
are you serious or joking?
I have all the original files in all languages do you understand?!
in which language should I write it to you?!
I just need to know how to create the pack, is it that hard to understand?!
Thanks
I'm not teasing you If you have a file as requested for Italian, real and complete And I can do
0 -
56 minutes ago, Condor.07 said:
For Windows 2003 Server x64 the official languages are 19!
I asked you how you create packages for the x64 versions, since DXUPAC does not work.
If you want to give me an answer I thank you.
If you want to evade the question I will find the method in another way.
ThanksI already told you that if there is no source files, the language and I only have English.
The Japanese language, I created it, just making each message straight text files in DLL.
And the following problem is SFC
There is a lot of mistakes.19 that language I already know You will never find official files.
Unless you have to ask for Microsoft only0 -
On 6/2/2025 at 4:15 AM, Condor.07 said:
what program can I use for x64, since the DXUPAC program only works for x86
I would like to integrate all updates for Windows 2003 Server x64 for all languages.
Thanks
It is not useful for other languages in x64
Some source files are only released in the company and on request
and only in English
Some updates like RDP in x64 are only in 2 official languages
English and Japanese0 -
Since I have released a new version of Update Packs for
RyanVM Windows XP Post-SP2 Update Pack
I have checked several new and old missing Updates
which are missing KB894871 not in Update Packs.
And can't access thehotfixshare.net at all
It will give ERR_SSL_PROTOCOL_ERROR
Each time
KB894871 - When you use the System Preparation tool and the Sysprep.inf file to update drivers on a Microsoft Windows XP image, the File Signature Verification tool may report that some drivers are not digitally signed0 -
On 3/7/2025 at 11:39 PM, zcarrt said:
I am trying to make fully slipstreamed windows 2003 64 bit ISO. I tried DXUPAC but it didn't work. Can you make a simplified Chinese version of IE 8? Thank you in advance.
The tools do not have the ability to create x64
multilingual
I created only Japanese and English because both Windows XP and Server 2003 are x64Chinese Only Server 2003 x64 no XP
and it is not worth me to do it but I can share the update with you (DM)0
Realtek High Definition Audio Driver for HP z230
in Windows XP
Posted
You simply need to install KB888111 first, and then install the existing Windows XP audio drivers from the audio manufacturer's website.
If you have any problems, contact me.