Linked by Thom Holwerda on Thu 30th Jan 2014 23:13 UTC

Microsoft is once again planning to alter the way its Start Screen works in Windows 8.1 Update 1. While the software giant originally released Windows 8.1 last year with an option to bypass the "Metro" interface at boot, sources familiar with Microsoft's plans have revealed to The Verge that the upcoming "Update 1" for Windows 8.1 will enable this by default. Like many other changes in Update 1, we’re told the reason for the reversal is to improve the OS for keyboard and mouse users.

Wow, a touch interface does not work with a mouse and keyboard. Who saw that coming.

I expect photos of many people eating crow.

Permalink for comment 582171
To read all comments associated with this story, please click here.
RE[4]: hmm
by Megol on Sat 1st Feb 2014 14:29 UTC in reply to "RE[3]: hmm"
Member since:

More disturbing is that my main remaining technical problem:

...has been known about since at least November of last year, I first came across it in December when I set up the laptop, and it is almost February now... and as far as I know, there is no guaranteed "cure." There is no "official" fix that I could find or even acknowledgment from Microsoft for that matter, and if Windows Update is supposed to take care of it, then it sure as hell ain't doing its job.

All I can find are: "try uninstalling and reinstalling various hardware drivers" (no thanks, my current OS is running just fine, 8.1 is not worth that hassle for probably nothing...) or "disable fast start" (which sounds worthy of at least giving a try, I was leery about the "feature" to begin with actually, wouldn't surprise me if it's the problem since once the system has been up for 3 minutes and running fine chances are it won't lock up until next boot).

I fixed what I believe were the main hardware driver-related issues (system failing to come out of sleep mode after updating to 8.1 and requiring a hard shutdown/reboot as a result of bad graphics drivers and something else IIRC).

Maybe that's driver related and if so don't expect MS to fix it. It could also be the cause of a faulty BIOS with errors that MS doesn't detect and patch (they do have some level of patching as non-compliant drivers/BIOS code are all to common)...

Reply Parent Score: 2