Windows 10: Update 1903 Killed NVMe

I have always been against updating windows for obvious reasons. Google windows 10 killed computer and you will find many.


Update 1903 was forced on my computer, which killed my main storage ($90 EX920 500GB M.2 NVMe), is there any way to hold Microsoft accountable without opening a lawsuit?


If not, how many would be interested in opening yet another class action lawsuit as done in earlier years?

:)

 

Windows 10 installer don't detect NVMe drive

I have 2 drives:

• disk1 (SATA SSD, with Ubuntu 16.04)
  • partition1 (sda1: flag /boot)
  • partition2 (sda2: flag /home, encrypted by LUKS)
• disk2 (NVMe SSD)

So, the goal is to install Windows 10 on disk2 and boot it from GRUB (which is on sda1).

What is the problem ?

In disk-choose step, disk2 is missing. However Ubuntu 14.04 installer "see" this disk, so I assume that is software issue, rather than my hardware.

What I tried to solve this problem ?

• loaded Samsung NVMe drivers from this thread
• patched Windows image using DISM tool by adding 2 updates. I followed this guide
• tried to run Windows 10 installed on USB stick to install it

All of them failed.

Please help me to solve this issue.

 

Windows 10 1903 update - resulting problems

Hi Vijay,

Thank you for the rapid response.

Your suggested actions are very technical - hardly for 'the man in the street'

'

If I understand correctly, in simple terms, you are suggesting changing the path/method of obtaining the 1903 update but still installing it anyway -

Surely if the problem is actually with the 1903 update then the result will be the same problems irrespective of how it is applied?

Please could you clarify in simple terms, step by step, what your suggested actions actually do and how this may solve the problem.

Thanks,

Mike Longley.

 

Local profile issue after upgrading to 1903


Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken