Changes between Version 1 and Version 2 of Ticket #19060, comment 3
- Timestamp:
- Dec 7, 2019 5:41:29 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19060, comment 3
v1 v2 9 9 10 10 It stands to reason that, with your fix in place, some additional code is running, and I see that it reports fWinVerifyTrust=1 in the log for this DLL. But, the key question is, what happens internally as a result of this to "approve" the DLL? I.e., since it's already loaded, the answer is not "load it." So, what exactly happens when fWinVerifyTrust reports success to allow the DLL to run??? ... because I think that's not happening. 11 12 (Note that I've followed up in this ticket rather than the original because I believe the "missing steps" to fully enable/initialize the DLL should be run as a result of the fix you added for this ticket.)