One USB 3.0 drive works only as 2.0 with my desktop computer

Hi,
I have one USB 3.0 drive that works only as 2.0 with my desktop computer, but used to work fine. When I connect that drive to any other computer it's recognized as 3.0, so it's not the drive issue. On my desktop computer when I connect it to any USB 3.0 port, Windows (10 version 21H2 19044.1766) recognizes the drive, but says it's uninitialized. It's actually MBR drive. It doesn't matter which USB 3.0 controller I use. I have Intel on the motherboard and Fresco Logic (using manufacturer, not Microsoft driver) on a plug in USB controller. However when I connect the drive to USB 2.0 port (on Intel controller) it's recognized just fine, but of course it works at much slower speed. To me the issue must be somewhere in USB 3.0 stack, not USB 2.0 stack or hardware driver. This issue survived several upgrades, so Windows refresh doesn't fix it. How do I fix that?
Thanks.

The problem is likely a missing or out of date device driver. On my mobos though the years, USB3 is achieveable only through the device driver that came with the mobo...then updated, if needed, by Windows updates.

So, this can't be a driver issue. I have 4 other USB 3.0 drives that are permanently connected to this machine and they all work fine. I have more USB 3.0 drives that I occasionally connect and they also work fine (as USB 3.0). It's just this one particular drive. And no, there are no issues in device manager. The drive normally shows up as USB mass storage device under USB controllers section (without any abnormalities), but doesn't show up as disk drive if plugged in to USB 3.0 port.
When I delete the device and let it be discovered again, I get the following, which look rather normal to me:

Device USB\VID_2109&PID_0715\000000123ACE was configured.

Driver Name: usbstor.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1682
Driver Provider: Microsoft
Driver Section: USBSTOR_BULK.NT
Driver Rank: 0xFF2000
Matching Device Id: USB\Class_08&SubClass_06&Prot_50
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_2109&PID_8110\5&4390423&0&25

And that:

Device USB\VID_2109&PID_0715\000000123ACE was started.

Driver Name: usbstor.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: USBSTOR
Lower Filters:
Upper Filters:

It's somewhere higher than at the driver level that the problems is.

Did I mention that this issue "survived" several Windows upgrades? I guess that I forgot to mention that. I think the issue is 2 years old, but I'm finally fed up with that. If it was a driver issue, all those actions (not literally of course) are performed by Windows installer. Aren't they? When you upgrade you have a "fresh" OS, you don't need to do chkdsk, sfc or dism. So, if Windows upgrade didn't fix this issue, those actions won't do that too.
One other thing that I need to mention is that a long time ago (a year?) I deleted all USB controllers from device manager and rediscovered them. That action fixed the issue for a short time. I don't remember how long, a few days or a week at most. Well, obviously it's not a permanent fix. It's some sort of a configuration somewhere (registry?) that is different for USB 2.0 controller and USB 3.0 controller. Also, it's not a driver issue, because the same thing happens when I plug in the drive to Intel USB port as well as Fresco Logic USB port. Inter controller uses Microsoft driver and Fresco Logic uses its own. Both drivers have the same issue? Hardly. Perhaps it's a protocol driver for USB in Windows. Again, it can't be a corrupt file, but it could be corrupt configuration somewhere that isn't fixed by an upgrade.

Circling back to this issue... it can't be a hardware driver. I've already mentioned that 2 different controllers using 2 different drivers have the same issue. How could that be? But there is more... what I haven't mentioned yet. At some point I had a FireWire card installed that also had USB 3.0 ports. I don't remember exactly which chipset it was, but it was a third one. Either VIA or Asmedia. For that I also installed the manufacturer driver. Guess what? Same issue there too. This should definitely disprove your theory of a hardware issue. Three different controllers using 3 different drivers having the same issue? Nuff said...
The issue is somewhere in the USB protocol stack. Somehow the drive data that exists in the protocol stack gets corrupted and deleting the USB device (the drive) doesn't fix that. Deleting the controllers does, but somehow this is short lived. Interestingly, when I deleted both USB 3.0 controllers (well, Intel is actually 3.1) the USB 2.0 ports were gone too. That made me lose access to my PC as my mouse and keyboard are USB type. That is why I don't want to keep going through this exercise, especially that the effect wasn't permanent.
The drive shows up as "USB Attached SCSI (UAS) Mass Storage Device". The id is USB\VID_2109&PID_0715&REV_0336. That is when connected to USB 2.0 port. When connected to USB 3.0 port it's plain "USB Mass Storage Device" and the id is USB\VID_2109&PID_0715&REV_0336 (same). Under disk drives section it shows up as "VirtualDisk USB Device" with several ids, but the theme is "USBSTOR\Disk________VirtualDisk_________" and "USBSTOR\GenDisk" when connected to USB 3.0 port. When I delete the virtual disk and USB mass storage device and let the system rediscover it, it's back to the same issue.

I would download and run (no install required) this USB Device Tree Viewer tool.
Can tell you a lot about what Windows thinks about your USB device and its capabilities.
Link: USB Device Tree Viewer

I do have UsbTreeView output, but the size is over 1.2 MB. I can insert image and video it seems, but there is no option to attach text files.