Open vif opened 8 months ago
Do you have AV software installed? If so can you add an exemption for TTD.exe and TTDInject.exe? Module selective recording depends on being able to change module memory from execute to non-execute and back. AV software may trip on this.
@KenSykes I'm running in a corporate environment so some things are locked down. Only Windows Defender should be running.
Just to get TTD working at all, I needed to make sure I was part of the "Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights Assignment->Debug Programs" in the group policy editor.
Is there another right / etc. that TTD or TTDInject might implicitly rely on?
Sorry for not coming back to this. The version you have, 1.11.316, has a regression with module recording. We fixed this in 1.11.323 (not released). We will be releasing the new version this week (1.11.410) which will include the module recording fix.
Version 1.11.410 is available now through winget and https://aka.ms/ttd/download. Windbg has also been updated.
Let us know if you still have issues.
Recording a program run works as long as I'm trying to record all the instructions. It stops working when I try to specify some modules (even a single one).
Here's the output of the .out file generated, I've redacted the
program
name and paths..