win 10 forced update causes first casualties...

[Elixer]

Now, who didn't see this coming?
While it is true that it also kills win 7 & 8 systems, at least they have a way to skip it.

Microsoft released an update "KB3064209" to update Intel Microcode, and now you got lots of people in BSOD death loops.
Lots of reports of this, like https://communities.intel.com/thread/77391

 

[SparkyJJO]

Except is it really a MS issue, or an Intel issue? Sounds like an Intel issue to me...

 

[Elixer]

MS pushed the update...

 

[SparkyJJO]

Right, but if it is Intel's microcode, MS doesn't have a lot to do with it aside from pushing it out right?
Or I may be misunderstanding the whole thing entirely.

 

[Dahak]

Well to be fair this is also affecting Win 7 and Win 8 machines as well, no need to pin it directly on Win 10

 

[Elixer]

Well to be fair this is also affecting Win 7 and Win 8 machines as well, no need to pin it directly on Win 10

Yes, I said that, but those are optional on 7 & 8, not on 10, everything gets pushed on 10.

 

[MustISO]

Welcome to the first week of an OS. Not sure why people are rushing to install it. I've already talked to several people who had had issues with the upgrade or after the update. Outside of installing it on a virtual machine I'm waiting for the service major update and even then it'll probably never go on my primary system.

 

[quikah]

Title is wrong. This microcode update was rolled into the Windows 10 release. There is no Windows 10 "forced" update. The updates in the KB are for Win 8/7/2008/2012.

If you have the effected processor, you should probably not install Windows 10.

 

[Ketchup]

If Microsoft received a software update from a vendor, they are the ones who are ultimately responsible for making absolutely sure it works. Whether it's Intel's code or Microsoft's own code, they are the ones that are pushing it out to customers running their OS.

 

[Socio]

You know I have read speculation that since technological, and software advancements have slowed down keeping older systems relevant longer and longer that the forced updates are forced so that Microsoft can use them to deliberately break hardware or shut off parts of the bios to make it appear broke after a period of time.

In doing so it naturally forces the end user to upgrade say the motherboard, then of course the processor and ram for example and of course buy a new Windows license.

Which is a win-win for the hardware industry, and for Microsoft.

Perhaps there is some truth to it?

 

[Ketchup]

This has been speculated ever since Microsoft used the term "life of the device."

Another view is to consider MS saying something like this: "hey, people and companies are buying new devices all the time. Combined with the Store, we can get plenty of revenue in this way. Individuals who are going out an buying a copy of MS to update their existing computer? Miniscule in comparison. We can make people think we are saving them money (making ourselves look good), and we will actually end up making money in the end."

 

[Sabrewings]

You know I have read speculation that since technological, and software advancements have slowed down keeping older systems relevant longer and longer that the forced updates are forced so that Microsoft can use them to deliberately break hardware or shut off parts of the bios to make it appear broke after a period of time.

They would have to be retarded. Do you know how large of an anti-trust suit could be brought against them?

Besides, they can't even get Windows 10 to upgrade properly on my machine when I want it to. Why should I believe they could surreptitiously break my hardware in the background if they can't even get the easy things right?

 

[Steltek]

They would have to be retarded. Do you know how large of an anti-trust suit could be brought against them?

Besides, they can't even get Windows 10 to upgrade properly on my machine when I want it to. Why should I believe they could surreptitiously break my hardware in the background if they can't even get the easy things right?

You forget, you are talking about Microsoft here. Breaking things is apparently what they do. It could even be considered their unofficial company motto.

In these days and times, anti-trust suits are pretty much a lost cause - too much money paid to line the pockets of too many corrupt lawyers, judges, and politicians. They litigate them for 10 years, then settle for peanuts once everybody on the take has gotten rich. Otherwise, Microsoft would have been broken up into multiple companies years ago.

 

[SparkyJJO]

You forget, you are talking about Microsoft here. Breaking things is apparently what they do. It could even be considered their unofficial company motto.

In these days and times, anti-trust suits are pretty much a lost cause - too much money paid to line the pockets of too many corrupt lawyers, judges, and politicians. They litigate them for 10 years, then settle for peanuts once everybody on the take has gotten rich. Otherwise, Microsoft would have been broken up into multiple companies years ago.

 

[sandorski]

Fortunately for me my SSD is all filled up and I have no idea why, nor do I feel enthused enough to figure out why right now. Sometime in the next few weeks I'll do the upgrade, but for now I'll avoid the drama.

 

[ninaholic37]

Welcome to the first week of an OS. Not sure why people are rushing to install it. I've already talked to several people who had had issues with the upgrade or after the update. Outside of installing it on a virtual machine I'm waiting for the service major update and even then it'll probably never go on my primary system.

My dad has Windows 7 on his laptop. I told/warned him that Windows 10 was out, and it was free upgrade, and he replied (confidently) that it's better to wait a year for MS to work out the bugs. It was a funny comment, because of the MS letting you upgrade for free for the first year thing. It's like he intuitively knew that anyone upgrading in the first year were "beta testers working for free" (suckers) for their new OS. I was impressed, my dad was smarter than I thought. :awe:

 

[SparkyJJO]

I reserved right away but even when it is available I may wait for several months before applying it. Not sure yet.

 

[cmdrdredd]

I've had no issues on 4 machines doing the upgrade in place. Everything works. Honestly I think there's a lot of unnecessary fear mongering.

 

[2is]

Welcome to the first week of an OS. Not sure why people are rushing to install it. I've already talked to several people who had had issues with the upgrade or after the update. Outside of installing it on a virtual machine I'm waiting for the service major update and even then it'll probably never go on my primary system.

Never? At what point did you adopt this philosophy I wonder? Just curious because if it was say, 10 years ago, you're still on Windows XP, if it was longer than that you might be on Windows 2000 or 98.

 

[JEDIYoda]

who cares about being fair?? People will say its Microsoft`s fault even when it is not.....lolol

 

[pcgeek11]

I've had no issues on 4 machines doing the upgrade in place. Everything works. Honestly I think there's a lot of unnecessary fear mongering.

It has been like that as long as I remember... I started on computers running MSDOS 3.

It is new and will have rough edges for some.

 

[davmat787]

who cares about being fair?? People will say its Microsoft`s fault even when it is not.....lolol

Yep, nv4_disp.sys bugcheck f4... How long did people put up with that while blaming Microsoft even though it was crappy third party code?

Class drivers are a great thing and third party driver code should be kept to a minimum.

 

[mikeymikec]

Not sure why people are rushing to install it.

This. I could understand if most of the people who rushed to upgrade straight away were young enough not to remember previous scenarios affecting "early adopters" of new MS operating systems. That's just aside from the amount of people who will roll the dice on an unnecessary major upgrade even though they haven't properly prepared for the possibility of the upgrade going wrong.

 

[DustinBrowder]

Title is wrong. This microcode update was rolled into the Windows 10 release. There is no Windows 10 "forced" update. The updates in the KB are for Win 8/7/2008/2012.

If you have the effected processor, you should probably not install Windows 10.

This is wrong. It is forced update. You can disable updated on windown xp,7,8 and 8.1. You don't have the option to disable updates or install when you want to on win10 home edition. Pro edition you can delay the updates for a certain time, but on that edition it will automatically update at some point.

Only the enterprise edition can significantly delay updates up to 2 years.

 

[DustinBrowder]

Yep, nv4_disp.sys bugcheck f4... How long did people put up with that while blaming Microsoft even though it was crappy third party code?

Class drivers are a great thing and third party driver code should be kept to a minimum.

But MS pushes it. There is ALWAYS going to be faulty 3rd party software and MS faulty updates, in previous versions of windows you could NOT install them, in win10 it forces ALL the updates on you, you have no option NOT to install an update!