Leaderboard

I've attached RAR5 compressed files with lists of download links for all official updates for Vista 32-bit and 64-bit Post SP2 up to April 2017. Includes all language packs for Vista, IE9 and local Help update. Also included are Ultimate Extras, Optionals and .NET Framework 3.5 SP1 / 4.52 with updates. Superseded updates are not included except for a few ones just to satisfy Windows Update. Hotfixes are not included, unless available through Windows Update. Someone please mirror them on Web Archive. ASAP. EDIT: Updated files with .NET Framework 3.5 SP1 Language Packs. Installing System Updates: If you want to install a language pack, you must do it first, by downloading and running the language pack executable. 1) Download all files from Main_URLs.txt to the same folder. 2) Using WinRAR, sort files by type and unpack all .MSU files to the same folder, overwriting existing files. Then you may delete the .MSU files to save space. 3) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 4) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 5) Run Main_Part1.bat, Main_Part2.bat and Main_Part3.bat. At the end of execution of every batch file, Windows will restart automatically. 6) Optionally you may install local copy of Help update (LangPacks_Help_URLs.txt) and the IE9 language pack (LangPacks_IE9_URLs.txt). PS: It'll take a while to install all 210+ updates. Installing .NET Framework 3.5 SP1 / 4.52 with updates: 1) Download all files from NDP35_45_URLs.txt to the same folder. 2) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 3) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 4) Run NDP35_45_Install.bat, if needed Windows will restart automatically. 5) Optionally you may install a language pack (LangPacks_NDP35SP1_URLs.txt and LangPacks_NDP452_URLs.txt). Installing updates for optional features (only if you have installed IIS, IIS ASP, IIS FTP or Telnet from Program and Features Control Panel extension) Download all files from Features_URLs.txt and run the following .MSU packages if you have installed: IIS: KB4012373 IIS ASP: KB2124261 IIS FTP: KB975254 Telnet: KB960859 and KB3020393

Now USB 3.0 works also on Intel chipset under XP SP3 Yesssssssssssssssssssssssssssssssssssaaaaaaaaaaaaaaaaaaaaaaaa:))))))))))))))))))!!!!!!!!!!!! Dietmar https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-82.html#msg83830

official build got errors as well, but it is not good to post bug report to their side with my account.

+1.

Hi Jumper, I can now print with SumatraPDF 3.1.2. using the 'Win2k_PD4: PrintDlgW_fwd' comp-mode !! The other three did not work. Haven't checked the ME modes. Will test other apps during the weekend. Thank you very much !!!! @Goodmaneuver. Thanks for looking into my SeaMonkey issue but I have to admit that I did not understood what you suggested to do. But no problem !!

@erpdude8 I am darned sure that at any given point, you only need to install the latest Flash update for Windows 8. That's all I do on a new installation.

Thanks, yeah the pnidui.dll threw me off, I was searching for them in the .mun files

@Tommy, I am not sure when you used my packages before, but according to the changelog on my website, I removed the unofficial updates from the updates lists in 2014 . I do not remember exactly when I removed them from my FullPack, but I would guess that it was around that time too (maybe a little bit later, but still ~4 years ago). I decided not to include them, as I wanted to focus mainly on providing a stable base with all the official updates integrated, and leave the unofficial modifications to the more skilled people (who were @WildBill and @blackwingcat at the time). As for the USP 5.1, it is not included because it installs buggy USB 1.1 drivers, and also is English-only while I want to eventually provide my packages in all languages supported by Windows 2000. Also, while I do not have the hard data right now, judging from my testing in the past, I am almost 100% sure that all the updates and hotfixes included in the USP 5.1 (excluding the buggy ones) are covered by my updates list. As you said, DX 10 or even any unofficial drivers would require to have the unofficial kernel / core installed in the first place, thus I am not including any of them. While there are a few unofficial packages listed on my website, they are mainly just repackaged versions of official system components, such as the .NET Framework addons, or the additional system fonts, both of which work in stock Windows 2000. Unless I decide to include the unofficial kernel / core, or any other modified files on my website, I do not plan to include any such unofficial packages for now. If I ever change my mind, they would become a separate list, as I want to keep the main updates list stock.

Highly unlikely ; you rebuilding your browser profile from scratch was what probably fixed your CPU issues (possibly some conflicting extensions/preferences/about:config settings were the cause of elevated CPU cycles in your original profile...). FWIW, --no-remote is just a cmd line switch that means "don't talk to an existing Firefox, start a new instance"; together with the -p switch, one is able to launch a new Firefox (or fork) instance loading the specified profile, so that the two Firefox instances one ends up with are completely separated! For anyone that cares, there exists an excellent article dedicated to the switch in question, found here

Well, actually (for the record) there is a very good free tool that can be used for the conversion between GPT and MBR: https://www.rodsbooks.com/gdisk/ but - basically - it is just a matter of using a hex viewer/editor (knowing where to look for). The difference between GPT and MBR styles is ONLY in the way the partition(s) are "indexed" or - even more accurately - where and how the addresses of the extents of the partitions/volumes are stored, the actual volumes are exactly the same so (unlike - to make an example - a file system conversion) there is no actual "conversion" of data, it is simply a matter of reading an address and write it in another place in a slightly different notation, even if a lot of references (and of course those making Commercial software) make it look like rocket science or brain surgery, it is not, things may become more complicated if there are more than four partitions (as in GPT you can have *as many* partitions as you want and they are all "primary" whilst on MBR you have max 4 partitions - primary - or three primaries and all the other ones must be logical volumes inside extended) but on a SSD like yours (and actually most "normal" disk devices) with just two partitions/volumes it is straightforward: https://www.rodsbooks.com/gdisk/mbr2gpt.html jaclaz

Hello dear! For Volume Icons SndVolSSO.dll.mun inside SystemResources. For Network Icons you can still editing "pnidui.dll" inside System32 folder.

Good (which actually means "bad" ). The issue is that the booting mechanism is different (but it can be solved, don't worry, only it isn't exactly "simple"). A UEFI based computer is - generally speaking - compatible with the "old" (and "good") MBR style of partitioning (most UEFI based computers have a CSM or Compatibility Support Module, aka BIOS) but the reverse does not apply. The BIOS booting sequence (for a Windows NT 6+): BIOS->MBR (first sector of hard disk)->Active partition in partition table->PBR (or boot record of partition)->BOOTMGR.EXE->\boot\BCD->Winload.exe->Windows the UEFI: UEFI->a partition with a given GUID, usually FAT32 formatted->a file BOOTMGR.EFI->\EFI\Microsoft\Boot\BCD->Winload.EFI->Windows The GPT style of partitioning includes a so-called "protective MBR partition table" to avoid issues, so all your BIOS can actually see in the MBR (that has NO code) is a huge single partition with ID 0xEE. Now there are two approaches to solve the problem (for the moment only the booting one): 1) leave the disk//SSD "as is" and boot from another device (the USB stick) then boot (in BIOS mode) the existing install on the SSD and see what issues (if any) come out 2) convert the disk/SSD (connected to another computer) style from GPT to MBR, add the relevant files and then attempt booting from it The #1 is "safer" in the sense that the SSD isn't touched at all but until the conversion to MBR is made it won't boot without the USB "helper", the #2 is more risky in the sense that if something goes wrong during the conversion you are stuck. There is actually a third way (adding a booting mechanism to the SSD that remains GPT style but allows booting on BIOS) but - while doable - is a bit complex. You will need anyway a few files from an original Windows 10, ideally if you have a Windows 10 DVD (or image) it would be better, and even better if you have another PC running Windows 10 to which you can connect the SSD, which I believe you have since you posted that screenshot. The generic idea is to make (conceptually) a "Vista boot floppy": http://www.multibooters.co.uk/floppy.html only that it will be "Windows 10" and not a floppy but rather a USB stick. We need to make the USB stick bootable (I would suggest something that boots to grub4dos as it offers a few features that might come handy), a good tool might be RMPREPUSB: https://www.rmprepusb.com/documents/rmprepusb-beta-versions and then run BCDBOOT, copying creating the needed files on the USB stick *like*: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di jaclaz

Hmm. He did mention previously that the version numbers of those two files obviously did not match up with the other files, which may not sit well. I don't know if he changed them, but if not, try imagecfg (https://robpol86.com/imagecfg.html). The syntax would be: imagecfg -b *version number* *file path* Alternatively, you could try doing the manual inf install with the new files, then replacing them with the old files in WINNT\system32\drivers before rebooting. UPDATE: I noticed a 25% performance boost in Cinebench R11.5 x86 in XP x64 with 320.xx drivers over my 261.19 in win2k, so I looked at the missing dependencies against extended kernel/core: DisplayDriverExt.dll and nvdispgenco32.dll: one in setupapi.dll (SetupDiGetActualSectionToInstallExW) The nv4_disp.dll from 306.81, does in fact have no missing dependencies whatsoever. nv4_mini.sys (the 306.81 version as well), needs videoprt.sys. Doesn't exist in vanilla win2k but extended core provides it. With that in mind, I gave 306.81 a spin for myself with all original files. It gave an "invalid flags" error at the end of the install through device manager, and it appeared listed as the old driver version afterwards, but the files were in fact updated. Unfortunately my cinebench result went down further to 35 fps from 40, so I'm going back to the old driver. It is important to note that there were no stability issues, at least in my limited testing. This could very well be holy grail for those with 500/600 series GeForces, Quadro 7000s, and earlier Tesla models (for supercomputers).