Most people have drivers from other vendors that are also problematical with this setting.įeedback from anyone who lives on the bleeding edge and insists on using a brand-new OS is welcome. If you have Windows 10, you can try turning it ON and Windows will present you with a list of drivers that are incompatible. This setting also exists in Windows 10, but it is OFF by default. Settings -> Update & Security -> Windows Security -> Device Security -> Core Isolation -> Memory Integrity. 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. These drivers are not needed if you're using a HEX-V2 or HEX-NET: If you have a current interface, you might have to un-check the " Install USB Drivers for Legacy Interfaces" option in the installer. We haven't done much testing, but don't anticipate any real problems with VCDS who are using any our current interfaces (HEX-V2 or HEX-NET). I have done both via Ross tech and vcds loader but after this vcds will not see the interface. With the Windows 11 release imminent, we're starting to get questions. Hi all I know there are a lot of post about VCDS showing message of interface not found, the one problem I have is that when the interface is using firmware 1.94, vcds sees it and tells me it’s status, including to update the firmware to 1.96.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |