LOL, that is still a SATA based SSD using a VERY mature AHCI drivers.. Just because it has a M.2 connector does not mean it is new technology. User cbutters is using a TRUE PCIe based SSD, no SATA on his SSD to be found anywhere in its spec.
No, it isn't, it's simply a fault of the Driver Developer and that's the Hardware Manufacturer! Period!! Unfortunately, many users just like to bash Microsoft for anything include what isn't done by Microsoft! Objectivity is something what this User's will never understand!
Yeah, now that is my kind of SSD. Lol, I can't wait until I get my first NVMe based SSD. Not sure which one I want though, or if I'm going to wait a little bit longer. The Samsung SM951 looks REALLY good to me, but with my older machine I think I want to wait until I build a newer PC. Currently only running a Xeon Hexa core on a old Rampage III Intel x58 machine. Its fast but really dated. My system has 6 cores 12 threads at 4ghz, but like I said its getting very dated already (for my standards anyway). I want a new system, but I think I am going to wait until 2016's release of Skylake hardware. Then my raided sata drives will be replaced by single NVMe drives. lol, well at least the boot drive will. I currently do not trust Windows built in NVMe drivers as of yet, but I wouldn't mind trying it, hehe
OK....Kinda weird. Couldn't get the Start Menu to work at all yesterday, and today it seems to be fine. I'm wondering if the problems I'm running into are related to Win 10 or the VMWare Workstation I'm running under. Guess I'll have to check it out. Cheers.....
Huh? if the driver developer ( hardware manufacture) always release new updates but M$ still using driver from 2006 for 2015 system why i should blame the driver developer?! that makes no sense
i don't know when you do it but i have no problem with this build 10130, for my run perfectly and i have question this one is last build before RTM or new build coming ( official not leak)
I installed this build on a laptop and it seemed to install fine ie. I got to see the choose which OS to boot screen (7 & 10). I chose to load Windows 7 first to check if everything's alright over there and after restarting to let 10's setup continue, the laptop won't boot at all! It stays at the spinning ring and skips the boot choice menu. I tried going back to 10's installer and saw that my C: (Win7) now has only 5GB free and attempts to reinstall 10 to the partition I had chosen for it only give a "locked" error. What should I do to get at the very least my Windows 7 installation to boot? It would be nice to have Win10 to test on a real machine instead of a buggy VM but 7 takes priority.
So?! And have you ever think about that Microsoft need's to get permission to add such drivers to their OS'es? And what MS could do if they didn't give that permission? Just use those driver Ms has permission to use! Mister, get real! If MS could add a better driver (if some exist) I hardly believe they wouldn't! Nobody, include Microsoft would be that stupid NOT to use the better drivers! But, it's a question of legality for Microsoft too!
Testing this build has been going quite well so far, until I realized that... SD cards are not working, not showing volumes External USB 3.0 hard drive not working, not showing volumes Sony HD video camera (built in SSD) not working, not showing volumes USB sticks (USB 2.0 and 3.0) not working, not showing volumes All of these have worked effortlessly with all previous builds since the beginning of my Insider testing. Each of these different, unique devices are all referring to the same Roxio Saib driver even though they are different devices. I've never heard of this driver before and not sure why this build is trying to use this same driver for all devices. Windows Update itself is trying to install this driver as well, but is failing with Roxio - Other hardware - Roxio Saib - Error 0x800f0219 and the finer details are showing the failure having something to do with Windows 10 trying to install Windows 95 device drivers. I have to admit that I am completely stumped here. Anyone else come across this issue in build 10130 to do with Roxio Saib and storage devices? Any workaround or ideas? Thank you. EDIT: Can anyone confirm if this issue is fixed in the leaked builds 10134 or 10135?