WinVerifyTrust bcrypt.dll - Debug Mode

[Ernaw]

Hey,
I'm having some problems when debugging the solution. Maybe I missed something. (solution is clean)

[AlSch092]

What operating system? There was a similar issue opened a while ago and it had to do with them using an older OS (Win7), however it's difficult for me to debug this since I don't have access to any older OS versions. I believe it was specifically that one of the structures used in the WinVerifyTrust routine has different offsets, your best bet is to find a working example of signature verification for your specific OS and then replace the code with the example's.

[Ernaw]

I'm using windows 11 (24H2), that's what's so strange

[AlSch092]

Is bcrypt.dll the only file that causes this? I can't find any information online about this particular case, it looks as if it's a null pointer issue due to writing to 0x00..24, which implies a member of a struct is being written to but the object is NULL. We also can't seem to wrap the WinVerifyTrust call in a __try/__except block due to stack unwinding.

Although this isn't a good solution, you could add a check to see if the file is bcrypt.dll and skip over it if so (assuming it's the only file causing this issue). I'll see if I can get a dual boot of Win11 going, since I'm on 10 currently, but unfortunately for now your best option is probably skipping over whatever files are failing.

Cheers