Can't verify publisher for mf.sys

I've got a multiportSerial inf that uses mf.inf/mf.sys to enumerate x number
of serial ports. When I use this inf for my device, Server 2008 complains
that "Windows can't verify the publisher of this driver software". If I say
to install the driver software anyway then it will enumerate all my serial
ports correctly and it's happy to install the serial driver I have written
for the child devices.

What do I need to do in order to get the mf.inf/mf.sys portion of my install
to work without user interaction?

You need to sign your mf.sys file (and mf.cat) with an Authenticode Code
Signing Certificate issued to your company.


"skiloup" wrote:

> I've got a multiportSerial inf that uses mf.inf/mf.sys to enumerate x number
> of serial ports. When I use this inf for my device, Server 2008 complains
> that "Windows can't verify the publisher of this driver software". If I say
> to install the driver software anyway then it will enumerate all my serial
> ports correctly and it's happy to install the serial driver I have written
> for the child devices.
>
> What do I need to do in order to get the mf.inf/mf.sys portion of my install
> to work without user interaction?

It uses the mf.sys that is distributed with the OS. Are you suggesting that
I sign mf.sys as my own and install it that way?

"Bo Skjoett" wrote:

> You need to sign your mf.sys file (and mf.cat) with an Authenticode Code
> Signing Certificate issued to your company.
>
>
> "skiloup" wrote:
>
> > I've got a multiportSerial inf that uses mf.inf/mf.sys to enumerate x number
> > of serial ports. When I use this inf for my device, Server 2008 complains
> > that "Windows can't verify the publisher of this driver software". If I say
> > to install the driver software anyway then it will enumerate all my serial
> > ports correctly and it's happy to install the serial driver I have written
> > for the child devices.
> >
> > What do I need to do in order to get the mf.inf/mf.sys portion of my install
> > to work without user interaction?

If anybody else encounters this problem the solution is as simple as creating
a cat file from the .inf even though it doesn't directly include any driver
files. That then gives you something that can be signed and everything plays
nice. I thought I had tried this previously, but evidently I didn't.

Thanks Bo for your comments. They definitely pointed me in the right
direction.