Sticky Windows 11

[akuhlman]

Just checked and my HEX-CAN I purchased it in 2008, so have had good use out of it! Unfortunately, no matter what I try it will not work on a Mac M1. Windows 11 insider addition does NOT have a core memory isolation option for some odd reason. When trying to install VCDS I cannot tick the box install USB memory drivers. VCDS will install, but testing option doesn't work once plugged in. Sadly, I will just have to keep an old laptop (either Windows or a Mac with Intel) to run VCDS, not worth replacing my HEX-CAN.

 

[Uwe]

Just checked and my HEX-CAN I purchased it in 2008, so have had good use out of it! Unfortunately, no matter what I try it will not work on a Mac M1.

Yeah, a Mac with an ARM CPU is likely to be problematic with a legacy interface, but that isn't a Windows 11 issue per se.

Sadly, I will just have to keep an old laptop (either Windows or a Mac with Intel) to run VCDS, not worth replacing my HEX-CAN.

If you're working on older cars that are compatible with legacy interfaces, then you might have to keep an older computer around as well.

-Uwe-

 

[Nuje]

The other option is to sell the HEX-CAN (they hold value quite well) and put that towards a more modern interface. (?).

 

[diedeb]

After much faffing, I've figured out what is interfering with VCDS finding HEX-V2 interfaces on my laptop.

I had the bright idea of seeing if another process was using high CPU when VCDS was timing out, and hey presto!:

The culprit appears to be
"Windows Driver Foundation - User-mode Driver Framework Host Process", so a legitimate Windows process.
With that end-tasked, VCDS finds the interface OK.

Not sure if that points to something RT can change, or whether it's still an issue my end...

Thank you for pointing out the "Windows Driver Foundation" issue. I managed to find the device which is causing the issues in combination with VCDS on Windows 11.

In my case disabling the "HID sensor collection V2" resolved my problems related to VCDS not working / crashing when HEX-V2 interface is being used.

I needed to disable the following devices:
HID\VID_8087&PID_0AC2\6&1E814A59&0&0000
HID\VID_8087&PID_0AC2\6&859E19C&0&0000

 

[Mike@Gendan]

In my case disabling the "HID sensor collection V2" resolved my problems related to VCDS not working / crashing when HEX-V2 interface is being used.

You're a star! That fixed mine too

(I wonder what that device actually does )

 

[XSP]

My Hex Can is failing on my new laptop with win11 I have made the said adjustments. But no luck. Any pointers?

 

[Uwe]

My Hex Can is failing on my new laptop with win11 I have made the said adjustments. But no luck. Any pointers?

I get a fault 28 and drivers won't update.

Error 28 is: "The drivers for this device are not installed."

Let's back up for a moment and ask a basic question: Did you actually install the drivers? I.e. did you put a tick mark in the box next to, "Install USB Drivers for Legacy Interfaces"?

-Uwe-

 

[XSP]

You know sometimes in life you just have to hold your hands up! I did manage to work out i had not ticked the driver download tab but only when i decided to re install the software, anyway alls well that ends well it is working perfectly.

Thanks for the responses

 

[Green_GTi]

I had the same problem with the HEX-V2 with a brand new Dell XPS-13 9320 and a brand new HEX-V2 interface.
The recommendation of "Leave the V2 plugged in. Power down them machine. Power it back up and let it boot normally. Again, leave the V2 plugged in the whole time."
Worked great!
Thank You

 

[Cjbaker]

I'm no Bill Gates, but can't the memory integrity issue be resolved with updated drivers? I've got an old KII-USB interface and a brand new Windows 11 laptop that I'd rather not compromise with memory integrity turned off.

 

[Uwe]

I'm no Bill Gates, but can't the memory integrity issue be resolved with updated drivers? I've got an old KII-USB interface and a brand new Windows 11 laptop that I'd rather not compromise with memory integrity turned off.

In theory, yes. But considering how long the affected interfaces have been out of production, we're not inclined to invest the effort & expense required to make updated drivers -- especially considering the hoops that need to be jumped through in order to get the drivers signed -- when there are several straightforward work-arounds for this.

-Uwe-

 

[Cjbaker]

In theory, yes. But considering how long the affected interfaces have been out of production, we're not inclined to invest the effort & expense required to make updated drivers -- especially considering the hoops that need to be jumped through in order to get the drivers signed -- when there are several straightforward work-arounds for this.

-Uwe-

Fair enough, but when the work-arounds compromise the security of your computer they are far less than ideal.

 

[Cjbaker]

In theory, yes. But considering how long the affected interfaces have been out of production, we're not inclined to invest the effort & expense required to make updated drivers -- especially considering the hoops that need to be jumped through in order to get the drivers signed -- when there are several straightforward work-arounds for this.

-Uwe-

Finally decided to just stick with an old slow laptop for VCDS. Uninstalled from my new machine, but the drivers persist, so I still can't turn on memory integrity. Can't find a Ross-Tech driver in Device Manager. Found the two files in explorer, I could delete one but not the other even though I'm administrator. Can you help me with how to get these drivers uninstalled in Win11? KII-USB install.

Thanks.

 

[Uwe]

Can you help me with how to get these drivers uninstalled in Win11?

Me personally? Doubtful. The only Win11 device I have has an ARM CPU on which those drivers can't be installed at all.

What exactly remains, where? Try booting in SAFE mode and then removing it?

-Uwe-

 

[Cjbaker]

RT-USB64.SYS
It was in Windows\system32\drivers where I deleted it
It's still in Windows\system32\driverstore\filerepository where it won't let me delete it.

 

[aspataro]

Right.


I believe they enumerate slightly differently; different PIDs?

Try this next: Leave the V2 plugged in. Power down them machine. Power it back up and let it boot normally. Again, leave the V2 plugged in the whole time.

-Uwe-

This worked for me, thanks!!

 

[Booorizza]

Thank you for pointing out the "Windows Driver Foundation" issue. I managed to find the device which is causing the issues in combination with VCDS on Windows 11.

In my case disabling the "HID sensor collection V2" resolved my problems related to VCDS not working / crashing when HEX-V2 interface is being used.

I needed to disable the following devices:
HID\VID_8087&PID_0AC2\6&1E814A59&0&0000
HID\VID_8087&PID_0AC2\6&859E19C&0&0000

This worked for me!

 

[Mike@Gendan]

If you're using a legacy interface (anything other than a HEX-V2 or HEX-NET), the old drivers may be a problem with the way Windows 11 appears to be configured by default. We believe work around should be:

Settings -> Update & Security -> Windows Security -> Device Security -> Core Isolation -> Memory Integrity.

Turn Memory Integrity OFF.

Noticed today that in the current version of Windows 11, this has changed to:

Settings -> Privacy & Security -> Windows Security -> Device Security -> Core Isolation -> Memory Integrity.

 

[Uwe]

Noticed today that in the current version of Windows 11, this has changed to:

Interesting. I recently (finally, because W10 support is ending next month) upgraded my PC to Windows 11. "Security" initially complained that Memory Integrity was off. Well, yes, it is. I do occasionally need to test things with one of our Legacy interfaces. I dismissed the complaint and it hasn't come back so far.

-Uwe-

 

[Mike@Gendan]

Interesting. I recently (finally, because W10 support is ending next month) upgraded my PC to Windows 11. "Security" initially complained that Memory Integrity was off. Well, yes, it is. I do occasionally need to test things with one of our Legacy interfaces. I dismissed the complaint and it hasn't come back so far.

-Uwe-

I have a feeling that may be the case on the majority of Win10 upgrades where the setting is inherited, as opposed to clean installs.
It's turned off on this PC for example, and I didn't change it.