Success getting Dexcom Studio(G4) running on Windows 8?

Poked around the registry. Not clear what needs to be cleared out. Those strings appear in numerous places.

I have added another version of the InstallDexcomWorkaround tool.

luxmatic and bort269 both ran into an issue because the device driver for the virtual USB port for teh Dexcom receiver was installed for multiple COM ports (i guess each time you install the driver it changes the COM port or maybe it uses different COM ports for each USB port).

To react to this i changed InstallDexcomWorkaround so that it will show an error when multiple receivers are identified and ask you to pass in the "right" COM port.

The best way to figure out which virtual COM Port is actually the right one is to open the Device Manager (in the start window just type “Device Manager” and then on the right side choose “Settings”). There you should see a node “Ports (COM & LPT)”. Win8 will only list the actually connected USB devices. I have attached a screenshot from my machine for clarification.

Once you found the "right" COM port, unzip the updated InstallDexcomWorkaround.zip.The tool needs to be started from an elevated command prompt. (You can get into an elevated command prompt from the "Start WIndow" by typing in cmd - the right click the Command prompt entry and choose "Run As Administrator". Switch into the folder in which you unzipped the InstallDexcomWorkarouund (via cd "FOLDERNAME") and then call "InstallDexcomWorkaround X" (where X is the "right" port).

This will apply the workaround (af if you executed the previous version also clean-up the registry).

Thanks for being so patient beta-testers :-)

Best regards,
Fabian

I added yet another post with a new version. Sorry for the inconvenience. Bort69 had the same problem - also getting the error for multiple receivers. The new version should fix this - but it is slightly more complicated, because you need to identify the right COM-port first. I tried to explain how to do it in the post above - let me know if it is not clear enough or you still run into issues.

Thanks,
Fabian

I'm still getting no receiver attached. I've attached the fix results.

1838-Dexcomfix.JPG (91.5 KB)

That sorted it out! Thanks very much for taking the time to look into this. Studio is now showing me data from my G4.

For your reference, this is the output from your workaround:

C:\Users\David\Downloads>InstallDexcomWorkaround.exe 9
==================================================
Receivers (BEFORE applying the workaround to the registry):
==================================================
- COM4: 5&1e313dec&0&2 [1]
- COM5: 6&e3e7252&0&2 [1]
- COM7: 5&1e313dec&0&1 [1]
- COM9: 6&e3e7252&0&1 [1]

==================================================
Applying the workaround to the registry:
==================================================

==================================================
Receivers (AFTER applying the workaround to the registry):
==================================================
- COM9: 6&e3e7252&0&1 [1]
- COM4: 5&1e313dec&0&2 [-1]
- COM5: 6&e3e7252&0&2 [-1]
- COM7: 5&1e313dec&0&1 [-1]

Hopefully if you try:

C:\test>installdexcomworkaround 3

then it'll work!

Thanks bort269. That fixed it. :)

Awesome!
I know how hard you've been trying to get it to work since last year! (we can finally uninstall VirtualBox ;-)

Thanks again, Fabian.

I really think Dexcom should add your fix to its FAQ even if it's with a warning (but I know they won't... it's ridiculous that they are waiting for FDA approval just for a slightly different OS). I guess once they have it online (like Carelink) this won't be an issue anymore. But it's crazy that if you were to buy a brand new computer right now, you wouldn't be able to use their software! (since new computers come pre-built with Windows 8, or it would be a Mac)

Hopefully people will find this post, or maybe you can start a new thread with a title like:

"Here is a fix to run Dexcom Studio with Windows 8"

I have posted a new thread here with the newest version of the tool. I was able to simplify it so that it is not necessary anymore to manually figure out on which port the receiver is attached.

Best regards,
Fabian