A recent user who purchased the VXDIAG NANO for Volvo encountered an issue: while using the VXDIAG device with the official Volvo diagnostic software VIDA, the software could log in normally, but the "Communication Tool" dropdown list did not display the VXDIAG device, making it impossible to establish communication with the vehicle.
The customer later shared a complete workaround that, while a bit unconventional, effectively solved the problem. We’ve organized his experience here to help other users facing the same issue.
Problem Overview
-
Operating System: Windows 7
-
Diagnostic Software: Volvo VIDA (2014D)
-
Interface Device: VXDIAG VCX SE
-
Issue: VIDA can launch and log in, but the VXDIAG device does not appear in the “Communication Tool” dropdown menu.
Summary of the Solution
The user managed to get VIDA to recognize the device and communicate with the vehicle by performing the following two steps:
-
Disable Driver Signature Enforcement
-
Reset Windows Activation Status
Step 1: Disable Driver Signature Enforcement at Startup
How to do it:
-
Restart your computer and press F8 during boot.
-
In the “Advanced Boot Options” menu, select
"Disable Driver Signature Enforcement." -
Once the system starts, reinsert the VXDIAG device and check if VIDA now lists it in the Communication Tool dropdown.
Technical Background:
Windows 7 enforces driver signature verification by default, preventing the system from loading drivers that are not digitally signed by Microsoft. Disabling this enforcement allows the system to load the VXDIAG driver.
Step 2: Run slmgr -rearm to Reset Windows Activation Status
How to do it:
-
Open Command Prompt as Administrator.
-
Type the following command and press Enter:
slmgr -rearm -
The system will reset the activation countdown and may prompt for a restart.
-
After rebooting, try connecting to VIDA again.
Technical Background:
If Windows remains unactivated for an extended period, it enters “non-genuine” status, which can restrict system functionality, including USB drivers and communication capabilities. The slmgr -rearm command temporarily restores full system functionality by extending the activation grace period.
User Feedback
"These workarounds are not ideal, but they allowed me to successfully complete changes to my vehicle."
— VXDIAG User
Additional Considerations
We also learned that the customer had previously installed GM diagnostic software such as TECH2WIN and GDS2 on the same Windows system. This could have caused a software conflict, preventing VIDA from detecting the VXDIAG device.
Alternative Solution:
-
Uninstall other diagnostic software that might be interfering.
-
Or, set up separate system partitions or virtual machines for different diagnostic environments to avoid conflicts.
If you’ve run into the same issue with VIDA not recognizing your VXDIAG device, we hope this experience helps. Feel free to share your own solutions or questions in the comments!
