From the rumor mill: Microsoft preparing to "relaunch" Windows 8 in February Written by Ron on January 24, 2013, 03:37PM
It's no secret that Microsoft is blaming PC manufacturers for the weak sales of Microsoft's latest Windows 8 operating system. Now, new details have emerged indicating that Microsoft is preparing to "relaunch" Windows 8 in February with the launch of the Surface Pro.
"Now Microsoft is planning to reboot its launch of Windows 8 next month. On Tuesday the company gave 9 February as the date for the US and Canada unveiling of the Intel-powered Surface Pro tablets. But sources tell us Microsoft is actually preparing for a February 'relaunch' of Windows 8," the report claims. Microsoft is apparently upset that manufactures did not follow guidelines for creating Windows 8 PCs while manufacturers argued that high-end and expensive devices would have been created and consumers would be confused and would not want it. As for this so-called relaunch of Windows 8, Microsoft could be planning a massive media campaign highlighting everything great about Windows 8 and the Surface Pro. We will just have to wait and see exactly what Microsoft has up its sleeve when the Surface Pro is launched on February 9th.
We've already heard from several different PC manufactures such as Acer, Asus, Fujitsu, and Samsung regarding sales of Microsoft's new Windows 8 operating system. HP even offered an opinion explaining the weak Windows 8 sales: "Clearly it's as been reported, it was a slower start than many people expected. But I think as we've gone through January, as we look at retail sales week to week, as we look at web sales week to week, we see continued momentum and continued growth. So, I think the combination of a very new experience, a very touch driven experience, and lots of choices over the holidays, it's not to be unexpected," HP stated in a recent interview. It's pretty funny to see Microsoft blaming PC manufacturers for the weak Windows 8 sales, while PC manufacturers blame Windows 8 for weak PC sales. Will a correctly timed "relaunch" of Windows 8 fix the problem?