DiCE Unit "This device cannot start (Code 10)" Topic is solved

[prwood]

I just received a DiCE unit last night and am trying to get it working on a Windows 7 Enterprise virtual machine running in Virtualbox, with a Mac OS X host. Here are the steps I have taken so far, which have not been successful:

Edit: Clarifying below whether each step was run in the Mac OS X Host (MAC HOST), in the Virtualbox software on the Mac (VB), on the Windows VM, or hardware (HW).

Edit 2: Adding additional steps that were done before installing VIDA. Let me know if you need any additional details as I'm trying to be concise.

1. [MAC HOST] Downloaded and installed Virtualbox for Mac OS X: https://www.virtualbox.org/wiki/Downloads
2. [MAC HOST] Downloaded Windows 7 Enterprise Edition w/IE 11 Virtualbox virtual machine from Microsoft: https://developer.microsoft.com/en-us/m ... tools/vms/
3. [VB] Imported virtual machine to Virtualbox.
4. [MAC HOST] Ran this command so that Virtualbox didn't try to set the virtual machine's clock: https://askubuntu.com/a/331871
5. [VB] Started virtual machine.
6. [WIN VM] Un-rar'd VIDA files from the DVD provided with the DiCE unit.
7. [WIN VM] Disabled setting Windows system time via internet, and manually set time to a pre-12/31/2017 date.
8. [WIN VM] Ran installer for VIDA All-in-One.
9. [WIN VM] Ran patch that was included on DVD.
10. [WIN VM] Started up VIDA and verified that I was able to log in as admin and browse around the VIDA interface. Then logged out of VIDA.
11. [HW] Connected the DiCE unit to my Volvo via its OBD cable.
12. [HW] Upon connection, the green "Firmware status" light came on, followed by the blue "Bluetooth com status" light. Then both lights slowly blinked for a few seconds. Then the "Bluetooth com status" light shut off, and the green "Firmware status" light continued to blink slowly. Throughout the rest of this procedure, the only light that had any activity was the slow blinking green "Firmware status" light.
13. [HW] I connected the DiCE unit's USB cable to my computer.
14. [VB] In Virtualbox, I selected the "SETEK DiCE Vehicle Diagnostic Adapter" from the USB device menu.
15. [WIN VM] Upon doing this, the Windows virtual machine showed an alert that a new device had been detected.
16. [WIN VM] After about 20 seconds, I got another alert that the device drivers failed installation.
17. [WIN VM] I went into the Windows Device Manager and saw an entry for the SETEK DiCE unit, which was popped open with a sub-entry showing a yellow exclamation point.
18. [WIN VM] Double clicking on this entry revealed the error message from the subject of this post, "This device cannot start (Code 10)".
19. [MAC HOST] Did some Google research and found this thread: http://www.volvoxc.com/forums/showthrea ... experience
20. [WIN VM] Tried the recommended advice of removing all USB devices in the device manager and restarting the VM, but I was left with the same issue.
21. [WIN VM] When I logged in to VIDA after connecting the device, there was just an "X" in the box for communication tools. I found a suggestion to add some keys to the Windows registry (can't bring the link back up at the moment), I tried it, and the communication tools box in VIDA now showed the SETEK DiCE adapter.
22. [WIN VM] However, when I select the device and click 'Read', VIDA gives me an error message in red text saying that there was a communication error. The DiCE unit doesn't show any additional lights to indicate that it was registering any communication - just the slow blinking green "Firmware status" light.

Any suggestions on where to go from here?

[prwood]

Here is a photo of the device showing both the blue and green lights when initially connected.

IMG_4406.PNG (1.16 MiB) Viewed 5813 times

[RickHaleParker]

What is your Host Operating System?
It is not clear if you doing everything in the VM OS or some of it in the Host OS.

[prwood]

What is your Host Operating System?

Mac OS X.

[prwood]

What is your Host Operating System?
It is not clear if you doing everything in the VM OS or some of it in the Host OS.

Edited my initial steps to indicate where each one was executed.

[RickHaleParker]

Scratch that, I was going to tell you how to do a working Vida install on a Windows 7 host.

The error code 10 is a common driver error. It indicates that the driver for the specific device is failing to load. Therefore, you can fix the problem by focusing on device drivers. ... Usually, for any device, uninstalling or reinstalling the driver would resolve the problem.


1. Go here and get the new patch. viewtopic.php?f=40&t=83834 Follow the instructions.
2. Unplug the Dice from the USB port.
3. Go to Device Manager in Windows and uninstall the Dice driver.
4. Reboot Windows
5. Turn on the Dice
6. Wait for the lights to settle.
7. Plug the Dice into the USB port.

The drivers should reinstall. If they don't, the Dice installer should be on the Vida install media look in \3PP\Products\DiCE.

[RickHaleParker]

Edited my initial steps to indicate where each one was executed.

What part are you executing on Mac OS X?

[prwood]

Edited my initial steps to indicate where each one was executed.

What part are you executing on Mac OS X?

Hm, actually there were some prerequisite steps I didn't include, which I did run on Mac OS X. I'll edit the original list again to include those.

[prwood]

Edited my initial steps to indicate where each one was executed.

What part are you executing on Mac OS X?

Ok, my original post is updated with all of the Mac OS X steps.

[RickHaleParker]

I was able to get it installed by setting the VM's system clock to a pre-12/31/2017 date.

It would not let you Install with a post 2017 date or you set the date back to run Vida?

VM] When I logged in to VIDA after connecting the device, there was just an "X" in the box for communication tools.

You can get that even when the driver is OK in Device Manager. It is that conflict between Dice, Internet explorer and .net Framework. My Chrome conversion gets around all that. viewtopic.php?f=40&t=83998