Microsoft Clarifies which Intel SSDs Borking Installs

FrgMstr

Just Plain Mean
Staff member
2FA
Joined
May 18, 1997
Messages
58,694
Intel just sent word over to let us know that Microsoft has clarified which Intel SSD drives are screwing the pooch when it comes to that latest and greatest big Windows 10 April up. You can read MS's verification of this information here.

Microsoft has temporarily paused the Windows 10 April 2010 Update (also known as R4) on select devices using the Intel SSD 600 series and Intel SSD Pro 6000p series due to issues that may cause a system to crash and enter a UEFI screen after reboot. To date, Intel is aware the block Microsoft implemented applies only to the Intel SSD 600 series and Intel SSD Pro 6000p series. Microsoft is working on a resolution that will allow the April 2018 update on these systems in the near future.
 
They cannot test every possible hardware scenario. Expecting them to is ridiculous. It's why they have a fast ring for beta, to catch MOST things, not all.

You guys need to settle down.

They especially can't test every possible hardware scenario when they fire most of their professional QA staff and make the public Nutella's QA department.
 
In all fairness to Microsoft on this one Intel did a lot of special things to make the 600 series hit the price points it did, the 600 was the first to use the SM2260 controller and those have been problematic for just about every product using them, pair that with Intels first attempt at what they called a "consumer-oriented firmware" and to meet Intels price/performance ratio they further customized the chips just for intel (which is why they have both the Intel and SMI branding on the controllers) and you have the perfect storm for something that is easy to break.
 
They especially can't test every possible hardware scenario when they fire most of their professional QA staff and make the public Nutella's QA department.
You do realize that it would require an entire army of people and several city blocks full of warehouses full of systems to test. This is not at all as easy as many people think.

I talked about it in another thread but I will copy and I paste it here.
With just how many hardware configurations that exist in the market this is quite literally impossible to do. If Microsoft were to do this they would have to have four to five city blocks filled with warehouses with multiple floors and an army of thousands people to test each update on. Why? Think about it. They would have to have each and every single hardware configuration that's imaginable.

Let's take one possible configuration here... take a system with a Gigabyte Z370 AORUS Ultra Gaming motherboard. Take the system and pair it with a Core i3, a Core i5, and a Core i7. Oh, but we're not done yet. Were they overclocked or were they running at stock configurations? We need identical systems with a Samsung SSD, a Toshiba SSD, a Sandisk SSD, a Plextor SSD, a Crucial SSD, and an Intel SSD, etc. Done yet? Nope. We need SATA and NVME versions of each SSD. Done yet? Nope. Now we need identical systems with RX 580s, RX 570s, RX 560s, AMD VEGAs, GTX1060s, GTX1070s, GTX1080s, GTX1080Ti's, etc. Done yet? Not by a long shot!!! What about different versions of various drivers? Especially different nVidia and AMD drivers for video cards. Now we need to repeat all of those possible configurations by replacing the Gigabyte Z370 AORUS Ultra Gaming motherboard with another motherboard and another motherboard and another motherboard and another motherboard and another motherboard and another motherboard and another motherboard.

Now you get to see just how impossible it can be to test on every single hardware and software configuration that the world has to offer. And this is just a snapshot of what's possible as far as hardware configurations. Oh, and now we get the fun job of duplicating all of those possible hardware permutations and run it with AVG, Avast, TrendMicro, Norton, etc. Oh shit, now the number of hardware and software configurations are numbering in the billions.

If Apple can't maintain perfect software quality with their limited hardware choices just how the hell do you think Microsoft can do it when they have to contend with everything from a cheap Dell being held together with duct tape and chewing gum to someone's elite gaming system?
 
You do realize that it would require an entire army of people and several city blocks full of warehouses full of systems to test. This is not at all as easy as many people think.

I talked about it in another thread but I will copy and I paste it here.

It's also not as difficult as you make it sound.

The point is that Microsoft formerly did have the QA staff it needs to produce quality and stable releases - but fired them when Naddy become Microsoft's CEO in a bid to cut Microsoft's costs by offloading QA onto the public - a move which has resulted in a major decline in release quality of Microsoft's OS updates.

So, it is indeed very likely that this SSD issue, along with many of the other issues related to this update and previous large MS updates wouldn't have occurred if Nadella hadn't shut down huge parts of Microsoft's QA departments for the sake of saving money by offloading Microsoft's QA work onto the public. That is because Microsoft's QA was formerly notably much better than it has been since.

https://www.linkedin.com/pulse/2014...hy-did-microsoft-lay-off-programmatic-testers
https://www.extremetech.com/computi...-its-sure-got-a-funny-definition-of-that-word
 
It's also not as difficult as you make it sound.

The point is that Microsoft formerly did have the QA staff it needs to produce quality and stable releases - but fired them when Naddy become Microsoft's CEO in a bid to cut Microsoft's costs by offloading QA onto the public - a move which has resulted in a major decline in release quality of Microsoft's OS updates.

Define quality, stable release. Because all non-trivial software has bugs, it's just a matter of finding them.

So, it is indeed very likely that this SSD issue, along with many of the other issues related to this update and previous large MS updates wouldn't have occurred if Nadella hadn't shut down huge parts of Microsoft's QA departments for the sake of saving money by offloading Microsoft's QA work onto the public.

So before Windows 10, no Windows release had any bugs or problematic updates?
 
So before Windows 10, no Windows release had any bugs or problematic updates?

You would be correct in saying that before Nadella moved Microsoft away from robust internal testing that Window updates featured much fewer overall issues as well as fewer serious issues.

No Service Pack broke as many things as the large bi-annual Win 10 updates do.
 
You would be correct in saying that before Nadella moved Microsoft away from robust internal testing that Window updates featured much fewer overall issues as well as fewer serious issues.

No Service Pack broke as many things as the large bi-annual Win 10 updates do.

Incorrect. It might be before your time, but I can think of two examples.

Windows ME. The entire thing was garbage. It was released after, we have to assume, the same internal QA department that worked on Windows 2000 and Windows 98SE said it was ready for primetime. It wasn't.

Windows XP SP1. I worked Windows XP tech support right around the release of this SP. It was insane the amount of systems that went down because of it. Usually requiring full reinstallation.
 
You would be correct in saying that before Nadella moved Microsoft away from robust internal testing that Window updates featured much fewer overall issues as well as fewer serious issues.

No Service Pack broke as many things as the large bi-annual Win 10 updates do.

That article you posted shows NOTHING about a Q&A staff being fired. Amazing, people must have this all or nothing mind set because, as you know, if it does not go 0 t0 60 in 5 seconds, it MUST be slow. :rolleyes:
 
You would be correct in saying that before Nadella moved Microsoft away from robust internal testing that Window updates featured much fewer overall issues as well as fewer serious issues.

No Service Pack broke as many things as the large bi-annual Win 10 updates do.

And where are getting this information? Service Packs caused plenty of issues. XP SP2 with the changes in security caused a number of problems. And how many machines out there might start up, but never got OS updates but plenty of malware installed?

With the number and diversity of devices installed, no ones personal experience no matter what that is even begins to cover it. All I want to see if real data on failure rates.
 
Incorrect. It might be before your time, but I can think of two examples.

Windows ME. The entire thing was garbage. It was released after, we have to assume, the same internal QA department that worked on Windows 2000 and Windows 98SE said it was ready for primetime. It wasn't.

Windows XP SP1. I worked Windows XP tech support right around the release of this SP. It was insane the amount of systems that went down because of it. Usually requiring full reinstallation.

There clearly have been problematic and unpopular Windows releases before Windows 10. Windows ME was one of them. In terms of hardware issues, Windows Vista? That QA department that should have been fired then.
 
That article you posted shows NOTHING about a Q&A staff being fired. Amazing, people must have this all or nothing mind set because, as you know, if it does not go 0 t0 60 in 5 seconds, it MUST be slow. :rolleyes:

If Microsoft only had more QA personnel to handle every iffy piece of hardware out there. Because well, gee, Intel. Why didn't Microsoft's QA department catch Meltdown? For that matter why didn't anyone's QA department catch it before TEN YEARS went by?
 
Incorrect. It might be before your time, but I can think of two examples.

Windows ME. The entire thing was garbage. It was released after, we have to assume, the same internal QA department that worked on Windows 2000 and Windows 98SE said it was ready for primetime. It wasn't.

Windows XP SP1. I worked Windows XP tech support right around the release of this SP. It was insane the amount of systems that went down because of it. Usually requiring full reinstallation.

Been using Windows since 3.1. Windows ME isn't a service pack.


That article you posted shows NOTHING about a Q&A staff being fired. Amazing, people must have this all or nothing mind set because, as you know, if it does not go 0 t0 60 in 5 seconds, it MUST be slow. :rolleyes:

Actually, the first link tries to explain WHY (according to Microsoft) Microsoft laid off its OS testers. Are you really unaware that Microsoft's massively slashed its number of testers? You and heatlesssun, both? That's pretty remarkable.

http://www.businessinsider.com/huge-layoff-for-microsoft-employees-too-2014-7
http://www.businessinsider.com/about-700-microsoft-employees-to-be-laid-off-sources-say-2017-1
https://www.cnbc.com/2017/07/06/microsoft-will-layoff-thousands-of-employees.html
https://www.geekwire.com/2018/microsoft-makes-new-round-layoffs-across-multiple-business-units/

Between 2014 and 2017, I think Microsoft fired over 20,000 of its staff - many of them were testing engineers, and many were from the Windows OS testing branch of the company.


Also, in the first link in the post you made your comment in response to, a quote from Microsoft literally states that Microsoft was laying off its in-house testers to shift bug-testing onto the public:

"QA still exists and is still important, but it performs end-user style "real world" testing, not programmatic automated testing. This testing has been successful for Bing, improving the team's ability to ship changes without harming overall software quality".


And where are getting this information? Service Packs caused plenty of issues. XP SP2 with the changes in security caused a number of problems. And how many machines out there might start up, but never got OS updates but plenty of malware installed?

With the number and diversity of devices installed, no ones personal experience no matter what that is even begins to cover it. All I want to see if real data on failure rates.

I didn't say that service packs didn't cause issues. I said they didn't cause as many as each major Windows 10 update. Windows 10's bi-annual major updates are 'gonna have to reinstall Windows 10' time for many people.


There clearly have been problematic and unpopular Windows releases before Windows 10. Windows ME was one of them. In terms of hardware issues, Windows Vista? That QA department that should have been fired then.

Vista didn't have anywhere near the number of bugs that Windows 10 has had since its launch. Vista's biggest issues were related to people not having good enough hardware, and 3rd-party drivers not being included with the OS, combined with a much more tech-illiterate society than there is today.



There's way too much disingenuous and history-revising spin and deflection is coming from a Microsoft Defence Force, here.
 
Last edited:
I didn't say that service packs didn't cause issues. I said they didn't cause as many as each major Windows 10 update.

XP SP2 did though is was a great release to help address security concerns.

Vista didn't have anywhere near the number of bugs Windows 10 had since its launch.
​

Personally that wasn't my experience. And Windows 10 is getting enterprise adoption. Vista never did.
​

​
There's way too much disingenuous and history-revising spin and deflection is coming from a Microsoft Defence Force, here.

Personally I'm not having higher rates of these kinds of issues with 10 than any other Windows OS. Sure there are bugs, I see them all of the time, but not wrecking hardware. And personally I just don't know how to frame it. I'm using stuff that just doesn't work or as well under older Windows versions. One bug that I've mentioned for a while here is the issue with Netflix 4k with the Windows 10 app in full screen. Which is working now. That doesn't even work in older versions of Windows.

This a FAR more complex issue needing WAY more data than you say.
 
Been using Windows since 3.1. Windows ME isn't a service pack.




Actually, the first link tries to explain WHY (according to Microsoft) Microsoft laid off its OS testers. Are you really unaware that Microsoft's massively slashed its number of testers? You and heatlesssun, both? That's pretty remarkable.

http://www.businessinsider.com/huge-layoff-for-microsoft-employees-too-2014-7
http://www.businessinsider.com/about-700-microsoft-employees-to-be-laid-off-sources-say-2017-1
https://www.cnbc.com/2017/07/06/microsoft-will-layoff-thousands-of-employees.html
https://www.geekwire.com/2018/microsoft-makes-new-round-layoffs-across-multiple-business-units/

Between 2014 and 2017, I think Microsoft fired over 20,000 of its staff - many of them were testing engineers, and many were from the Windows OS testing branch of the company.


I didn't say that service packs didn't cause issues. I said they didn't cause as many as each major Windows 10 update. Windows 10's bi-annual major updates are 'gonna have to reinstall Windows 10' time for many people.




Vista didn't have anywhere near the number of bugs that Windows 10 has had since its launch. Vista's biggest issues were related to people not having good enough hardware, and 3rd-party drivers not being included with the OS, combined with a much more tech-illiterate society than there is today.



There's way too much disingenuous and history-revising spin and deflection is coming from a Microsoft Defence Force, here.



I read both of your linked articles and neither one indicates that the Q&A department was cut. In fact, one of the articles pointed out that they are hiring people too.
​


Ah, I see, so we are now moving into name calling territory?
 
This entire thread is all opinion based, as far as the "bugginess level" of service packs.
 
This entire thread is all opinion based, as far as the "bugginess level" of service packs.

One thing I found is that until very recently, the System Readiness update tool never really fixed anything. Seems a repair install of Windows 7 was needed more often than not, when you did not want to redo everything from scratch, anyways.
 
me being me, did MSFT know the "uproar" that win 8-8.1-10 would/did cause so they pre emananted cutting staff because the revenue would not allow keeping nearly the same substantial staff numbers....if they did not preminate exactly this happening, then it probably was a good thing that "dude" cut the fat before they did what they did cause likely the mass residual in the bank account would have drained very rapidly.

cause they sure have seemed to really focus on trying to get rid of the "free" 3rd party stuff with more focus on pay to play type software in the last year or so (at least from all I have read)

probably could explain why they switched over to the large update "packs" so there is less service staff to keep the servers "fluid" as they might have once been.

Cause I know (at least for myself) it seemed right around the time of win 8.1 release and going to Win 10 the "update servers" really went downhill as far as double checking what updates one had as well as what updates once politely told "fk off hide this crud" LOL

Am sure there is no "easy way" for them to have done things, but, really wish they did not do the forced update crud, while can understand the "why" kind of, do not agree with the "it is a good thing" mentality they seem to be pedaling.
 
This entire thread is all opinion based, as far as the "bugginess level" of service packs.

Exactly. We're talking about hundreds of millions of devices. There's NO WAY to make a fair and unbiased assessment of this because no one here has the data to do so. I'm perfectly willing to concede that anti-Windows 10 folks are correct, but where's the data to confirm?
 
cause they sure have seemed to really focus on trying to get rid of the "free" 3rd party stuff with more focus on pay to play type software in the last year or so (at least from all I have read)

This makes no sense. Hell even the Microsoft Store houses free open source software. All of the open source stuff that Linux folks like to promote like Libre Office, runs perfectly on 10, even side by side with Microsoft Office.
 
There clearly have been problematic and unpopular Windows releases before Windows 10. Windows ME was one of them. In terms of hardware issues, Windows Vista? That QA department that should have been fired then.

The hardware "problems" with Vista wasn't really Microsoft's fault for the most part. The biggest problem was that the hardware mfgs drug their feet in relation to drivers for Vista and a lot of the drivers that were available for Vista early on were very buggy.

The biggest problem with Vista was that OEMs were selling very underpowered for Vista systems with Vista on them. That was not Microsoft's fault at all. Just because the technical system requirements are low doesn't mean that a program or an OS will run well on a system that technically meets the requirements for it to run.
 
The biggest problem was that the hardware mfgs drug their feet in relation to drivers for Vista and a lot of the drivers that were available for Vista early on were very buggy.

Not saying this isn't true but in all my years of using Windows, the problems with Vista, regardless of whose was at fault, were clear. How many systems were borked going from XP to Vista? How many complaints were there on that upgrade process? I didn't hate Vista, I ran it full time personally from day one, but remember the outrage over UAC?
 
It gets even better. I had someone come in with a new Acer laptop. Has a combo Intel 630 and Nvidia graphics. While looking for a cause for the issue it was supposed to have I saw that the video drivers hadn't updated since late last year. I figured I'd search up the drivers. While being lazy and Googling the model number for a link to the ACER support page I found a forum link where people were complaining the 1803 update was crashing the video completely on these ACER laptops with Intel 630. Even more annoying, the generic Intel drivers won't load without using the zip file and manually forcing the install because Acer doesn't use the default hardware ID and they havn't released an official fix.

So that's yet another common Intel piece of hardware drivers that doesn't survive the new update without a serious work around that the average user can't handle.

Hmmm.... I also noticed that the 1803 update wasn't immediately popping up when I forced a Windows Update check. Wonder if that model laptop is also on the no-update list for the time being?
 
Considering this little piece written by Anandtech...
Anandtech said:
It is not yet clear what is causing the incompatibility between the Intel 600p and Windows 10 version 1803, but the most likely culprit is a bug in the 600p's controller firmware. Intel has issued two firmware updates for the 600p family, each fixing several bugs including some that had the potential to cause data loss or corruption. The most common theme in the release notes for 600p firmware updates seems to be power management troubles, but those are unlikely to prevent Windows 10 v1803 from even installing to the 600p.
I would be very confident in this SSD.

Source: https://www.anandtech.com/show/12742/latest-windows-10-version-incompatible-with-intel-ssd-600p
 
because Acer doesn't use the default hardware ID and they havn't released an official fix.
I can't blame Microsoft there, I put the blame squarely on Acer's shoulders here. Once again the OEMs have shown that they mess with shit that they have no damn business messing with.
 
Back
Top