We have confirmed the problem. It happens because the VeriSign timestamping service used by VisualGDB to sign the generated drivers with a temporary certificate stopped working. We have updated VisualGDB to use a different timestamping service. Please try this build: VisualGDB-184.108.40.20636.msi
I thought I have to install VisualGDB-220.127.116.1136.msi which would fix the issue we are having but it didn’t. Until I realized, that the USBDriverTool is included within the VisualGDB-18.104.22.16836.msi package.
It works now but we have students working with the USBDriverTool which do not have Visual Studio installed on their private computers. What’s the solution for them if they do not have a license for Visual Studio? As far as I know the VisualGDB-22.214.171.12436.msi package does not support the Visual Studio Community editions?
Sorry, our support only covers our paid products such as VisualGDB. We will eventually release an updated stand-alone version of USBDriverTool, however we are not able to guarantee any timelines for it.
Edit: we have updated the stand-alone USBDriverTool to use the new timestamp server.
This reply was modified 1 week, 2 days ago by support. Reason: updated USBDriverTool