Windows 10: Could not locate efi boot bootx64.efi error

Hi there, I have installed windows 10 pro on a ssd nvme m.2 and I have used it for few weeks without any problemit is a win to go with an adapter for USB. After an windows update I got this error: ,,could not locate efi boot bootx64.efi'' and cannot use it anymore. I want to mention that the Secure Boot is disabled. The ssd was running perfectly fine before that update and the windows is activated. I have attached a picture. Please help me. Thank you!!

:)

 

Why would windows 10 EFI installer not recognising keys?

I bought a gigabyte board to find it boots to EFI console.

No matter the helpful MS
TechNet provided instruction enough on how to install my OEM copy of Windows 10 64.

One glaring problem I can type the following into the console as directed by MS TechNet BUT/HOWEVER/WOULD YOU BELIEVE when the BOOTX64.EFI "runs" it prompts with "Press any key to boot from CD or DVD" and then IGNORES the keyboard
- result my machine never boots but just falls back into the console.

So, behaviour is the raw motherboard boots to EFI, recognises the usb keyboard enough to allow me to enter the commands above but ignores keyboard when "\EFI\BOOT\BOOTX64.EFI" is run.

Is this a problem with the \EFI\BOOT\BOOTX64.EFI? Why would it not accept keys from the same keyboard that was used to run it and from the same shell that run it?

As you can imagine it is a little frustrating because the OEM version is not free.

Any useful suggestions appreciated.

Cheers,

B

 

Which tool to recover the EFI partition? Booted into Rescue Disk

The location is here:

C:\EFI\boot\bootx64.efi

 

Which tool to recover the EFI partition? Booted into Rescue Disk

That's not what they suggest here:

FIX: Steps to Fix Winload.EFI Error - Appuals.com

Winload.EFI Error, is pretty much self explanatory by it’s name is an error that prevents windows from loading. This is usually caused by corrupt boot records or incorrect boot configuration. Depending on your Operating System, the error message may vary but the keyword winload.efi will be same. On a Windows 8/8.1/10 system, the error usually pops-up in the following form.