Launch a application via device Co-installer will fail the WHQL HCK test.

Question

Our device need to install a value-added software with our device ,so we implemented a device co-installer to launch a application to download our software from internet. When we tested the driver and co-installer, it can work fine when we install the driver manually , but when we try to get the WHQL certification, and then the HCK test will fail with this kind of co-installer mechanism . Can someone know why ? We used CreateProcess API to launch our software, is it the reason for HCK failed?

Answer 1

Not sure what is causing the failure, but the why is to allow server side installs which makes launching a process problematical at best.

---

Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

Answer 2

Supported ways to install value-add software are

• Windows Store Device Apps - More information about device apps can be found at http://msdn.microsoft.com/library/windows/hardware/br259114 under the "Design Great Hardware Experiences" section.
• Finish Install Actions - http://msdn.microsoft.com/en-us/library/windows/hardware/ff544940(v=vs.85).aspx 
• Finish Install Wizard Pages - http://msdn.microsoft.com/en-us/library/windows/hardware/ff544942(v=vs.85).aspx

Windows Store Device Apps are new with Windows 8 and will not work on previous operating systems.  I don't believe finish install wizard pages are commonly used anymore due to finish install actions providing greater flexibility, though finish install actions were only added in Vista so they are not available as an option if you are supporting XP.  The documentation about finish install actions and finish install wizard pages may not be updated yet for changes made in Windows 8.  Some of those changes are described at http://social.msdn.microsoft.com/Forums/en-US/wdk/thread/aef6bbc3-91af-4207-a636-14900870aba4/#aedb5d93-de9d-4db0-8199-cc322811c5bb