Thanks i didnt get any message that these where already installed, so its good sign.

Maybe someone can make some magic and create something like injecting these from Windows PE, or Windows To GO USB, or something like that. I saw at least some drivers injection by such way.
I dunno what these are doing if its just some dirty system file rewrite and you would miss only some proper possiblity to uninstall updates because of not working registry and other minor things it would be nice.. More nicer if it would be usefull for 1 boot and after would be possible install them by proper way.

Hmm,
i installed both updates - i checked that they are installed - but run them again - im getting already installed, cloned installation on Samsung 950 Pro, but im still getting some boot error.. Something else has to involved. I dont thing that my Samsung 950 Pro is fake one, i seem to have all right stickers and its reporting in Bios as Samsung 950 Pro.

I finaly made it.. I was able to clone M.2 Sata NVME to M.2 for long times, but had some booting issues (blue screens), its probably because of used imaging tools.

How to convert Win7 x64 MRB installation to EFI installation:
- i suppose that now all steps are needed, or that is best or fastest way
0) install 2 Win7 updates for NVME support first
1) First i made whole driver image (M.2) Sata with Acronis, but you can probably use any tools. Make its from USB /CD its saver than from working OS.
2) Migrated this image into virtual machine with EFI enabled.. I just tried to mount orginal physical M.2 Sata driver within Win10 machines in Vmware Workstation or VirtualBox - these options are on paper supported, but its lengthy and has issues, for example when Vmware tried to read from EFI partition.. im getting read errors and crashed.
So i had create new virtual disk.. boot from imaging tool cd.. recover M.2 Sata image from network to new virtual drive.
O discovered that Vmware in EFI its not booting from lots legit EFI boot CDs, Virtualbox is booting from everything.
3) Restore image - i used lots of partition tools - EasyUS (11.5.12), R-Driver (6.1001), but i always got blue screens after booting.. Acronis true image worked fine, i suspect it from doing some P2P HW adjustment, but im not sure.
4) Now i used some partition tool - like free Minitool / Aomei / Paragon HDD suite etc.. and you need to convert MBR disk to GPT disk without data lost.
5) Now you need with that partition tool resize Win7 partition, to make at the start of disk place for EFI partition (200 MB is enough).
6) Now you have to create Windows 7 EFI partition, from other real and virtual machine (my case)...
7) Restore Win 7 EFI partition image to free space at the start of disk..
8) Now you probably could to use Windows 7 with NVME drivers and mess with it until to it would be able to link EFI partition with Windows 7 partition.. I made this in the past working with Win 8 but its mas ungly process..
So im recomend just install some you favorite linux distro (if you have not favorite Linux Mint is most user friendly and its still based on Debian->Ubuntu) on some other (small partition - 20GB is enough) and install GRUB efi bootloader during installation (i thing that is default, so you dont need to do anything special). Linux is nice as better recovery console and backup OS for surfing etc.
If after reboot are Linux and Working, you just can change /boot/grub/grub.cfg (need admin rights to select Windows as default instead Linux).
7B) If as i you already have Linux on your NVME, you have to make MBR Linux to EFI too - boot-repair-disk -, for this -https://sourceforge.net/projects/boot-repair-cd/ .. and use its nice wizzard to install Grub EFI on EFI partitions.. I had once some issues because of old Linux Mint 18.2 - not available packages (sudo apt-get update), but update packages form terminal fixed it.
Now you maybe can skip.. all Linux stuff and just try, if will see in EFI no target driver Windows boot loader and if it will boot, right away - but im not sure about that..
8) You can now, but you dont need it try to to boot Windows within virtual computer, if could file, because emulated HW is else that previous physical. This step is not needed and if booting its good check that all is working.
9) Make image (again here i recommend Acronis) without virtual machine, with some boot CD and save it to some network share.
10) Recover disk image to new target disk - i my case M.2 NVME - because, that was of whole point of my MBR to EFI migration. You can make it on target computer on any other computer.
11) Switch target machine bios to boot UEFI firsts, or simply eble UEFI.
12) Boot from migrated disk on target computer, it should work fine. In EFI you can select Windows boot loader on target device for direct Windows boot, or Ubuntu - or other distro name for Grub 2 menu, here you get boot menu with selection between Linux and Windows - of course you can select it from EFI right away only optimally - its your choice.
13) I dunno if is was done that Acronis P2P (Physical to Physical migration magic) or MB now reporting other MB ids, but after boot.. USB devices where dead so i had to connect to machine remotely and reinstal somel drivers with Windows driver search and Snappy driver installer.

NVME proof:

- BTW i find out that Crystal disk 5 and 7 no reporting very diffent numbers for 2/3/4.. maybe some tests where altered or old version has bugs.. Version 7 reporting bigger numbers.

Im using just cheap Adata 256 M.2 NVME recommended by mighty Diderius.


Second small NO-NAME partition was probably created by Boot repair disc, i dont checked what is not on it, maybe you can get rid of it.. but its so small that its in big deal.

So my NAS is now EFImied..

@ruthan - glad you got it sorted out, and thanks for posting your method for others in the future

For future reference in case others are searching and find this thread, here is my way of doing it, and Fernando's way too

Clone SSD to NVME
Installing Clean Win7x64 on M2.2280 PCIe Gen3x4 SSD A-DATA SX8200 Pro << My way
[Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS (330) << Fernando's way

This guide is not for clean install.. but for migration of already installed system.

Otherwise i started with this long time ago.. and at that time nobody pointed me to working solution, so had to find it myself.

@ruthan - Yes, "My way" link I gave above is for clone of already installed OS too (or you can do clean install, then clone that, either way is OK)
So you and me doing same, just different ways I only added those links in case others in future want to look at several ways to do the same thing

I had more time to look in to, first ESR partition could be deleted.. on EFI partition are all boot loaders.. there are also grub.cfg files.. but within them is just some path to "real" grub.cfg on Linux parition where are rest of Grub files (/boot/grub).

Other fine thing is that i could simply move and resize EFI partition to new empty space with Minitool and its still booting.. I also discovered that good way to edit EFI entries is Win10 EFI USB to go.. because setting are in NVRAM of UEFI on MB.. it doesnt matters if they are edited from OS on actual SATA / NVME disk or from live media.