[quote]
Chris Capossela, Chief Marketing Officer at Microsoft, said in the latest edition of the Windows Weekly that this was the moment when the company indeed went too far, pointing out that the two weeks between the moment when users started complaining about the unexpected behavior and the one when a patch was released were “very painful.”

“We know we want people to be running Windows 10 from a security perspective, but finding the right balance where you’re not stepping over the line of being too aggressive is something we tried and for a lot of the year I think we got it right, but there was one particular moment in particular where, you know, the red X in the dialog box which typically means you cancel didn’t mean cancel,” he said.

“And within a couple of hours of that hitting the world, with the listening systems we have we knew that we had gone too far and then, of course, it takes some time to roll out the update that changes that behavior. And those two weeks were pretty painful and clearly a lowlight for us. We learned a lot from it obviously.”[/quote]

They definitely learned something-- they learned just how far their anti-consumer practices can go before the pot boils over. They learned what that threshold was. They learned just how badly they could fuck us, to the picometer.

They didn’t learn to not fuck the consumer, as that article seems to imply. Next time they’ll fuck us ever so slightly less, so the internet doesn’t explode again in bile and hatred. Good for them, but definitely not good for us.

Microsoft's latest Windows 10 patch breaks multi-monitor gaming and the current workarounds are inadequate. How about using that telemetry data to flag users who shouldn't install a given update, instead of making them all mandatory?

Looks like it’s not just if you run games on multiple monitors, just if you have more than one connected.

I just updated to 15002 last night. It took 2+ hours, I went to bed after a while. Had to leave the computer on all night because the Install Updates and Shutdown Option only goes 1/10th of the way through the process before shutting down. So stupid.

So this morning when I log in I have to wait another 30 minutes while it updates my profile. When I finally get in my whole profile is busted to hell and the explorer doesn’t even work. I finally found a guy on reddit who posted that unplugging his extra monitor fixed the issue. I was pretty skeptical, and tried a lot of other options including reboots, new profiles, etc but when I finally tried that it all worked.

If I understand this correctly, update 15002 is an insider update and aren’t insider updates a beta release. Since this is a beta release won’t there be bugs and issues that need to be reported so that when Microsoft releases the final version the problems you are having will supposedly be fixed. This is assuming that Microsoft actually listens to the “Insiders”.

If I understand this correctly, update 15002 is an insider update and aren’t insider updates a beta release. Since this is a beta release won’t there be bugs and issues that need to be reported so that when Microsoft releases the final version the problems you are having will supposedly be fixed. This is assuming that Microsoft actually listens to the “Insiders”.

Yes, it’s an insider build and you can expect these kinds of things on the fast ring, absolutely. I just haven’t run into anything near this bad yet, it’s all been pretty stable. The only reason I am on the fast ring is for the linux subsystem updates - no other way to get them.

It’s not a big deal even if it trashed my system, it would just take a couple of hours to restore. Which would be annoying, but not the end of the world. I was more venting about the length of the update process. I can reinstall that build from scratch faster than the update. Also it would be nice if when you select update and shutdown it actually went through the full update including profile upgrade instead of the current ‘shutdown and do the update next time you turn on the machine’.

I thought so, but to read all the chatter on the internet you’d think that this was an official update that was going to screw up every computer that used dual monitors. It still might when the official update comes out, but hopefully Microsoft will have it fixed by then. Which by the way makes me thankful to all of you who have the time and patience to run beta software and report the bugs you find.

Is there a good replacement for the Metro shell style? I am thinking of buying the Object Desktop bundle, but I am not 100% happy with the few skins I’ve seen. I like Windows 7 very much, but am open to other “skins”.

Can anyone recommend a WindowBlinds skin that is not too flashy or weird?