Hi Greg,
Thanks for the reply, yes I definitely made sure it's not a caching conflict, that's the very frst thing I thought of. I don't cache to removables due to the fact that it cause corruptions if I yank out a drive shortly after a file transfer. That said, I still wait 30 seconds after file transfers before pulling a removable, it's just an old habit. But even if it was a cache corruption, it wouldn;t (or shouldn't) cause this type of behaviour, you would get a notice from Windows stating that there's an issue with the file system on the drive, and it would attempt self-repair, or the file would simply be corrupted. Like I said in my post, I did all the obvious fixes (what I call "idiot fixes", because one would feel like an idiot for not having thought of that solution themself lol). And I hexdumped the partition to check for obvious fat errors, and nothing stood out.
What's interesting is that the problem seems to be limited to this brand/model of jump drive only. I have other brands, they don't replicate this problem. I also have other models of Kingston drives (older USB2 drives), and they also don't replicate this problem. Furthermore, the problem with this specific drive also occurs on my three other Win10 / Win11 PCs. It happens on my office Win10 desktop, my home office Win11 desktop, and my two Windows laptops. So I'm suspecting this bug that many are having with the hung drive letters on Kingston g3 drives is specific to this drive's hardware/fimware. I've tried on my various Linux machines that I use for writing firmware for bootcode and microcontrollers (C, ASM, ARM opcode/binary), and the problem doesn't occur with Linux. I can mount and dismount volumes to my heart's content. But that's not surprising being that Linux is much more robust than Windows due to the more direct interface between the human and the machine's kernel code.
I'll go ahead and issue an official bug report to MS, but I'm guessing they already have dozens of them from the other users on the internet (and this very forum) who have the same problem. I've tried the solutions given to them, (scannow, shutdown /f, and so forth), but none worked for me just as it didn't work for them. The problem lies with Kingston and/or MS, which has to do with some incompatible glitch between the flash controller of these sticks and Windows. Unfortunately, with Windows everything is so locked down that us end users are unable to get into the 1s and 0s to see what the glitch is in real time.
Thanks again for your help, if I ever do find the solution I'll be sure to update this post.
Cheers,
Eric