{"id":2331,"date":"2004-05-01T00:00:00","date_gmt":"2004-05-01T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/05\/01\/microsoft-confirms-windows-xp-sp2-delayed-until-3q\/"},"modified":"2021-12-30T11:41:05","modified_gmt":"2021-12-30T11:41:05","slug":"microsoft-confirms-windows-xp-sp2-delayed-until-3q","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/05\/01\/microsoft-confirms-windows-xp-sp2-delayed-until-3q\/","title":{"rendered":"Microsoft Confirms Windows XP SP2 Delayed Until 3Q"},"content":{"rendered":"<p>Microsoft confirmed on Thursday that its much-anticipated Windows XP Service Pack 2 has been delayed for release until late this summer.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Windows XP SP2, a significant Windows client update that incorporates a host of new security features, has slipped for release until sometime in the third quarter, a Microsoft spokesman said.<\/p>\n<p>On April 20, Microsoft security executives said the second-release candidate would be released in mid-May and Microsoft was still targeting to ship during the first half of 2004.<\/p>\n<p>One solution provider, who requested anonymity, said Microsoft bumped into some security issues that it couldn&#8217;t resolve before June.  Michael Cherry, an analyst with Directions on Microsoft, a newsletter in Kirkland, Wash., said the delay illustrates the difficulty of integrating new features with a set of constantly-evolving patches.<\/p>\n<p>More info: http:\/\/www.crn.com\/sections\/BreakingNews\/dailyarchives.asp?ArticleID=49808<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2331","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2331","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=2331"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2331\/revisions"}],"predecessor-version":[{"id":4818,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2331\/revisions\/4818"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}