Is your driver being loaded? Is it auto start? Or manual with a user mode
service that commands it to start on reboot? I’m guessing no? That will be
a requirement for your testing.
If all of that still fails… start a new hlk studio project, delete your
machine pools and start over reassigning.
For the script? It’s just a bat script that copies files to a remote target
and invokes an installer via psexec (sysinternals). Psremoting could work
too, i think, but then you’d need to have powershell installed on all your
test targets.
Also you should be fine using sc.exe, this can also be done remotely. If
your inf file has defaultinstall and or defaultuninstall sections, you can
use this to install and uninstall these types of drivers leveraging the
setupapi.dll InstallHinfSection method it exports. This is in the msdn
documentation for how to install a mini filter driver (google it 
).
You’ll figure it out, just be patient and multiply your time to complete by
10.
I’m going through this process myself and being held up by microsoft who
seems to have registered our signing credentials certificate improperly
with the submission portal. Been waiting on them 5+ days… ugh.
On Tue, Jun 27, 2017 at 4:48 AM wrote:
> Hi,
>
> It is a security software driver, similar to the one ESET and other AV
> companies are using.
>
> > If you’re loading a test project it will not show up unless you make
> specific API calls into the kernel.
> Which API is that, is there any documentation about that anywhere?
>
> > Moreover the use of sc.exe seems to be deprecated - I’m not sure how it
> relates to your problem, if it all, but you might see what other ways there
> are to do what you want to do.
>
> Are you suggesting I install a driver via other means possible? Do you
> have one in mind, which would be consistent with the WHQL testing.
>
> > Assuming you’ve installed everything correctly, try rebooting your test
> target.
>
> Done that, the driver does not show up.
>
> > I’ve found there’s a little bit of a song and dance of when these will
> sync
> up. If that doesn’t work, close out and reload hlk studio and reload your
> project.
>
> I’ve also tried that and rebooted the Windows Server 2012 entirely, then
> started HLK only to come to the same conclusion: driver is still not there.
>
> > I’ve written test deployment scripts that update the drivers and force a
> reboot on the target after the fact. Usually does the trick.
>
> Would it be possible to get the hands on the deployment script (are you
> using Ansible, PSRemoting or anything else). If you cannot do that, can you
> at least let me know how are you updating the driver? Also, after
> restarting the target PC, do you do anything special to HLK or does it just
> pick up the new driver automatically (since there is no refresh of any kind
> in HLK).
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: <
> http://www.osronline.com/showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:>