{"id":1357,"date":"2004-11-29T00:00:00","date_gmt":"2004-11-29T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/11\/29\/microsoft-cans-windows-2000-sp5\/"},"modified":"2021-12-30T11:39:13","modified_gmt":"2021-12-30T11:39:13","slug":"microsoft-cans-windows-2000-sp5","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/11\/29\/microsoft-cans-windows-2000-sp5\/","title":{"rendered":"Microsoft Cans Windows 2000 SP5"},"content":{"rendered":"<p>Microsoft has dumped the idea of releasing a fifth service pack for the enterprise-popular Windows 2000, and, instead, plans to produce an &#8220;update rollup&#8221; in the middle of next year as its last security patch for the OS.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>According to a posting on Microsoft&#8217;s Web site, the Update Rollup for Windows 2000 Service Pack 4 (SP4) will include all the security-related updates produced for the operating system between SP4&#8217;s release in November, 2003, and when the Redmond, Wash.-based developer finalizes the rollup&#8217;s contents.<\/p>\n<p>It will also contain &#8220;a small number of important non-security updates,&#8221; said Microsoft.<\/p>\n<p>It&#8217;s taking the rollup route&#8211;which it also used in October 2003 when it released a cumulative collection of security fixes for Windows XP&#8211;rather than a service pack, said Microsoft, because the number of not-seen-before updates are few, and Microsoft expects to have released most of them as individual updates prior to the rollup&#8217;s release.<\/p>\n<p>Microsoft will end support for free security fixes to Windows 2000 in June, 2005.<\/p>\n<p>http:\/\/www.newsisfree.com\/iclick\/i,62767654,1920,f\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1357","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1357"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1357\/revisions"}],"predecessor-version":[{"id":3844,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1357\/revisions\/3844"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}