multiple errors when opening VeraCrypt

[mehgcap]

Steps to reproduce:

1. Download VeraCrypt. You want the portable version, at least that's what I used and am testing with. Downloads page, or direct link to 1.26.15.
2. Run the installer. It's a self-extracting archive, so just agree, choose a location, and let it extract.
3. Open the folder if it didn't do so automatically and run VeraCrypt.exe.

Actual behavior:

NVDA plays a bunch of error tones in very fast succession, pauses, then does it again. The log has a whole bunch of the following:

ERROR - RPC process 33108 (VeraCrypt.exe) (21:38:32.924) - Dummy-5 (14320):
Thread 79c4, build\x86\common\apiHook.cpp, apiHook_hookFunction, 36:
DetourAttach for function at address 0X76B5A280 with  new function at address 0X6F000D60 failed with 8

At the end of a long list of such messages is a freeze recovery:

INFO - watchdog.waitForFreezeRecovery (21:38:33.015) - watchdog (16316):
Starting freeze recovery after 0.5001169999995909 seconds.
INFO - watchdog.waitForFreezeRecovery (21:38:33.066) - watchdog (16316):
Recovered from freeze after 0.550960300002771 seconds.

There are at least two freeze recovery messages, the first 0.5 or so seconds, the second 2.2 or so.

Expected behavior:

NVDA shouldn't do this. It doesn't impact anything, as NVDA operates as expected once the window is open, but it's odd.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

2024.4 RC 1

Windows version:

Windows 11, 24H2

Name and version of other software in use when reproducing the issue:

VeraCrypt portable 1.26

Other information about your system:

No braille display in use, the screen is not blacked out. I'm using the official, built-in ESpeak synthesizer. I don't know what else might be useful.

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, this has happened since I tried VeraCrypt in August of 2024.

If NVDA add-ons are disabled, is your problem still occurring?

Yes.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.

[gerald-hartig]

The impact to NVDA users appears to be low. No workaround is possible from our side. The developers of VeraCrypt would need to look at this.