ShowSystemTimeOnDebugMessages
to FALSE
then it no longer sends date and time along with each message (These messages along with time are used in internal logging functions, and it's not exposed to the script engine).UseWPPTracing
to TRUE
. After that, you no longer see any message in HyperDbg, and instead, you can see the messages in a WPP Tracing compatible app.TRUE
then it uses DbgPrint instead of HyperDbg's message tracing or WPP Tracing. Keep in mind that DbgPrint is not usable in most events as it's not vmx-root compatible.UseDbgPrintInsteadOfUsermodeMessageTracking
to FALSE
TRUE
. However, it kills the performance as sending buffers to the user-mode involves various and heavy functions.FALSE
(default), then HyperDbg accumulates (~5 or more) messages, and when the buffer is full, it sends the buffer to the user-mode CLI or GUI.TRUE
then it's like to add imm yes
to each event command, and if you set this option to FALSE
then it's like to add imm no
to each command.imm yes
and imm no
.Tag
value.