Win 10, signing, driver runs, but OS says unsigned.

NTDEV
1

Hello, Guys.

We have a driver which have passed HLK tests is signed with EV certificate through a new dashboard https://developer.microsoft.com/en-us/dashboard/hardware .

The problem is that after installation after some time the message appear:
“A digitally signed driver is required”
“Windows blocked the installation of a digitally unsigned driver. Uninstall the program or device that uses the driver and check the publisher’s website for a digitally signed version of the driver”
This warning scaring our customers and they often refuse to install our product.

In the same time the driver loads well and works correctly. I would understand, if the driver would not be loaded at all, but the driver is runing.

We opened a MSSolve case on this issue a couple months ago. MS guys confirmed that the driver is signed correctly, also they re-checked sys,inf,cat,hlkx and confirmed that they could not see any wrong with the files,
but in the same they are able to see the issue. Also we have found that when we do installing of on Windows 10 we can see the same warning; this info has passed to MSSolve team as well.

The result for now is that we know where from that MessageBox appears:
taskhostw.exe
and we even have a call stack with raw arguments of the MessageBox, but we still don’t know why it appears and how to fix it.

So, Guys,
Does anyone faced to the similar issue, when HLK signed driver is running well, but Windows 10 says it is not signed on installation?
Maybe you have the idea on how to fix this issue?
Or this issue already was discussed, but I cannot find it?

Thanks,
Alexey Barabash

2

What does setupapi.dev.log say wrt the installation of your driver?

Bent from my phone

From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com
Sent: Tuesday, May 2, 2017 8:48:30 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Win 10, signing, driver runs, but OS says unsigned.

Hello, Guys.

We have a driver which have passed HLK tests is signed with EV certificate through a new dashboard https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fdashboard%2Fhardware&data=02|01|Doron.Holan%40microsoft.com|480986a7f33d43910e0908d49172ad89|72f988bf86f141af91ab2d7cd011db47|1|0|636293369106801751&sdata=RcrUuw0w0akCSxm8BPngshaOvS%2F%2FZNNA1ixsEJLiIHg%3D&reserved=0 .

The problem is that after installation after some time the message appear:
“A digitally signed driver is required”
“Windows blocked the installation of a digitally unsigned driver. Uninstall the program or device that uses the driver and check the publisher’s website for a digitally signed version of the driver”
This warning scaring our customers and they often refuse to install our product.

In the same time the driver loads well and works correctly. I would understand, if the driver would not be loaded at all, but the driver is runing.

We opened a MSSolve case on this issue a couple months ago. MS guys confirmed that the driver is signed correctly, also they re-checked sys,inf,cat,hlkx and confirmed that they could not see any wrong with the files,
but in the same they are able to see the issue. Also we have found that when we do installing of on Windows 10 we can see the same warning; this info has passed to MSSolve team as well.

The result for now is that we know where from that MessageBox appears:
taskhostw.exe
and we even have a call stack with raw arguments of the MessageBox, but we still don’t know why it appears and how to fix it.

So, Guys,
Does anyone faced to the similar issue, when HLK signed driver is running well, but Windows 10 says it is not signed on installation?
Maybe you have the idea on how to fix this issue?
Or this issue already was discussed, but I cannot find it?

Thanks,
Alexey Barabash

—
NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

3

Hi, Doron.

All looks good:

>> [SetupInstallFromInfSection - DefaultUninstall]
>> Section start 2017/05/02 19:07:01.400
cmd: C:\WINDOWS\system32\rundll32.exe setupapi,InstallHinfSection DefaultUninstall 132 C:\Program Files\KineticFAM\FAMv4.inf
<<< Section end 2017/05/02 19:07:01.401
<<< [Exit status: SUCCESS]

inf: DelService=FAMv4,0x200 (FAMv4.inf line 39)
dvi: Deleted service ‘FAMv4’.

>> [SetupQueueCopy]
>> Section start 2017/05/02 19:07:56.821
cmd: C:\WINDOWS\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 C:\Program Files\Online Backup\FAMv4.inf
<<< Section end 2017/05/02 19:07:56.822
<<< [Exit status: SUCCESS]

flq: Copying ‘C:\Program Files\Online Backup\FAMv4.sys’ to ‘C:\WINDOWS\system32\DRIVERS\FAMv4.sys’.

>> [SetupInstallFromInfSection - DefaultInstall]
>> Section start 2017/05/02 19:07:56.880
cmd: C:\WINDOWS\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 C:\Program Files\Online Backup\FAMv4.inf
<<< Section end 2017/05/02 19:07:56.880
<<< [Exit status: SUCCESS]

inf: AddService=FAMv4,FAMv4.Service (FAMv4.inf line 27)
dvi: Add Service: Created service ‘FAMv4’.

>> [SetupInstallFromInfSection - FAMv4.Service]
>> Section start 2017/05/02 19:07:56.936
cmd: C:\WINDOWS\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 C:\Program Files\Online Backup\FAMv4.inf
<<< Section end 2017/05/02 19:07:56.937
<<< [Exit status: SUCCESS]
========

Thanks,
Alexey