Microsoft should just rename Windows XP as Windows 9 AS SOME LOOK AHEAD to what Microsoft's next version of its PC operating system (OS) might bring and rumours of Windows 9 are starting to trickle out, the Windows XP support battle continues to drag on. There seems to be only one sensible option here for Microsoft. Scare tactics aren't the answer to making Windows XP users upgrade to newer versions of Windows, so maybe Microsoft needs to think of a way to repackage its next OS in a Windows XP wrapper. It should rebrand Windows 9 as Windows XP 9, and whoever gets the new CEO role needs to get Microsoft's software engineers working on a back-to-basics version for the next OS release, merging the best of Windows XP with the faster performance offered by today's more modern hardware. GO HERE TO READ IT ALL http://www.theinquirer.net/inquirer...ft-should-just-rename-windows-xp-as-windows-9
Microsoft Quietly Fixes Windows XP Resource Hog Problem Microsoft indicated this week that it has fixed a Windows XP resource-hog problem associated with the system's SVCHOST.EXE processes. Windows XP users affected by this problem typically found that the operating system was using up system resources for 15 minutes to an hour after startup, making it difficult to use the machine during that period. The Microsoft Update team had vowed last month to spend the holiday break tackling the issue, which has plagued some users for years. The fix involved stopping the system from perpetually checking Internet Explorer updates. Microsoft indicated that the fix was rolled out on Tuesday." http://tech.slashdot.org/story/14/0...utm_source=rss1.0mainlinkanon&utm_medium=feed =========================================\ =========================================== Microsoft Quietly Fixes Windows XP Resource Hog Problem By Kurt Mackie 01/16/2014 Microsoft indicated this week that it has fixed a Windows XP resource-hog problem associated with the system's SVCHOST.EXE processes. Windows XP users affected by this problem typically found that the operating system was using up system resources for 15 minutes to an hour after startup, making it difficult to use the machine during that period. The Microsoft Update team had vowed last month to spend the holiday break tackling the issue, which has plagued some users for years. The fix involved stopping the system from perpetually checking Internet Explorer updates. Microsoft indicated that the fix was rolled out on Tuesday. On Tuesday, Microsoft depreciated legacy security updates for Internet Explorer that had been replaced by more recent ones. We did this to improve customer experience, reducing the time Windows Update requires to check existing updates before installing new ones. This action was purely to improve update performance and does not affect customer security. - Dustin Childs, group manager, Microsoft Trustworthy Computing Microsoft did not announce the fix broadly. Instead, it released the above statement to Susan Bradley, a Microsoft MVP and moderator of the PatchManagement.org list-serve service, which is a discussion group for IT pros. Apparently, that's the only venue where the statement appeared publicly. Microsoft's January security bulletin announcing four patches and nonsecurity releases did not mention the SVCHOST fix for Windows XP. Microsoft's fix took effect on Tuesday. It apparently stops systems from grinding through older Internet Explorer updates before releasing system resources. The fix also seems not to require any actions by Windows XP users or IT pros to take effect. Of course, Windows XP users still face the broader problem of the operating system falling out of product lifecycle support by Microsoft. On April 8, 2014, Microsoft won't issue updates to the 12-year-old OS at all. http://redmondmag.com/articles/2014/01/16/windows-xp-resource-hog.aspx
