Windows Hardware Compatibility Program (WHCP) - issue?

Eigenharp
1

note: forgive the generic title, as whilst Im posting this for Eigenharp’s its a possible issue for other device with custom windows drivers, so I wanted a ‘catch all’

see below, for where this info comes from.
also apologies, for long post, but its important to have context here.

BTW: if anyone does encounter this issue (or not) with the Eigenharp driver, please post below,
if you do, and then use the solution detailed below, also let us know - did it work?
basically, if would be really useful to get some first hand experience on this.

Issue

Windows 11 - April 26 update, no longer trusts legacy drivers, and will disable after 100 hours.

https://news.thewindowsclub.com/windows-11-will-no…/

I don’t have this issue !

ok, the odd bit is, old drivers are put into a 100 hour / 3 reboots evaluation window BEFORE they are deactivated. so, you may not see notice it for quiet a while… :frowning:

Does it affect my devices ? (including Eigenharp)

Im not actively using my windows machine, so I don’t know.
basically, its going to affect any older driver, that not been updated to newer signing.

I assume this will therefore affect the eigenharp driver used by ALL eigenharp models on windows (pico, alpha / tau).

so I want to get this info out there, just in case.

(obviously this only affects windows, not mac/linux)

Solution?

so, yeah, there is a solution, disable the new WHCP policy

  1. Disable Secure Boot
  2. Mount the EFI partition
  3. Delete the WHCP policy files
  4. Re‑enable Secure Boot

the facebook post include a project/script that will automate this.

https://github.com/x1nv/disable-windows-WHCP-policy

Important note :

I have NOT verified this, nor do I know if this has any side effects and can be trusted
that said, its a simple script, and you can verify its contents.

Caveat

as I said, Ive not tested this, and I’ve not seen this issue yet, which is why Im supplying full source of this information (see post below).

however, I think its very important, as it does appear eigenharps could stop working on windows 11, and users might be very confused why suddenly ‘now’.

Future

for EigenD 3 (not released) my plan is to move to windows to a user-land implementation based on libusb drivers. Im these are, or will be, WHCP compliant.

I was already ‘concerned’ we were reliant on an old (32bit) driver that we do not have the source code for, so frankly, whilst I did not know this was in the works, I cannot say it surprises me… its the issue with relying old software, it will eventually break.

2

its a post in the “Access Virus TI”, facebook group,
(so you likely have to join, which is why I replicating here(

context, in that group there are a number of post from users saying that the Virus driver has stopped working, starting from May 26, so a month after the windows updare.

facebook post by Erik Å. Ingmanndsen - link

1 Like