Rollout of Windows 10 April Update Halted For Devices With Intel and Toshiba SSDs (bleepingcomputer.com)
Catalin Cimpanu, writing for BleepingComputer: Microsoft has halted the deployment of the Windows 10 April 2018 Update for computers using certain types of Intel and Toshiba solid state drives (SSDs). The Redmond-based OS maker took this decision following multiple user reports about the Windows 10 April 2018 Update not working properly on devices using: Intel SSD 600p Series, Intel SSD Pro 6000p Series, Toshiba XG4 Series, Toshiba XG5 Series, and Toshiba BG3 Series.
The Intel and Toshiba issues appear to be different. More specifically, Windows PCs using Intel SSDs would often crash and enter a UEFI screen after reboot, while users of Toshiba SSDs reported lower battery life and SSD drives becoming very hot.
The Intel and Toshiba issues appear to be different. More specifically, Windows PCs using Intel SSDs would often crash and enter a UEFI screen after reboot, while users of Toshiba SSDs reported lower battery life and SSD drives becoming very hot.
Really?
I would have thought old school hard drives would be incompatible.
Looks like the Windows 10 1803 update also prevents the Intel HD graphics driver from changing the screen brightness. Again, don't they have people check things like that before they release the update?
If MicroSoft and the hardware vendors stuck to device interface standards as written instead of relying on sketchy un-documented features to keep the competition locked out, things like this wouldn't be a problem.
To focus on bugs.They would rather work on Bubble Witch Saga than test SSDs.
Windows fanboys keep telling me that Windows runs on EVERYTHING because Microsoft has drivers for everything, and it's shitty Linux that breaks on computers that aren't 20 years old. Were they lying?
After being nagged a LOT and worrying about MS wiping out a current session i been working on for a while I bit the bullet and installed the durn thing.
Now I'm sitting here wondering if it's gonna screw up due to my SSD.
Caution: Contents under pressure
more poof.
I love the vagueness of the messages ;-)
After the April update, I noticed a temperature spike of roughly 20 degrees celcius being reported from somewhere on my motherboard. Problem is there doesn't seem to be proper documentation on where that particular sensor resides on my motherboard. Now I'm wondering if it's near my SSD.
I love the vagueness of the messages ;-)
It's not like Microsoft knows.
dont worry, we may brick your desktop.
if your backing up to azure your data is safe -- despite your lost time and productivity.
I understand that these are complicated systems but I've had it with the increasing frequency of these mandatory updates causing major IT issues and downtime.
Yes I know there are obscure tools and registry changes that can somewhat mitigate that. I shouldn't have to.
All my mission critical windows systems are now quarantined from the internet and other networks because they are bandwidth hogging security risks with secret backdoors. As soon as I implemented that the performance and stability of my windows computers increased massively.
When I know a major update is due, I make images of both machines' boot drives. I have only used such an image once, out of desperation over some strange issues I was having -- and it didn't fix them, they turned out to be due to buggy drivers that had been updated prior to my disk imaging. (So the fix was exactly the same whether Windows was updated or not.) This isn't the only time or reason for making boot drive images, of course, but it seems to me that right before a potentially disastrous procedure like a major update is a good time to be making backups. I certainly worry less about correcting brokenness after an update when I have drive images in hand. (Finding brokenness can be the hard part. Just because I use a software package infrequently, that doesn't mean it's not damn critical when I do use it.)
Imaging a half-full 250 GB SSD doesn't take that long if it's to a local drive. Pushing the image to the NAS box is another matter entirely, especially if it's by WiFi. Using a fast(ish) flash drive is somewhere in between. I have spinning rust in the desktop as well as an SSD, so that's where the images go. (They are then duplicated onto the NAS box when the machine has nothing better to do.) The Chromebook gets backed up to flash drive, then the flash drive gets transferred to the desktop for duplication to the NAS box, to take full advantage of GigE.
How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
Who the bleep is a Insider these days that this sort muck up slipped through to a release??? Its full of bugs and worthless features that were not worth it. There is no such thing anymore as a stable release with Windows 10. Why even bother with Insider's if this sort of crap still exist in a release to public? Heck were all forced beta testers anyway its seems, right?
The install failed on my Windows 10 N machine, too. Why? Because I'd installed MS Windows Media Player (yes, yes, I know).
The solution involved using optionalfeatures.exe to remove the entire Media Features option. Restart. Then from an admin shell:
Net stop wuauserv
Net stop cryptSvc
Net stop bits
Net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
Net start wuauserv
Net start cryptSvc
Net start bits
Net start msiserver
The standard Windows Update wasn't happy so it was necessary to use the Update Assistant: https://www.microsoft.com/en-us/software-download/windows10
Finally, re-install the Media Features: https://www.microsoft.com/en-us/download/details.aspx?id=48231
Putting this here to save others the 6 hours of repeated rollbacks and research.
This update took it upon itself to create a new recovery partition, which then complains it's full. I eventually fixed it, but it seems like there wasn't very much QA involved in this update.
https://borncity.com/win/2018/05/02/windows-10-v1803-update-creates-a-new-oem-partition/
I keep picturing time cards from Spongebob Squarepants.
"3 hours later"
I thought upgrades were meant to improve the os? Did ms make a policy change since releasing Windows 10 I'm unaware of?
Oh right... They didn't bother to do that.
Once again I'm wondering how the heck small businesses owners deal with these problems.
Film at 11.
Escher was the first MC and Giger invented the HR department.
Intels days of being king and we don't give a dam are over. zen 2 epyc will destroy the data center market for intel.
Microsoft ASSUMES that you have these drives installed at the time of the update and that you are not using them as external backups. BAD THINKING, as I for one use SSD drives for back ups. I guess since I only boot of these in the event of an emergency, such as replacing my main drive that I'll just be Gated in my corn hole.
When win10 auto-updates:
- I used to think "oh shit, I'm screwed".
- Now I think "fsck it, I'll deal with the fallout on monday - I'm headed home for an early weekend".
" More specifically, Windows PCs using Intel SSDs would often crash and enter a UEFI screen after reboot" ... every few days/each week
Exactly what my new Win 7 box does. It seems to have trashed both Samsung SSDs I have tried somehow.
If you want someone to work with you there needs to be some accommodation, but with Linux there is no accommodation, only submitting to the dictates of the GPL.
OK, what if a developer signed an NDA and wrote a driver under a different license?
If you want it portable you still have to release the source, even if it is obfuscated.
Uncommented C-code is about as readable as a binary blob ran through a decompiler so if that is a violation of the NDA we are back to the vendor being the problem.
Also, the GPL clause about "suitable for editing" is a bit vague.
Historically I've had it easier editing binary blobs with a hex editor than I've had when trying to make something out of perl sources.
I like the way that they give you a little frowny face when Windows crashes :-(. It's about time that MS outsourced manufacture of all hardware to Mattel. Then the entire ecosystem would at least be correctly represented.
The incompetence Microsoft is showing at the moment really knows no bounds. It is one thing to offload your quality control to an insider program of free labour but then it's quite another to not to actually listen to any of the responses.
The problem that affected the Spring Creator's Update which caused it to be pulled in the last minute was identified in 4 separate reports months earlier by the insiders. After fixing it the insider release was so short basically any new bugs were unable to be reported.
And now this. A problem that affects a large group of SSDs including the 2017 Surface Pro. Microsoft's premier hardware product.
It's one thing to offload widespread testing onto customers. It's quite another to screw up your most premium of products. This is no longer lack of quality control, this is sheer and utter incompetence.
If your Samsung is 840 or later, you can get its own measure of temperature out of SMART attribute "190 Airflow_Temperature_Cel".
(I just don't know how to do this in Windows 10. I mostly use Linux and smartmontools.
Maybe Samsung's Wizard tools can do it ? Maybe SpeedFan ? Have a look here.)
On Samsung 830, I haven't seen such an attribute.
If that unknown sensors is nearby the SSD, it and the SSD's sensor should evolve similarly over time (spike at roughly the same time, with more or less similar top temperatures)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
All my mission critical windows systems are now quarantined from the internet and other networks
Which by itself is a good approach as it drastically decrease *nearly all* security and safety risk for mission critical equipement.
(Basically only a few very advanced threats geared toward air gapped targets as stuxnet)
No mater the insanity of Windows 10 updates.
The next step would be to enclose them inside VMs and use a slightly saner host OS (something unix-y, e.g.: Linux) to handle the VMs.
Including snapshotting for safe roll back (which among other could help mitigate the buggy updates)
While of course still keeping them network isolated (they are mission critical after all).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Looks like the Windows 10 1803 update also prevents the Intel HD graphics driver from changing the screen brightness.
This has been the case since back when Windows 8 came around for me. Every Windows update that messes with the graphics on my ASUS N56dp laptop (AMD trinity APU) breaks the screen brightness. Fortunately, it can be fixed by re-installing the manufacturer's graphics drivers, and/or a registry edit.
If you want someone to work with you there needs to be some accommodation, but with Linux there is no accommodation, only submitting to the dictates of the GPL.
OK, what if a developer signed an NDA and wrote a driver under a different license?
That has happened and users of those hardware devices have had Linux support via a closed binary. Such binaries are sometimes not installed by default due to ideological purity but some distributions have a simple question during install to allow such binaries. And users approving them get working hardware under Linux.