not sure where this bad timestamps comming from.I didnt use sfc or dism commands yet (dont wanna make anything trashy / unworking).Just used chkdsk on main drive and it found no errors.I dont have any USB drivers and just using Windows drivers itself and otherwise I dont have the USB drive anymore.
Sfc and dism. You have bad timestamps on you Win10 cmd and bundled bluetooth driver. At a minimum since you show corruption on your main drive. Also chkdsk your main drive. Do you have other usb drives to test with before we conclude it's a hardware issue?
Something is wrong with T4Y now. I had the same errors. Ran a tracert and a server on the way is causing issues. Lot of European users cannot access or post as of late
Denuvo’s Anti-Piracy Protection Probably Makes Sense For Big-Selling AAA Titles