I just backed out of the new update (ver. 1803 - build 17134.1). It does not recognize my external USB Blu-Ray drive. Can't use it for anything, movies, music, etc.

---

I don't buy computers, I build them!!

I just backed out of the new update (ver. 1803 - build 17134.1). It does not recognize my external USB Blu-Ray drive. Can't use it for anything, movies, music, etc.

Did MS nuke its driver? Might be worth a refresh. Just a thought.

---

I just backed out of the new update (ver. 1803 - build 17134.1). It does not recognize my external USB Blu-Ray drive. Can't use it for anything, movies, music, etc.

Did MS nuke its driver? Might be worth a refresh. Just a thought.

I think it did. Upon the restore back to the previous version, the device was recognized and is working perfectly.

---

I don't buy computers, I build them!!

I just backed out of the new update (ver. 1803 - build 17134.1). It does not recognize my external USB Blu-Ray drive. Can't use it for anything, movies, music, etc.

I have an internal ASUS Blu-Ray drive, have updated and no problems with drive.

---

Kevin

A person at the pub yesterday was quite interested in my old ex-Vista Celeron lappy and was very surprised on how well it performed with Linux Mint when I told them that their Win10 lappy has 6 times the performance than it, so another Win10 to Linux Mint conversion will happen here over the weekend some time.

Cheers.

ver. 1803 - build 17134.1 just done the dirty on me:-(

I had nvida 397.31 running and it reinstalled one of the useless crappy windows video drivers.

am now reinstalling proper drivers.

---

Kevin

ver. 1803 - build 17134.1 just done the dirty on me:-(

I had nvida 397.31 running and it reinstalled one of the useless crappy windows video drivers.

am now reinstalling proper drivers.

Still having problems.

Have re-installed drivers several times.

Have now set NNT for Seti.

Have lost SoG and cannot seem to get it back - switched back to cuda 50 on GPU's, Trying to run SoG just gets Seti GPU tasks posponed.

Going to work now, Will try again in early morning.

---

Kevin

Wanted that Windows 10 update but have an Intel SSD? Computer says no

The Windows 10 April 2018 Update is not proving to be the smoothest of installations for PCs containing certain Intel SSDs.

Systems with Intel 600p and Pro 6000p SSDs are experiencing crashes and users are finding themselves staring at a UEFI screen after rebooting. Microsoft has recommended afflicted users reinstall the previous version of Windows 10, 1709 (aka the Fall Creators Update). Redmond is also attempting to block the devices trying the update again.

The issue is an unspecified "known incompatibility" between the operating system and the SSDs, which were launched in 2016. Both the 600p and Pro 6000p SSDs share the same SM2260 chipset and feature a PCIe NVMe 3.0 x4 interface.

---

Greetings,

Something is NOT making any sense to me...

Does Micro$oft write drivers and send them to manufacturers for distribution? Here's why I ask:

I went into Device Manager to check my M.2 SSD driver yesterday. The M.2 is a Samsung 960 EVO 250GB running PCI-E 3 x4. I downloaded the driver FROM Samsung and installed it after building this PC. Device Manager says the driver is provided by Micro$oft. I went back to Samsung and found they had a newer driver so I downloaded it and installed it. I went back into Device Manager and lo and behold it reported the driver is again provided by Micro$oft. If I get it FROM Samsung, it should tell me the driver is PROVIDED BY Samsung.

Is Micro$oft THAT arrogant that they think they are better at drivers than the manufacturers are? Right!!! Just look at the crap that happens when they change our video drivers when Windows 10 is "automatically updated". It just happened to me a couple days ago.

Micro$oft, give me back MY full control of MY PC!

If anyone has a logical explanation for this, please tell me. :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If anyone has a logical explanation for this, please tell me. :)

Are you looking in the right place?

From the Driver Installation Guide.

3. Confirming the installed driver
If you initiate the Windows Device Manager, a list of all the hardware present in your system is
shown. If “Samsung NVMe Controller” is shown below the “Storage controllers” as below, the
installation is successful.

---

Grant
Darwin NT

If anyone has a logical explanation for this, please tell me. :)

Are you looking in the right place?

From the Driver Installation Guide.

3. Confirming the installed driver
If you initiate the Windows Device Manager, a list of all the hardware present in your system is
shown. If “Samsung NVMe Controller” is shown below the “Storage controllers” as below, the
installation is successful.

Hi Grant,

Hmmm...

Ok, I had no idea I actually had to read instructions on "how to install a driver". ;) Probably shoulda huh? :)

(1) I did not install with administrator rights. (2) I didn't look in Storage Devices for the driver, I looked under Disk Drives.

The driver shows under Storage Devices and shows as provided by Samsung. The Microsoft Storage Spaces Controller driver is the same as that shown for my M.2 drive and my Western Digital HDD, same version number, under Disk Drives.

I will use the Samsung installer (with admin rights) to uninstall and re-install the driver to see what I get this time. What I see presently under Disk Drives is that the Microsoft controller is controlling my M.2 drive and not the Samsung controller. Hey, I could be completely spaced out on what I am seeing. Perhaps it is correct. Anyway, I'll report back what I find out.

Thanks Grant! :)

Siran

[edit] Here's what I have:



It just doesn't seem correct to me. The first 3 images are showing the version number of the Microsoft controller. The second image from the left, in my mind and opinion, should be the same as the Samsung controller version. What gives?

Siran
[/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I had problems getting the Samsung installer to work and update to the latest NVME driver on this rig under Win 7.
I finally found the actual NVME driver .inf files without the Samsung .exe installer and was able to update the driver in device manager without the dang Samsung program.
Here is a link to the drivers page, scroll down to the Samsung one.

---

"Time is simply the mechanism that keeps everything from happening all at once."

The Windows 10 April 2018 Update is not proving to be the smoothest of installations for PCs containing certain Intel SSDs.

I got the huge April update (last time I checked it was May Microsoft ...) the other day and had a serious issue. I have a Samsung SSD and after the update the notification area warned that my disk had errors and had to be scanned. Then I got a message that my Microsoft login credentials had some sort of issue I needed to fix too. I restarted the machine and the problems began. The blue screen claimed there was an error that had to be fixed and started the Windoze repair system - - - but it couldn't fix the problem!

Then I went through that several times and got into an "Advanced" settings area that asked me if I wanted to recover the system to a checkpoint yesterday. I had no options left (but I did have a cloned image from several days ago I did with a separate package). The recovery system then failed. But I restarted the system and I got back into Windoze!

I have no idea WTF happened but it all seems OK as of today.

---

I'm putting myself to the fullest possible use, which is all, I think, that any conscious entity can ever hope to do.

The "Storage Space Controller" is an interface between the hardware driver and the rest of the system. Essentially it provides a standard API for communication to and from the disk.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

The "Storage Space Controller" is an interface between the hardware driver and the rest of the system. Essentially it provides a standard API for communication to and from the disk.

Hi Rob,

I understand what the controller does. A dumb analogy would be the shifter in a car being the "controller" between you the driver and the transmission shifting. Sort of, told you it was dumb. ;)

Please see my edit, with image, on my post below.

Siran

[edit1]
I just made an observation that is just WRONG! Look at the driver date for the Microsoft controller. Isn't that before Windows 7? Or at the very least about when Windows 7 went public? 2006????????????? Give me a break!!!
[/edit1]

[edit2]
I just look at several devices, upwards of about 10 with Microsoft drivers, and they ALL have the same driver date, 2006!!! What gives?
[/edit2]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

...not all of Windows 10 is as new as one would imagine or desire

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

...not all of Windows 10 is as new as one would imagine or desire

I guess Micro$oft goes by the old axiom: "If it ain't broke, don't fix it."

Either that, or they update the drivers without updating the driver date for whatever reason.

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Micro$oft, give me back MY full control of MY PC!

You have been assimilated, resistance is futile. Comply.

---

Micro$oft, give me back MY full control of MY PC!

You have been assimilated, resistance is futile. Comply.

LOL!!!

Funny you should say that. I said something very similar just the other day.

"We are the BORG, you will be assimilated; resistance is futile. Your biological and technological distinctiveness will be added to our own."

I believe I said it about how the OS says "WE" will do this or "WE" will change that for you...

Our individuality has been taken away from us. I renamed the icon "This PC" to "Rick's PC" and the icon for "Recycle Bin" to "Garbage Dump". At least I restored that iota of individuality. ;)

Siran

[edit] corrected a spelling error [/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

It just doesn't seem correct to me. The first 3 images are showing the version number of the Microsoft controller. The second image from the left, in my mind and opinion, should be the same as the Samsung controller version. What gives?

It is correct.
Keep in mind that a NVMe SSD is actually a drive, with a controller built in. The controller interfaces between the drive itself, and the PCIe interface. So the NVMe driver will show up in the Storage Controller section.
The actual movement of data between the drive & the controller is pretty low level and the standard Windows drivers are all that is needed, so for the drive itself, it will use those basic standard drivers, and that is what you see in Device Manager for the drive properties.

As for the date of Microsoft drivers, it is intentional. It's so 3rd party drivers don't get replaced by Microsoft ones.
From a Microsoft blog,

When the system looks for a driver to use for a particular piece of hardware, it ranks them according to various criteria. If a driver provides a perfect match to the hardware ID, then it becomes a top candidate. And if more than one driver provides a perfect match, then the one with the most recent timestamp is chosen. If there is still a tie, then the one with the highest file version number is chosen.

Suppose that the timestamp on the driver matched the build release date. And suppose you had a custom driver provided by the manufacturer. When you installed a new build, the driver provided by Windows will have a newer timestamp than the one provided by the manufacturer. Result: When you install a new build, all your manufacturer-provided drivers get replaced by the Windows drivers. Oops.

Intentionally backdating the drivers avoids this problem.

---

Grant
Darwin NT