Application Packaging Preparation, Check for Unsigned Drivers
Filed under:
3rd Party Products, Basics
Submitted by riva11 on 22 June, 2007 - 10:34.
For correct application packaging, particular attention should be paid to check if all drivers are Microsoft Windows Certified. In fact, some issues can be tracked to the inclusion of unsigned drivers.
I use File Signature Verification utility (Sigverif.exe) to check -- in advance -- all drivers designed for Microsoft Windows and to identify drivers that are not certified.
This tool is a free standalone graphical program supplied in Windows XP and is an easy and fast way to detemine signed and unsigned drivers running in the computer.
Read more details and a short guide in the original Microsoft article: Unsigned Drivers - Use Sigverif.exe.
A short tip in this article in case you identify an unsigned driver:
When you determine what drivers are unsigned, create a folder in which to place the unsigned drivers. Typically, SysDriversBak is an easy folder name to remember.
Restart your computer without the unsigned drivers in the Winnt\System32\Drivers folder and test your program or other functionality to see if the error messages or issues occur.
Hardware and Software Third-Party Vendor Contact List
Also if you need to check details about manufacturer of your program, view the article in the Microsoft Knowledge Base:
- Hardware and Software Third-Party Vendor Contact List, A-K
- Hardware and Software Third-Party Vendor Contact List, L-P
- Hardware and Software Third-Party Vendor Contact List, Q-Z
(21 votes)
A really useful tool
Thanks Riva,
For wonderful update.
What method you generally follow to package unsigned driver based application. I prefer to give internal call to driver executable inside MSI. You have any other alternative than registry update.
cool tool
thanks this work very nice
Good tool
Thanks mate this really cool
Regards
Darshan
MCSE,CCNA,MCTS,ITIL V3