If the hotfix you want isn't available for public download (and most of them aren't), you must call Microsoft Product Support Services (PSS) to obtain the update.
Generally, you should install hotfixes only for problems you experience on your systems. However, I've taken editorial license with the official hotfix titles and, in many cases, modified the titles so that they better describe the problem that the hotfix corrects. (See the sidebar 'Important Security Hotfixes,' page 62, for information about post-SP1 security hotfixes.) I include each hotfix's URL as a reference. Watson, group policy, hardware, memory leaks, Windows NT 4.0 interoperability, and networking. To help you evaluate this large collection of hotfixes, I've organized them into categories: desktop, DNS, Dr. (If you're just now thinking about installing SP1, see Paul Thurrott, 'Win2K Service Pack 1,' November 2000.)
Although many of the Win2K Professional hotfixes also apply to Win2K Server and Win2K Advanced Server, I don't cover hotfixes released only for Win2K Server versions. As of mid-August, Microsoft had listed 70 Win2K post-SP1 hotfixes on its Web site. If you haven't paid attention to Windows 2000 hotfixes since Microsoft released Service Pack 1 (SP1), this article will prepare you for the next round of Win2K updates. Remedies for what's still broken after Service Pack 1
