Cannot boot Windows 10, unknown problem

I have Minitool Partition Wizard inside of WinPE which I am using now. What exactly I have to send? Which screenshot?

Math said:

I have Minitool Partition Wizard inside of WinPE which I am using now. What exactly I have to send? Which screenshot?

I've tried with UEFI yesterday but it isn't the problem. It existed before that.

Yesterday I tested it with chkdisk. Which info you need from HD Tune? In health section everything is fine except one current pending sector warning.

His system is getting past booting. The problem is not with the System Reserved Partition or the BCD files. The problem is with an improper SATA controller driver loading with Windows - or the proper SATA controller driver not loading with Windows. If you can't boot into safe mode to uninstall the improper SATA controller driver and go back to the basic Microsoft driver (until you can re-install the proper controller driver), then you are going to have to back up the data you want to save and clean install Windows 10.

However, after you do the clean install of Windows 10 - if you restore a backup image of the old Windows 10, the problem will return, because you will also be restoring the SATA controller configuration and driver that is causing the problem now.

Is F: drive shown in the screenshot a Recovery Partition? If it is, and if you are going to do a clean install, after selecting the custom install option, I would delete the first three partitions and select the resulting unallocated space to re-install Windows 10 to. If F: drive in the screenshot is a data partition that you want to keep, then I would delete the first 2 partitions and re-install Windows to the unallocated space.

I didn't install any driver in the meantime. As I already wrote system didn't want to boot because it lacked nvstor.sys which isn't part of my system. Why that happened, God knows. Just updated windows on CU and wanted to defragment system with OO Defrag.

Math said:

I didn't install any driver in the meantime. As I already wrote system didn't want to boot because it lacked nvstor.sys which isn't part of my system. Why that happened, God knows. Just update windows on CU and wanted to defragment system with OO Defrag.

And if the system was failing at the level of the System Reserved Partition or a bad BCD configuration (which is the troubleshooting path people are taking you down), then you would not know nvstor.sys is the problem file because you would not get that far into Windows 10 loading to be able to see that error. Booting into safe mode may bypass loading the nvstor.sys driver and allow you to uninstall the IDE ATA/ATAPI Controller from device manager - which is what would be trying to load nvstor.sys. After that is uninstalled, then the system would reboot and load the standard, Windows 10 default SATA controller driver provided by Microsoft. Then you could go back and re-install the proper SATA controller driver.

nvstor.sys is included in the standard Windows 10 download from Microsoft. Here's a link to the file from my computer:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

I am not sure where the file gets copied to when it is actually being used as the SATA controller driver - mine is just sitting in Windows/System32/drivers, but it is not installed or being used on my computer, so that folder may not be the proper folder for it when it is being used by the system.

If I understood Dalchina correctly, he suggests me to create images of these two important partitions and to add them inside of new Windows installation. Honestly, I've never did something like that and have no idea how to do that :)

Math said:

If I understood Dalchina correctly, he suggests me to create images of these two important partitions and to add them inside of new Windows installation. Honestly, I've never did something like that and have no idea how to do that :)

@dalchina's suggestion was to make an image of the Windows partition. Then clean install Windows 10, which would fix any problems in the System Reserved partition. But if you then restored the image of the Windows partition, the problem would return because the problem is in theWindows partition, not the System Reserved partition.