Facing similar issue, where i have been reported with error code 1304 which says
Found legacy AddReg operation using non-relative key (HKLM\SOFTWARE\Wow6432Node\Microsoft\Cryptography\Calais\SmartCards).
The error code and warnings page suggests registry operations should be done using a relative key (HKR) and this will store the value in an appropriate location.
But replacing HKLM with HKR didn't help me to load my minidriver at all.
Smart card minidriver - InfVerif on Windows 11 24H2
The InfVerif that was introduced with Windows 11 24H2 (- see https://zcusa.951200.xyz/en-us/windows-hardware/drivers/devtest/infverif_h) provides an error if an AddReg
HKLM\SOFTWARE\wow6432Node\Microsoft\Cryptography\Calais\SmartCards is performed.
While HKLM\SOFTWARE\Microsoft\Cryptography\Calais\SmartCards was considered an exception, no exception was defined for HKLM\SOFTWARE\wow6432Node\Microsoft\Cryptography\Calais\SmartCards.
I don't understand that because according to https://zcusa.951200.xyz/en-us/windows-hardware/test/hlk/testref/14d1de87-ed46-4ee3-8fe7-2785f0c95106
a SmartCard Minidriver must also enter registry keys under HKLM\SOFTWARE\wow6432Node\Microsoft\Cryptography\Calais\SmartCards
Here the mentioned requirement:
"
When you certify on a 64-bit version of the operating system, you must also have the 32-bit version of your minidriver DLL installed on the system. You can put the DLL in the %systemroot%\syswow64 subdirectory. You must put registry entries for the 32-bit version of the DLL under HKEY_LOCAL_MACHINE\SOFTWARE\wow6432Node\Microsoft\Cryptography\Calais\SmartCards.
"
Did Microsoft forget to define an exception here? - how should developers of minidrivers proceed?
Thanks for your help !
1 answer
Sort by: Most helpful
-
hanish gopi 0 Reputation points
2024-12-24T01:56:08.2333333+00:00