HELP: NVMe undetected by Windows and Linux but detected in BIOS after BIOS update

Not sure if ths is the right place to post this, it's actually a pretty unique problem I guess.

This won't be short ("that's what she said").

So, I have a Clevo computer (i5-8300H, MX150, 16GB RAM, 1TB Sabrent Rocket NVMe, 250GB Samsung 850 Evo SATA), running pretty good for almost three years.
Sometimes, during last year or some more, the computer suddently started to run the CPU fan (the GPU one acts normal) at max and to make some really annoying bip noises until it shuts down. This happens in Windows and in Linux, even if the computer is doing nothing; checking temps the CPU is cool (even the air pumped out by the fan is cool, very different from the one exiting while the CPU is at 100%). It started to be very annoying, since when happens who knows if it occurs once, twice or more in a row: I usually put in standby before it shuts down, wait some second and wake the computer up, hoping it realizes it's screaming for nothing since there is no hot alert. I even replaced the thermal paste 2-3 times (Artic MX-4).

I decided I wanted to solve this issue. I wrote to the support center where I bought the computer. They said it might be a motherboard issue (very happy to read that), and suggested me to try to update EC and BIOS, providing me updated files and a detailed guide.

I took some days to prepare to the event, since once I burned a laptop motherboard after a BIOS update (it was a very unfortunate coincidence that I won't explain here).
Yesterday morning I finally updated the EC and the BIOS, and while I was shitting myself I pressed the power on button to check if everything went well: I was really happy to see lights turning on.

But. The computer wasn't able to load two of the three OS installed. I provide further info about the OS installed:

• Windows 10 on Samsung SATA: I keeped this when I added the Sabrent disk a coule of years ago, so I could check files and software after installing Windows 10 on the brand new Sabrent. After some months I tried to remove this SSD to make it external, but I found out that the Windows Boot Manager was here, so without this SSD/Windows I won't be able to boot the main Windows 10 on the Sabrent. I planned to make a full clean install with Windows 11. Anyway, this is the only OS that boots now (I'm writing from here).
• Windows 10 on Sabrent NVMe: the main daily OS where all my stuff is located and all the software installed. I have a backup but it would be nice to check if I have everything saved. Won't boot; behaviours when tried to boot: black screen or blue screen of death with the error "inaccessible boot device".
• PopOS on Sabrent NVMe: won't boot; behavuiour: "mdadm: No arrays found in config file or automatically. cryptsetup: Waiting for encrypted source device UUID=there's a string here".

So, with this scenario you would say: "Where is the problem? Boot Windows from Samsung or a live distro and backup your files! Then make a clean install and you're good to go!". I'd love to, trust me. But here's the reason why I spent a day and a half to curse technology in front of a display and why I'm writing this essay: the Sabrent SSD is detected only by BIOS. I can't see the Sabrent in Windows, in diskpart, in a live distro from a pen drive, or when I try to install Windows.

I assume it could be a TPM stuff issue (even if I didn't do anything at all about it, never touched a thing), since when booting in Windows 10 (the woring one on Samsung SATA) I had to reset the PIN and change the Microsoft account password.

I loaded the default setting in BIOS, removed and reapplied the CMOS battery, turned off the TPM, cleared the TPM, but nothing worked.

I took some pictures to provide more infos: the first is a Diskpart and drive manager screen, the others are my BIOS settings.

I would really appreciate some help. Thank you very much for reading, I can provide more info of course.

UPDATE:
After thousands of tries and stuff I probably digged in the problem. The situation is very strange.

Sabrent nvme is alsways recognised by the BIOS but is never recognized by booted Windows on the other SSD or by a live Linux booted from a pendrive. I tried to unplug and replug the nvme while Windows was booted and surprisingly it appeared; so I thought to format it and make a fresh install.

But this method of unplug and replug won't work during Windows installation: the Sabrent won't be detected. It's like the Sabrent won't be recognized right after BIOS stage for some reason. I can buy an eclosure and make it external, but this behavior is very very strange.

The problem isn't the m.2 slot, since I tried with another SSD and it works normal.

If someone has some idea would be very nice.

Thanks.