tomasz86

Thanks for the tip! It seems that they have just changed the domain where the hotfixes are hosted. Old: http://hotfixv4.microsoft.com/Windows XP/sp4/Fix499402/2600/free/473489_ENU_i386_zip.exe New: https://hotfixv4.trafficmanager.net/Windows XP/sp4/Fix499402/2600/free/473489_ENU_i386_zip.exe This means that I will just have to fix the URLs .

It seems that M$ have closed their hotfix service all together: https://www.ghacks.net/2018/11/05/microsofts-hotfix-service-is-no-longer-available/. This means that all the links to hotfixes on my site no longer work. What is more, those links have also not been archived by the Wayback Machine (perhaps due to robots.txt restrictions?). You can, of course, download the files themselves from my Archive, and I will likely replace all the non-functional official URLs with links to the Archive as well. This is sad to see as my Archive is probably the only publicly available site where the files are being stored right now. I believe that we should have them backed up in more places.

Windows 2000 does not support dynamic frequency scaling, so my guess would be that your CPU is simply running at 100% all the time, hence the high temperatures. You will need 3rd party software to control the frequencies.

http://blog.livedoor.jp/blackwingcat/archives/1299806.html The site is indeed all Japanese, but the filenames are not . As of today, you will need Windows2000-KB935839-v29bG-x86-ENU.EXE Windows2000-KB979683-v16a-x86-ENU.exe

https://ryanvm.net/forum/viewtopic.php?t=9785

UURollup can only be slipstreamed because I manually tweaked the hell out of the installer specifically for HFSLIP . The BlackWingCat's kernel is not prepared like that, so direct slipstreaming is impossible. You should still be able to install it silently in T-13 (svcpack) but only after repacking the installer to the standard M$ format. I am not sure the effort is really worth it.

The registry edit will not work because you need to have the modified kernel files installed first. This is not a technical limitation, just a licensing issue. Simple speaking, Windows 2000 treats each of your cores as a separate CPU, and Windows 2000 Professional officially supports only two CPUs. In one word, you need to install the BlackWingCat's kernel to make everything work, but the kernel is not available in German. You can still force installation of English updates in your system, but the result will be a mishmash of English and German everywhere in the OS. I would really not recommend it, unless you are desperate . PS Please check my website for a complete list of official updates for Windows 2000. I recommend installing / slipstreaming all of them before trying out any unofficial packages. The updates, however, will still not help you with this particular problem though.

No problem. I do not take anything personally. I am aware of the HFSLIP's complexity, especially since it is no longer mainstream but rather a very niche piece of software with its documentation incomplete or spread here and there. I have basically finished rewriting / moving the old, original HFSLIP documentation from http://web.archive.org/web/20100523023650if_/http://hfslip.org:80/_left.phtml to my site, but, to tell the truth, I do not really like it. I think that it is either too complicated in some parts, or too brief in others that actually require a more detailed explanation. My goal is to incorporate the documentation into my site completely, so that all the required information will be available in one place. In order to do this though, I also have to reorganize the layout / structure of the site a little bit. I also want to separate the 2000 and XP updates lists, etc. In short, I do know that the whole project in the current state is difficult to use, and I have many plans on how to improve it, but unfortunately time (or lack of it) is the main obstacle. I agree that the original post should probably be more concrete and informative. I would also greatly appreciate any specific tips on how to structure the post in order to make it more accessible and easy to understand for someone who is not really accustomed to HFSLIP and everything related to it. I would not like to make it a replacement for my website though. What kind of information (and in what order) exactly do you think I should include there? Yes, I agree with this 100%. The lack of proper documentation on HFSLIP (and HFSLIP2000) is the culprit. The whole Windows XP/2003 updates idea should also be explained more thoroughly, so that there is no confusion on why these updates are included in the Windows 2000's updates list. The FullPack is kind of a side project though. The reason why it is not mentioned anywhere publicly is because a) many people prefer to download the updates from official sources only, b) some people have very strong feelings against sharing M$ updates through 3rd party sources, and c) the FullPack is currently English-only and I want to keep the whole project 100% multilingual. I like this idea a lot, but there is already a thread for this: https://msfn.org/board/topic/133014-last-versions-of-software-for-windows-2000/. I am not sure if it is necessary to list the software directly on my site, or maybe it is better to just link to the thread for details. If I ever decide to include such a list on the site though, I would really want to check each program myself in order to determine whether it is really incompatible with the OS. In some cases a simple registry change can "make" the software compatible, while in other cases the software may simply just require particular M$ updates to run.

I am writing this in the Windows 10 forum, although I have a feeling that this issue is related to all Windows versions that have Internet Connection Sharing. I have been trying to set up a desktop PC as a WiFi router. The motherboard is Gigabyte GA-F2A88XN-WIFI which has both wired Realtek RTL8168 and wireless Intel AC 7260 integrated. The cable modem is connected with a standard ethernet cable to the Realtek adapter, and the connection is then shared using the Intel AC 7260 adapter. In order to share the connection I simply use the following command (with my own ssid and key values). netsh wlan set hostednetwork mode=allow ssid=ssidOfUrChoice key=keyOfUrChoice netsh wlan start hostednetwork In the beginning, everything seems to work fine. I am able to connect to the network with other devices and use the Internet from them. The problem is that the connection suddenly drops every now and then (at least once or twice every hour). The PC itself stays connected to the Internet, but the other devices suddenly disconnect, and then re-connect after a few seconds. The cycle then repeats itself indefinitely. I have been trying to solve the problem but I am not really into networking and have no knowledge about how to troubleshoot such issues. I have tried to use both DHCP and assigning static IP addresses, but it made no difference (except for a faster reconnection to the network with the static IPs). In addition, the PC itself was used before to connect to the WiFi through an external router using its Intel wireless adapter, and there were no connection drops there. The connection drops happen even if the devices are located very close to the PC, where the WiFi signal is very strong. I have also disabled the "Allow the computer to turn off this device to save power" options for both network adapters in the Device Manager. Could anyone help me in troubleshooting this problem?

This is a collection of classic themes from Windows 2000 that I ported to Windows 8.1 and 10. I say "ported", because the themes rely on the new high contrast theme engine, and as such obviously are not the same as even the old high contrast themes from Windows 7 and earlier, which relied on the Windows Classic theme engine. Nevertheless, the colour values are taken directly from Windows 2000, so they should at least give you a similar feel (if not look) as the original themes. At the moment, there are 18 classic themes in the package. Also, I have included inverted versions of each of them. Those keep the same colour contrast as the originals, and are usually dark, so they may be more suitable to use in dark environments. In addition, I have also added several of my own versions of the themes that have a few colour values tweaked for better readability (or personal liking ). In fact, this whole idea started with a port of the Windows Standard theme for my personal use. After doing some research, I simply took the colour values from Windows 2000 and injected them into the High Contrast White theme from Windows 10. The theme worked surprisingly well, so I modified it a little bit further and renamed to Windows Standard (Warm). This theme is the one I am using on a daily basis, and while there are issues with some software, I still find it much much better and easier on my eyes than the default Windows 10 theme, whose colours and the overall darkish look can be tweaked only so much. I have put everything on GitHub, so please check there for more technical explanation, and the theme files themselves. https://github.com/tomasz1986/classic2000 Please also let me know what you think about the idea, or if you find any problems with the themes.

You could also just use WINNT.SIF to make your installation process fully automatic so that no user input will be required. http://unattended.msfn.org/unattended.xp/view/web/19/ You could then use your mouse to install the USB drivers once the OS is running. That is what I use when testing Windows 2000 installation in a VM. Alternatively you could just integrate the USB drivers into your Windows source before the installation.

Do not install UURollup. It does include more files than the KernelEx (additional fonts, etc.), but it is also outdated, and the essential components are covered by KernelEx anyway.

Oops, I meant the FullPack not being mentioned on the site. The HFSLIP2000 script itself is, of course, the core component of the whole Updates List project . I have actually been moving / rewriting the whole HFSLIP how-to to my site for the last few weeks, and hope to finish it soon.

But UURollup was just a compilation of BlackWingCat's files plus several other XP/2003 files, fonts, etc. Hence the name "Unofficial Updates Rollup". It was never a replacement for the whole HFSLIP updates list! I think you may be thinking of the unofficial Update Rollup 2 which was indeed a compilation of the official M$ updates and hotfixes released between 2005-2010. The problem is that the package ended up buggy and there was no easy way to rebuild it as I had added all the updates manually, one by one. It was also not multilanguage and thus, all in all, inferior to the standard HFSLIP procedure of slipstreaming all the single updates. I may indeed have to add such an explanatory note about the obsolete updates to prevent further confusion though. As I said above, UURollup in its core was basically a compilation of the BlackWingCat's Extended Core and Kernel. It has no real advantage to the original packages, especially now, as the Extended Kernel has received a lot of updates in the meantime.

I do not recommend using UURollup anymore. It is old and outdated now. The BlackWingCat's extended Core and extended Kernel are the modern solution for extending Windows 2000's capabilities. Mixing UURollup with them may work but I would not do it. UURollup will install old versions of the BlackWingCat's files, so you can never be sure what the result will be. Nevertheless, you can still find the old UURollup files in the depths of my Download Archive, if you really want to . As for the other (official) updates, I recommend following my Updates Lists under http://windowsarchives.com/updates/. The only way to use all of them though is to slipstream everything with HFSLIP2000 and then install the OS from scratch. After that you can just install the BlackWingCat's packages manually. Well, I must somewhat agree with what you are saying (although reluctantly ). Especially in the beginning, I used to start a lot of small projects that ended up being scattered here and there (and thus difficult to manage). In my defence though, I can say that since around 2014 I have been trying to keep everything as concentrated and concised as possible. Correct me if I am wrong, but during the last 3 years the only major "reorganizations" were the forced domain change (which naturally broke all the old links) and the move to MEGA as the main file hosting (caused by the lack of space on Google Drive). I did discontinue and remove many old files with time because, well, most of them were just that, i.e. old, outdated, and obsolete. At the moment there are really only two places where I am active, which are http://windowsarchives.com for all information and updates, and this very thread for other news and discussion. The only two unofficial projects that are still alive and not mentioned on my website are the combined .NET Framework installer (too experimental) and the HFSLIP2000 FullPack package (somewhat risky...). I am also aware that there is lack of proper how-to and I have been working on it. It is a one-man job though, so please understand . I am always open to feedback and suggestions on how to improve the current state of things.

Well, but that was UURollup. I had to do a lot of manual editing in order to make everything work like that. The BWC kernel uses a customised installer, so first of all everything has to be repacked. Next, there are many registry entries that HFSLIP will simply not add automatically, so the files have to be edited specifically with HFSLIP in mind (which I did then). In addition, everything has to be re-checked each time there is an update to the kernel. That is why I said "theoretically". There are, of course, many benefits of slipstreaming the kernel, such as the ability to slipstream new AHCI/RAID drivers or direct .NET Framework 3.5/4.0 integration, but all in all it was just too much hassle . I think that the only reliable way of integration would be to create some kind of a script/program that would repack the kernel automatically so that it could be added to HFSLIP directly. An alternate method would be to make HFSLIP itself support the kernel out of the box. HFSLIP even now has hardcoded many specific updates that are processed separately, such as the Update Rollup 1 or the USP 5.1 so it is indeed possible. Everything would require a lot of time and testing though.

If you mean the @blackwingcat's Extended Kernel, then there is no official way to integrate it directly to the Windows 2000 source. You could theoretically use HFSLIP but you would first have to repack and modify the whole package to make it compatible with it.

Just for the record, technically you are not skipping the Update Rollup 1 because the rollup is already integrated in the USP 5. Update Rollup 1 basically provides a baseline for all the updates released later. It should not cause any such issues in normal circumstances.

I have finally pushed a small update to my site and the Updates List for Windows 2000. I have added the IPv6 update mentioned by @Anixx and have also removed one old update that I found out to be obsolete. I have also been doing a lot of internal testings to check what files are exactly added by each update / hotfix in order to list them on the site later. I have also been working on the HFSLIP 2000 script a lot. I was actually motivated by the @bphlpt's comments and have started to rewrite many parts of the code. It takes time though so do not expect any quick updates in this field in the near future. You can follow the progress on GitHub.

Just for the record, I do use all the different versions of Windows, starting from Windows 2000 to Windows 10 . When it comes to the NT 5.x line, I have always preferred Windows 2000 to Windows XP. Windows 2003 also is/was cool, but being a server OS it was unavailable to normal users. I had also experienced some weirds quircks when trying to install printers in it (that otherwise worked fine in 2000/XP). As for the NT 6.x line, I like Windows 7 but have also always liked Windows 8 (especially on a tablet / hybrid device). I rather dislike Windows 10 for three reasons: 1) constant feature updates resulting in buggy and unstable experience, 2) privacy issues, and 3) the overall "dark" look. At the moment the last one is actually the most important for me as both the bugs are liveable with and the privacy related settings can mostly be blocked. However, the overall theme and especially the black taskbar right in my face from the very beginning is something that I just cannot bare with. The only way I feel comfortable in Windows 10 is to use my custom high contrast theme that makes the OS look similar to Windows Classic (but many programs have issues with high contrast themes, unfortunately). I still do not understand why it is so difficult for M$ to let the users change the OS colours as you could in all versions of Windows up to 7 (Windows 8 had this problem too but at least the overall look was light, not dark).

To Windows 2000? That is unfortunately not possible Unless new development has taken place in the last few months which I do not know about, the maximum you can get is IE6 SP1 with several IE6 SP3 files (already included in my updates list) and WMP10, but the later requires the BWC kernel and is itself non-slipstreamable.

I will think about although the Archive at this point is still not static, i.e. I have been adding files to it (new updates, XP updates, etc.) and removing others. I do submit the site to the Wayback Machine manually each time I have done a major update so they should have already archived most of the files listed there.

While I did manage to find the original direct URLs to the MSI files, they are useless, as they have not been archived by the Wayback Machine. The files themselves are indeed available to download from other sources, but I doubt that it will be possible to find all the language versions, so at this point I am kind of skeptical about including it. Not yet. The changes are still in the testing phase. What I have managed to do though is to upload the whole HFSLIP2000 script to GitHub! https://github.com/tomasz1986/HFSLIP2000 I have re-done all changes one by one, starting from the original HFSLIP, so that everything is properly documented. They may not be 100% in sync with the currently available HFSLIP2000 script as in the process I have found better / more proper ways to do certain things, but they should still be identical in terms of functionality. What took the longest in the original HFSLIP was unpacking and processing of the type 1 (HF1) updates. I was thinking about how to speed things up and came up with a solution where all the updates are unpacked simultaneously first and only processed later. The only disadvantages are that the unpacked updates require more disk space than when they are unpacked one by one, and that the CPU may be bogged down for a few seconds until the unpacking is finished. The speed benefits are instantly visible though. The specific commit is https://github.com/tomasz1986/HFSLIP2000/commit/b7d6a062085105a957491eb80144ff12cf88a3f6 so feel free to have a look if you are interested. Due to importance of the changes, the upcoming version of HFSLIP 2000 will be called 1.1.0. I am all for it . I have always worried that everything would be lost if something happened to me or the files. It is always nice to have multiple backups. Once M$ finally removes everything from their servers, I doubt there will be any other place to download them (in the whole Internet).

Unfortunately it is not compatible with Windows 2000. Firstly, the installer and the executable themselves are blocked from running in the OS. Secondly, although the executable does run when forced to start in XP compatibility mode, the UI is somewhat broken. Specifically, the default theme is broken and, what is more important, the drop-down menus do not display correctly and you have to use a keyboard to navigate through them. In this state I would be against adding it. On a side note, there might have been no visible changes on my site, but I have in fact been working on several improvements lately. I realised that the majority of the KB Article URLs were no longer working, so I have changed all of them to go through the Wayback Machine. Even though some of them do still function, I have decided that it would be too much work to keep checking them individually whether a particular link is still working or not. It may be slower to get to the sites, but at least all of them should be accessible now. I am also working on listing files installed by each update, as I removed the old, inaccurate list some time ago. This time I am not even looking at the information provided by M$. I am checking everything myself with HFSLIP which is time consuming because each update has to be checked separately in order to know for sure what it changes. The lists of files provided by HFSLIP for each slipstreamed update is useless as the updates processed later may (and often do) replace the previously slipstreamed files. In the process I have actually managed to speed HFSLIP up by ~30% (from 17 to 11 minutes) by changing the slipstream related code.

No problem . There are some other packages in that archive which you will likely not find anywhere else (like WIC). I should probably tidy it up a little bit to remove everything obsolete and leave only the stuff that is still viable. For now I have just removed all old daily and weekly releases of the .NET Framework and UURollup so that only last three are left. The other reason to do so was to free some space up. That is why I am also thinking of using 7-Zip to pack all the official updates by folder (so that the folder "180410" becomes "180410.7z") so that you would be downloading all language versions of each update in one package. This would also help preserve the original time stamps just in case something goes wrong and their get modified / reset. From my calculation it would be possible to gain around 2.5 GB this way, despite the fact that the original packages themselves are already packed with SFXCAB. These are still only plans so everyone interested please let me know if you have any objections.