Skip to content

Commit

Permalink
fix: set Debug Print Filter to dword:0000000f
Browse files Browse the repository at this point in the history
The registry entries for DbgView aren't working.
  • Loading branch information
Jamlee committed Dec 13, 2024
1 parent 534c5ba commit 25550bb
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 8 deletions.
11 changes: 6 additions & 5 deletions _posts/2018-08-21-hypervisor-from-scratch-part-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,15 +225,16 @@ The latest thing I remember is enabling Windows Debugging messages through the r

Just perform the following steps:

In the **Regedit**, add a key:
Save the following content as `dbgview.reg`.

```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter
```
Windows Registry Editor Version 5.00
Under that, add a DWORD value named IHVDRIVER with a value of 0xFFFF.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter]
"DEFAULT"=dword:0000000f
```

Reboot the machine, and it's good to go.
Double-click on `dbgview.reg`. Reboot the machine, and its good to go.

## **Nested-virtualization**

Expand Down
9 changes: 6 additions & 3 deletions _posts/2018-09-03-hypervisor-from-scratch-part-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -237,13 +237,16 @@ Unfortunately, for some unknown reason, I'm unable to view the result of `DbgPri

As I mentioned in [part 1](https://rayanfam.com/topics/hypervisor-from-scratch-part-1/):

In "regedit.exe", add a key:
Save the following content as `dbgview.reg`.

```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter]
"DEFAULT"=dword:0000000f
```

Under that, add a DWORD value named IHVDRIVER with a value of 0xFFFF.
Double-click on `dbgview.reg`. Reboot the machine, and it’s good to go.

This method should solve the problem, but if the problem still persists, we have another option. For this purpose, we can use WinDbg to find a Windows Kernel global variable called `nt!Kd\_DEFAULT\_Mask`. This variable is responsible for showing the results in DbgView. It has a mask that I'm not aware of, so I just put a `0xffffffff` into it to simply make it show everything!

Expand Down

0 comments on commit 25550bb

Please sign in to comment.