Windows 10 ISO mounting freezing issues with 1.26.31

[jbofhfkfkj]

Environment
-Windows 10 IoT Enterprise LTSC 2021 x64 19044.7807 (clean installed)
-Veracrypt 1.26.31

Issue
When trying to mount a windows installation image (.iso), the windows file explorer freezes and is unresponsive whatsoever. Task manager and even reboot is unresponsive. The time is exactly 160s until the freezing resolves automatically. Tried trouleshooting with claude code and GPT codex, but failed due to the session being flagged with cybersecurity.
According to claude code, the vhdmp.sys seems to be the reason. The type of ISO matters. Ordinary ISOs(which are not Windows installation images) open totally fine regardless of their size. Windows installation images are the only type that make the explorer freeze and crash.
This symptom has been reproduced in two different PCs, all having Windows 10 IoT Enterprise LTSC 2021 x64 19044.7807 with Veracrypt 1.26.31 installed. This symptom does not happen when Veracrypt is not installed, or when 1.26.29 is installed. I formatted and clean installed windows for each test, and Veracrypt 1.26.31 seems to be the one most likely that's causing this issue.

Please tell me which log/dumps I need to provide for further detail.

How to reproduce
-Acquire Windows 10 IoT Enterprise LTSC 2021 x64 image (either from internet archives or m@ssgr@ve)
-Clean install, and perform windows updates, reboot, and check that no updates remain.
-Install veracrypt
-Try opening any windows iso file
-If crash doesn't occur, try mounting a veracrypt encrypted drive, put the iso file inside that drive, and double click to open it.

[jbofhfkfkj]

I just clean installed the base Windows 10 IoT Enterprise LSC 2021 x64 image, performed absolutely nothing(no updates, no driver installation, etc), and installed VeraCrypt 1.26.29.
I mounted a veracrypt encrypted drive, and opened a windows iso inside that drive by double clicking, and the exact same freeze/crash appears.
Winver shows 19044.1288.
Opening non-windows iso files in the exact same situation is perfectly normal. I have no idea why this happens.

[jbofhfkfkj]

Finally pinned down the exact cause. Posted the issue on github: https://github.com/veracrypt/VeraCrypt/issues/1995