Judging by your Task Manager screenshot (that your SSD is listed as an HDD), the cause of the problem is probably either your SSD's firmware or the (software) SAT layer provided by your SATA/AHCI driver is not reporting / translating the corresponding information (that the drive is non-rotating) properly. (With a second thought, it could also be that in your UEFI settings, your SATA controller is not configured to operate in AHCI mode...)
Check whether you are using the Microsoft AHCI driver (Standard SATA AHCI Controller) or a driver from AMD in Device Manager (under IDE ATA/ATAPI Controllers). If it's the latter case, you might want to consider uninstalling it. (I do NOT guarantee that it will not break booting.)
You may also use programs (needs to be run with Administrator Windows Terminal / Command Prompt) in sg3_utils (click this to download the last working version) to confirm that your drive's firmware is doing its job fine and the SAT layer is indeed bad.
Firmware (Word 217 / 0xd9 being 0x0001 states that the drive is non-rotating):
PS C:\Users\tom\Downloads\sg3_utils-1.46mgw64> .\sg_sat_identify.exe PD0
Response for IDENTIFY DEVICE ATA command:
...
d8 0000 0001 0000 0000 0000 0000 10ff 0000 .. .. .. .. .. .. .. ..
...
SAT layer:
PS C:\Users\tom\Downloads\sg3_utils-1.46mgw64> .\sg_vpd -p bdc PD0
Block device characteristics VPD page (SBC):
Non-rotating medium (e.g. solid state)
...
What you might see when the produced VPD is not "good enough":
PS C:\Users\tom\Downloads\sg3_utils-1.46mgw64> .\sg_vpd -p bdc PD1
Block device characteristics VPD page (SBC):
Medium rotation rate is not reported
...
(There's also a chance that it does not produce this particular VPD page at all.)
For your reference:

Disk 0is listed as anHDD. This probably indicates that the SATL does not translate ATA IDENTIFY DEVICE result properly to a Block device characteristics VPD page (assuming Samsung does not suck enough on their firmware). I am betting that you are not using the Microsoft AHCI driver but one from AMD, and the driver is doing a bad job. (Consider showing which driver you are using with a Device Manager screenshot.) – Tom Yan Dec 06 '21 at 15:01