Trying to recover a hibernated Windows 10 ssd in a Dualboot setup with EndeavourOS ssd

I have a dualboot setup with Windows10 on one nvme, and EndeavourOS on another nvme on a Lenovo Legion Pro.
I’m trying to boot into Windows10.
The EndeavourOS drive boots fine, the Windows10 drive however doesn’t even show up as a boot option in neither BIOS nor grub, although the Samsung Drive which it’s installed on is listed in an overview in the Lenovo Legion BIOS.

I might have done an error by installing EndeavourOS over a Manjaro Install and expecting running $ sudo os-prober putting the windows install into the grub menu.

Things I’ve tried:

sudo fdisk -l gave me this output:

Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: WDC PC SN730 SDBPNTY-1T00-1101          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5D7982CB-1CF6-4D6E-9001-1ABDC873495E

Device           Start        End    Sectors   Size Type
/dev/nvme0n1p1    4096    2052095    2048000  1000M EFI System
/dev/nvme0n1p2 2052096 2000397734 1998345639 952.9G Linux filesystem


Disk /dev/nvme1n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 500GB                   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: CCFB8613-AC69-44B8-A669-0DA14EC5AC75

Device         Start       End   Sectors   Size Type
/dev/nvme1n1p1  2048     34815     32768    16M Microsoft reserved
/dev/nvme1n1p2 34816 976773119 976738304 465.7G Microsoft basic data


Disk /dev/mapper/luks-fa14a127-22f8-416c-be07-a3a00a5482ed: 952.88 GiB, 1023150870016 bytes, 1998341543 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

sudo grub-mkconfig -o /boot/grub/grub.cfg which gave me this output:

Generating grub configuration file ...
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done

and running sudo os-prober again, with no output at all, not even related to EndeavourOS

enabling and disabling ‘secure boot’ in BIOS which resulted in nothing.
sudo mount | grep efi

gave me:

efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)

sudo mount /dev/nvme1n1p2 /mnt/windows-efi (after sudo mk /mnt/windows-efi of course
gives me:

Windows is hibernated, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Could not mount read-write, trying read-only

So I’m guessing the hibernation state makes booting impossible.
I should maybe mention that after booting in EndeavourOS a pop op message says “Samsung 970 nvme is about to fail” which is the Windows drive. Please tell me if there’s any information I forgot to put in here.