Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging

The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.

Check out The OSR Learning Library at:

Debugging issues

rstruempfrstruempf Member Posts: 103

Since I installed the Windows update that remove HomeGroup (on my home computer), I have had various levels of dysfunction of the kernel debugger. I had originally used HomeGroup for controlling all access and sharing.

I am debugging by pressing F5 from VS, using a Hyper-V Windows 10 VM. Everything has worked flawlessly for as long as I can remember prior to the update.

The current state is: VS and OS (both host and client) are latest, not including VS 2019 preview. Installing the provisioning tools works fine, provisioning goes without a hitch, and minifilter driver deploys properly. Oh, and I got my local shared folder working with some effort.

What is not working is:

  • DbgPrint messages no longer come through
  • Cannot break into kernel
  • Adding a break point into the code hangs the computer but does not throw out to the debugger
  • Debug -> Attach won't connect

I've had similar problems in the past due to things like firewall issues (Internal virtual switch is set to Public, which blocks ICMP and other protocols, but cannot access to set to Private), but I have disabled all firewalls to no avail.

Any suggestions? The next step for me will be to start with a new VM, install Windows, provision, etc. and hope the problem is not with Windows. Any ideas would be appreciated



  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,299

    I never use the provisioning feature and only ever manually configure kernel debugging for use with WinDbg. I also never use HomeGroups, so I'm basically saying that I'm useless in helping you with your problem :) Feel the pain though, good luck!


  • rstruempfrstruempf Member Posts: 103

    Thanks for commiserating. I hope I can find the solution so I can add it to my troubleshooting list

  • Gabriel_BerceaGabriel_Bercea Member - All Emails Posts: 482

    Use hyper-v with network debugging. That works and it is super fast.
    Check out ( "here") if interested.
    I have never used that setup myself, as Scott is saying I usually configure it manually, recently using Hyper-V instead of VMWare. I decided to switch because the network debugging configuration is just so much quicker, but other than that windbg externally.
    Good luck.


  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,847

    I am debugging by pressing F5 from VS, using a Hyper-V Windows 10 VM.

    Bad idea.

    Everything has worked flawlessly for as long as I can remember ...

    Yup... until it doesn't. That's often the way. And when things stop working, it can be nigh unto impossible to diagnose the problem.

    That, and the fact that getting F5 deploy from VS to work in the first place is a hit-or-miss affair, are the reasons that we counsel our students, clients, and friends to just ignore the whole "deloy and debug using VS" and use WinDbg. With deploy, they need some very complex technology to solve what, for a human with a keyboard is a relatively simple problem (copy the file to the target, disable and re-enable the driver).


    Peter Viscarola

  • rstruempfrstruempf Member Posts: 103

    I have used F5 to deploy and debug seamlessly for a couple of years nearly. No real problems at all outside of this home computer that lost its marbles when HomeGroup went away. I've got a couple of ideas after my post in the WinDbg group. If that doesn't work, I'm going to create a new VM and start over.

    @Gabriel_Bercea Thanks for the advice. I am using Hyper-V, and love it, except for the enhanced vs non-enhanced mode mickey mouse stuff. Since the VS debugger requires the WDKRemoteUser to be logged in, and it only logs in in non-enhanced mode, and non-enhanced mode is very limited, I have to use that very limited interface when working on the VM, but I've gotten used to it.

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,847

    I have used F5 to deploy and debug seamlessly for a couple of years nearly. No real problems at all

    Well, every workman deserves the right to choose their own tools. You’ve got something that works for you, so... I hope it continues to work.


    Peter Viscarola

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA