First step I'd say is to import your certificate into the the debugged computer, so it doesn't warn you every time you re-upload the driver [1]. Second, use pow

First step I'd say is to import your certificate into the the debugged computer, so it doesn't warn you every time you re-upload the driver [1]. Second, use powershell remoting [2]. Pretty much all of the other steps can be established and automated with a powershell remote connection. I'm in fact surprised that microsoft hasn't updated that page to use powershell, because driver debugging is a task where it could be invaluable in helping. [1] https://blog.jourdant.me/ps-installing-drivers-from-untrusted-publishers/ https://blog.jourdant.me/ps-installing-drivers-from-untruste... [2] https://technet.microsoft.com/en-us/library/dd819505.aspx https://technet.microsoft.com/en-us/library/dd819505.aspx