Unable to boot into Windows 10 (UEFI)

You should search for such a small ~ >250 MB Fat32 formatted drive (on Linux it is called sda 1) and clone it separately, in addition to the main drive. In your case, it is the 260 MB drive:

• Perhaps also use bootrec to reactivate the boot drive, see https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-will-not-boot-disk-0-marked-as-gpt/431dbbee-4fdd-4418-8407-98ae9e885bbe. You can access the msdos command prompt using a regular Windows 10 legacy MBR format boot stick.

• Switching from MBR to GPT boot stick might be needed to get to msdos and then to the UEFI (without CSM) boot stick, see here for more details. The two boot sticks were needed in my case, since I did not have any menu / bios at startup, just a repeating Realtec Ethernet information.

• In MSDOS, go to d:, e:, f: ... until you find the GPT partitioned UEFI (without CSM) stick. When you have found it, type setup and try to repair a detected Windows.

If that does not help:

• You might also assign a new boot sector with a Windows 10 GPT UEFI (without CSM) ISO created with Windows Media Creation Center. The boot stick gerated from that ISO offers bootsect in /Boot/bootsect.exe. I tried this when everything was lost anyway, do not try this if you still have other options. You then need to search for the drive letter that is your Windows drive, e.g. d:, and assign the starting boot sector. I got it reassigned, but having a completely destroyed UEFI drive with lost files, it still did not help me. It might still help you. Very dangerous and not recommended of course.

• Perhaps take additional ideas from a translation of Gelöst: Das angeforderte Systemgerät kann nicht gefunden werden and [Boot Manager][SOLVED] Fixing UEFI Boot Issues: Black Screen After BIOS POST. Booting Only Possible From BIOS F12 Boot Menu

Thus, your following comment is probably right:

I believe this is because Windows 10 stored the boot files on SSD (not sure). After some research online, I had a hunch that I deleted the EFI partition and that is causing the boot errors.

Here is how I found out about it (optional read)

I had a similar issue, I had damaged the UEFI (without CSM) boot drive.

• I did not know that Windows drive was scattered into so many partitions, thus I expected every available drive on one screen. This is of course wrong, you need to switch to an external drive on the upper right, but this is not a Linux GParted tutorial. This made me think that only the small one in the list could be the card, but instead I only saw the Windows "Basic data partition" of 236,5 GB. Please understand that it was my first time using Linux GParted:

Summing it up, I split a 261 MB drive (sda1) into 220 MB for Linux (sda1) and 41 MB for Data (sda5) and destroyed the UEFI Bios with that and which would not make any sense at MB level anyway.

I tried to get the UEFI (without CSM) files back with a Linux undelete software. Getting those UEFI files back from the now-split 261 MB drive should be possible. I tried it with testdisk and also found something, but it was a bit fiddly and I just had a new laptop, thus I decided to format and re-install everything from a "UEFI (without CSM) + GPT Windows 10 boot stick" from scratch instead.