This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 17%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
How to get DbgPrint to show in Host debug window? Installation is a host wdk v11 VS2022v17_0 install, ndislwf, w10p21H2 host and a target
wdk 11, w10p21H2. Debug seems to just start after deploy and Break All does not work to insert a mask command(worked in previous wdk but still saw no DbgPrints) and tried a 'Default Print Filter" registry thing in target that did not seem to do anything.
Please show the specific changes you made to the registry for the default print filter.
I followed https://www.osr.com/getting-dbgprint-output-appear-windows-vista-later , and tried 0xf and 0xffffffff with reboots. The previous wdk and vs2019 would do a break so I could enter a 0x8 mask, but I saw nothing as the ndislwf had already loaded. That version was flaky in that the deploy complained of two invalid parameters were passed to a program in the deploy, and I read it does not work if w10 greater than 1507. Turned off Defender firewalls completely with no improvement.
I would add that the 2019 and 2022 were done on clean w10pro installs on host and target and not coexisting.