Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Forcing Use of Unsigned Drivers

- - - - -

  • Please log in to reply
17 replies to this topic

#1
joemarriott

joemarriott
  • Members
  • 5 posts
G'day,

Does anyone know a way to force Windows XP to use an unsigned driver file even if a signed one exists in drivers.cab?

The situation is:
- The Windows XP drivers.cab file includes a driver file E100b325.sys for an intel nic. Version 5.41.22.0000

- I have an updated signed intel driver that installs fine when its path is included in OemPnPDriversPath etc. Its version is 7.1.8.0

- I would like to modify the inf file that ships with this updated driver to force the Wake on Lan Settings of the card. Once I modify the inf file I can install the driver successfully using the GUI, but if I try to get the driver to install via unattend.txt, Windows uses the one from drivers.cab instead.

Please let me know if you would like more information,
Much appreciated.


How to remove advertisement from MSFN

#2
muevelonyc

muevelonyc

    USB Key Freak

  • Members
  • Pip
  • 67 posts
In the winnt.sif file in:
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore

the last 2 lines will let it happen.

#3
buletov

buletov

    Senior Member

  • Members
  • PipPipPipPip
  • 518 posts
what is this?

NonDriverSigningPolicy = Ignore

#4
prathapml

prathapml

    Follow the rules please :-)

  • Patrons
  • 6,791 posts
  • OS:Windows 8 x64
  • Country: Country Flag

NonDriverSigningPolicy = Ignore

Maybe it refers to signing of non-driver related files (like signed hotfixes/patches, etc.).

#5
buletov

buletov

    Senior Member

  • Members
  • PipPipPipPip
  • 518 posts
well i'll throw it in anyhow...it won't hurt :)

#6
keul

keul

    Newbie

  • Members
  • 37 posts
From MSDN :

Description
Determines what should happen when an attempt is made to install any nondevice driver software that has not been certified.

It Seems that the default setting for it is "Ignore"

More information here:
Unsigned non-driver installation behavior
No Driver Signing Warning Is Displayed When You Install the Device Driver
Driver Signing Registry Values Cannot Be Modified Directly in Windows

#7
Bilou_Gateux

Bilou_Gateux

    Powered by Windows Embedded

  • Members
  • PipPipPipPipPip
  • 766 posts
  • If the network adapter supports power management, WakeOnLAN can be enabled on the Power Management tab in the network adapter properties by clicking to select the Allow this device to bring the computer out of standby check box.
  • Right-click My Network Places, and choose Properties. Double-click Local Area Connection, then click the Properties button. Near the bottom of the Local Area Connection Properties window, you should see a checkbox next to Show Icon in taskbar when connected. Check that, click OK, and you're done.
If you own a HP/Compaq box, you can use their own small tool called nictool.exe that do both modifications.

#8
ralexand88

ralexand88

    Junior

  • Members
  • Pip
  • 69 posts
No one said if this entry works or not. Does anyone know for sure?

NonDriverSigningPolicy = Ignore

#9
prathapml

prathapml

    Follow the rules please :-)

  • Patrons
  • 6,791 posts
  • OS:Windows 8 x64
  • Country: Country Flag

No one said if this entry works or not.

Even the purpose of that entry is not known for sure. So whether it works or not, is a moot point.

Most people just put both (driver-signing, and non-driver-signing) values into their winnt.sif just to be sure - and even then, it seems to work for some and not work for others.

#10
keul

keul

    Newbie

  • Members
  • 37 posts
So, did anyone manage to install new non-whql drivers when old whql drivers are also present in drivers.cab during setup ?

I made a lot of tests with WinXpSP2 and couldn't obtain positive results.

My winnt.sif contains "DriverSigningPolicy = Ignore" and "NonDriverSigningPolicy = Ignore", I also use WatchDriversSigningPolicy.exe from Pyron, but these commands are only usefull to install non whql drivers that are NOT present in drivers.cab

I seriously doubt it can work, according to what Msdn says here:

If you are using the entry DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that is distributed with Windows XP or Windows Server 2003, Setup installs the signed Windows XP driver instead of the unsigned drivers, in accordance with the ranking process used by the operating system.

I verified what is said here in setupapi.log after install : (it may not be exactly what you have, I traducted it from french)

#I022 "PCI\VEN_10DE&DEV_0282" found in "C:\WINDOWS\Inf\nv4_disp.inf";.... #I023 Section d'installation réelle: nv4.Rang : 0x00002001...
#I022 "PCI\VEN_10DE&DEV_0282" found in "C:\Drivers\video\nVidia\nv4_disp.inf";...
#I087 Driver node can't be trusted, rank changed from 0x00002001 to 0x0000e001.


So after rank has been changed, windows automatically uses his own whql driver...

#11
joemarriott

joemarriott
  • Members
  • 5 posts
Thanks for the replies so far people.

Would anyone know how write an assembly code hack that could be used to disable / spoof the windows code that calculates the ranking of a driver file?

For example opening a dll or exe in a hex editor and modifying a few bits then saving the updated file to the windows setup folder (i386).

#12
keul

keul

    Newbie

  • Members
  • 37 posts
That's what I'm trying to do right now :rolleyes:

#13
prathapml

prathapml

    Follow the rules please :-)

  • Patrons
  • 6,791 posts
  • OS:Windows 8 x64
  • Country: Country Flag
Since you already have the driver file INF, you can directly replace the unnecessary older drivers in the driver CABs of windows installation source. This is just an outline, you'll need to explore the method yourself....
nLite allows you to merge the DRIVER.CAB and SP2.CAB. To do this, it first extracts the contents of both CABs to a folder. What you can do is to replace the original older INFs in the folder with your updated driver INF (and associated files). I've successfully done this with the nVidia drivers. The added benefit of doing this, is that you don't have to have 2 copies of the same driver (one old, one new), and that it is compressed too.

#14
joemarriott

joemarriott
  • Members
  • 5 posts
I'm not sure which is the lesser evil, an assembly code hack, or re-compiling drivers.cab......

#15
nitro322

nitro322

    Advanced Member

  • Developers
  • 387 posts
Has anyone figured this out, yet? I have this exact same problem, although it's with the nVidia drivers rather than a network card. I'm sure many others here must be using an nVidia card - how do you force Windows to install the newer, but unsigned, drivers rather than the built-in ones?

Thanks.

#16
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Members
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag

Has anyone figured this out, yet?  I have this exact same problem, although it's with the nVidia drivers rather than a network card.  I'm sure many others here must be using an nVidia card - how do you force Windows to install the newer, but unsigned, drivers rather than the built-in ones?

Thanks.

By removing the ones in Drivers.cab ;)

If you really want to go advanced, take a look at this guide and use CTRL+F to search for "video", you'll see ;). I would NOT recommend this, too much work!


Bâshrat the Sneaky

#17
nitro322

nitro322

    Advanced Member

  • Developers
  • 387 posts
Shoot, I was afraid that was going to be the answer.

Ok, if you don't mind, I could use a little bit of assistance here. I can unpack drivers.cab file with WinRAR (are there any other cab files I need to worry about?), and I'm sure I can identify the old driver files with a little work. However, how do I recreate the cab file once I'm finished? WinRAR can't do this, and I don't recall seeing any other programs to create generic MS cab files.

EDIT: After a little more research I found the Microsoft Cabinet SDK, which includes makecab.exe. This should do the trick, right? Anything special I should be away of?

Thanks.

#18
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Members
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag
If I remember this well (and I'm quite sure I do :P), nLite can remove drivers out of Drivers.cab for you. You just have to unselect the drivers you don't want to be there.

P.S.: makecab is standard included in Windows XP ;)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN