![windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0)](http://www.cgl.ucsf.edu/chimera/graphics/images/vista_adapter.png)
- #Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) drivers
- #Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) upgrade
- #Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) windows 10
- #Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) android
Note: Surface Go released with the Windows 10 April 2018 Update, version 1803.
#Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) drivers
On October 9th we made available the initial release of drivers and firmware for Surface Go from the Microsoft Download Center.
![windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0)](https://c1.neweggimages.com/ProductImageCompressAll1280/20-250-097-V04.jpg)
#Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) android
![windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0)](https://cdn.cnetcontent.com/syndication/feeds/wd/inline-content/06/7864A66E2FCCFA3B28DEC477A561D13C4D6C329C_DATASHEETWDBLACKNVMESSD2879810008_doctn.png)
![windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0)](https://c1.neweggimages.com/ProductImageCompressAll300/AM3KS200618gnwbF.jpg)
#Windows 10.0.14393 (standard nvm express controller driver v10.0.14393.0) upgrade
I did not try to downgrade the chipset drivers using the official lenovo drivers 10.1.1.27 (N1FID01W), but I'll do so after my next upgrade should that show the symptoms again. The three failing attempts correspond to the three "extra" nvme controllers/disks I'm seeing in the device manager after the boot: / (sorry, no screenshot yet of the "4" NVME controllers).ītw: the v10.1.1.33 chipset driver in 15007 claims to support both Skylake as well as Kaby Lake (7th gen) chipsets, whereas the v10.1.1.27 in my working 14986 build only sports Skylake (6th gen) support. this happens very early, close after kernel-boot: only after the third reset the drive is actually usable and boot continues. When I upgraded to the 1500x builds (14986 -> 1506 -> 15007), restarts during upgrade did work eventually, but each shutdown & startup would take ~3min each. according to the eventlog after the upgrade (excerpt attached here along with the devicemap registry tree, maybe this helps your storage team?), the nvme controller times out and forces a reset three times. the machine kept running in a defunct state (screen/keyboard off, fan & power on), requiring a powerbutton-long-press reset. Thanks for the feedback! at the very least it sounds related: in both 1507 the shutdown after the successful upgrade would not work at all, i.e.