Problem with recognising DCH after upgrade from Standard drivers #22

Closed
opened 2022-01-19 12:03:36 +01:00 by fyr77 · 0 comments
fyr77 commented 2022-01-19 12:03:36 +01:00 (Migrated from github.com)

When Standard drivers are upgraded to DCH, EnvyUpdate may still think Standard drivers are being used.

There are currently 2 checks in place for DCH:

  1. Registry, which is always correct, but access might be blocked by Windows. I have not yet understood what this depends on.
  2. Existence of file nvsvs.dll in system32, which does not exist after upgrading to DCH.

Checking for a unique file would be optimal, since Registry support is flaky. I need to find out which files are truly unique to Standard or DCH.

When Standard drivers are upgraded to DCH, EnvyUpdate may still think Standard drivers are being used. There are currently 2 checks in place for DCH: 1. Registry, which is always correct, but access might be blocked by Windows. I have not yet understood what this depends on. 2. Existence of file `nvsvs.dll` in system32, which does not exist after upgrading to DCH. Checking for a unique file would be optimal, since Registry support is flaky. I need to find out which files are truly unique to Standard or DCH.
This repository is archived. You cannot comment on issues.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: fyr77/EnvyUpdate#22
No description provided.