Yeah the 960 problem is a UEFI/boot issue, happens much earlier than the "start button" ;-]
Have you tried the "semi-reset" under Windows Defender? It saves your user data (but make a BACKUP FIRST, just-in-case), and resets "some" of the apps, you only really have to re-install the non-store apps, and then do some config. I have a pretty complex dev machine at home, and it took me maybe 2-3 hours to "recover", fully, after one of these, well-worth it, if things are getting "weird"...
Not saying I know this fixes your problem, but it tends to fix most "odd user" and similar issues like this, because it resets the whole "stack".
I go the same error last night. Thankfully after a few tries it reverted back so I didnt have to go through the trouble of the rest.
Running 2x 1TB 960 pros in the DIMM.2 and two 1TB 850 evos in raid 0. Using the windows driver for NVMe as I find no use in the Samsung driver.
Ive paused the updates so I dont get any more sneak attacks.
I'd give it a try with the new driver and or without Sata drives attached to the system. Should be real easy to simply unplug them for an update.
Samsung has released a new driver
Try to install this before new WIN upgrade
I have had that 2.2 driver for a while. I don't think it is the driver. Several people over at the Microsoft forum tried the windows NVMe driver instead of the Samsung driver and the error message still occurs.
Hell, I still haven't accepted that "Get Windows 10" invitation on some of my machines. Forgot to remove the gwx update before I cloned the image, lol.
Seems I missed out on several generations of broken drivers, shucks.