*Not* getting unsigned driver warning on unsigned driver install

Discussion in 'Windows Vista Drivers' started by Gary R. Van Sickle, Aug 17, 2007.

  1. Hi folks,

    I'm having what is known as a "high-class problem": I am *not* getting the
    unsigned driver warning dialog (you know the one, the box telling you that
    your drivers aren't signed and bad things are going to happen etc etc) when
    installing unclassified USB drivers that are most assuredly not signed (these
    drivers don't even have a .cat file yet). This is on both W2K SP4 and XP
    SP2. The "System Properties/Hardware/Driver Signing/Driver Signing Options"
    is set to "Warn", and "Make this the system default" is set.

    The drivers are pre-installed via a DIFx-based application (FWIW this is
    Jungo WinDriver with customized INFs, and the installer is the wdreg.exe
    utility bundled with it). On the first plug-in of a device, the behavior is
    slightly different on 2K vs XP.

    - On 2K, the device is plugged in, and two “Found New Hardware†“alert
    boxes†pop up in very quick succession in the center of the screen and
    disappear. These appear to be the W2K equivalent to the system tray bubbles
    in XP. The user is never asked to click on anything, and the device is ready
    for action.

    - On XP, the device is plugged in, you get some system tray bubbles, then
    the usual "Found New Hardware Wizard" pops up, and the user has to click
    through a few Wizard pages before the device is installed. At no time though
    does the "Warning! Unsigned Driver!" box show up.

    What's going on here? Does DIFx somehow bypass the warning box? Do other
    people see this? This is completely new behavior to me and I don't know what
    to make of it.
     
    Gary R. Van Sickle, Aug 17, 2007
    #1
    1. Advertisements

  2. It is possible to turn off the warning while installing the software and turn
    on after the installation is complete. Check for this option.

    --
    Sincerely,
    Maruf Maniruzzaman,
    Software Engineer,
    KAZ Software Limited,
    Dhaka, Bangladesh.
    http://www.kaz.com.bd
    http://www.kuashaonline.com
     
    Maruf Maniruzzaman, Aug 19, 2007
    #2
    1. Advertisements

  3. If your driver has a custom setup class, it won't cause "unsigned driver"
    warning, at least in XP and W2K.
     
    Alexander Grigoriev, Aug 19, 2007
    #3
  4. Installing a driver is simple as copying a file in the system32\drivers and
    setting a registry node. afterwards you are free to load it and do any
    initialization. Windows XP does not stop anything.

    --
    Sincerely,
    Maruf Maniruzzaman,
    Software Engineer,
    KAZ Software Limited,
    Dhaka, Bangladesh.
    http://www.kaz.com.bd
    http://www.kuashaonline.com
     
    Maruf Maniruzzaman, Aug 20, 2007
    #4
  5. Gary R. Van Sickle

    Don Burn Guest

    This is only true for a legacy driver. If you hack the registry to get the
    data for a PNP driver you are likely to corrupt the system.


    --
    Don Burn (MVP, Windows DDK)
    Windows 2k/XP/2k3 Filesystem and Driver Consulting
    Website: http://www.windrvr.com
    Blog: http://msmvps.com/blogs/WinDrvr
    Remove StopSpam to reply
     
    Don Burn, Aug 20, 2007
    #5
  6. Ohhhhh, ohohohoh. Ok, thanks. Creating a silent setup (i.e. getting rid of
    the Wizard that you have to click through in XP) still requires that the
    driver be signed though, correct?
     
    Gary R. Van Sickle, Aug 20, 2007
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.