Attestation signing is all that is needed for a driver to load on Server
2016. For that matter, it works for all recent platforms, not just
Windows 10. So I’m not quite sure what they mean in the link by ‘it will
not work’.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: xxxxx@hotmail.com
To: “Windows System Software Devs Interest List”
Sent: 2/28/2017 7:01:01 AM
Subject: RE:[ntdev] Nano Server
>Well, according to MSFT:
>https://msdn.microsoft.com/en-us/windows/hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release
>“An attestation signed driver will only work for Windows 10 Desktop. It
>will not work for other versions of Windows, such as Windows Server
>2016,Windows 8.1, or Windows 7.”
>
>Of course if this were wrong it wouldnt surprise me.
>
>
>(Have to say Attestation Signing is news to me, I didnt know MSFT had
>changed the way Windows 10 works. )
>
>—
>NTDEV is sponsored by OSR
>
>Visit the list online at:
>http:
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:></http:>
My problem is with Nano Server. The drivers run on W2K16 (and all older OSes) but not on Nano Server.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of PScott
Sent: Tuesday, February 28, 2017 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re[2]: [ntdev] Nano Server
Attestation signing is all that is needed for a driver to load on Server 2016. For that matter, it works for all recent platforms, not just Windows 10. So I’m not quite sure what they mean in the link by ‘it will not work’.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: xxxxx@hotmail.com
To: “Windows System Software Devs Interest List”
Sent: 2/28/2017 7:01:01 AM
Subject: RE:[ntdev] Nano Server
>Well, according to MSFT:
>https://msdn.microsoft.com/en-us/windows/hardware/drivers/dashboard/att
>estation-signing-a-kernel-driver-for-public-release
>“An attestation signed driver will only work for Windows 10 Desktop. It
>will not work for other versions of Windows, such as Windows Server
>2016,Windows 8.1, or Windows 7.”
>
>Of course if this were wrong it wouldnt surprise me.
>
>
>(Have to say Attestation Signing is news to me, I didnt know MSFT had
>changed the way Windows 10 works. )
>
>—
>NTDEV is sponsored by OSR
>
>Visit the list online at:
>http:
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:></http:></http:></http:>
If the system you’re using has UEFI Secure Boot enabled, try turning it off.
-------- Original Message --------
Subject: [ntdev] Nano Server
From: Bill Wandel
To: Windows System Software Devs Interest List
Date: 2/27/2017 9:39 AM
> I created a Nano Server image and installed our drivers. The drivers are
> filter drivers and have been signed through the MS portal. These drivers load
> and run fine on W2K16 but will not load on Nano Server. Does Nano Server
> require running the HCK tests?
xxxxx@hotmail.com wrote:
Every kernel component has to be MSFT signed in order to load (since win 7 AFAIR), I guess Nano isnt going to be any different.
Not so. Kernel components need to be signed by someone on all 64-bit
systems, but the requirement to have a Microsoft signature did not arise
until the “anniversary release” 1607 of Windows 10.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
We have been testing WIN10 with the normal signed drivers. Attestation
signed is only required for secure boot.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, February 28, 2017 2:12 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Nano Server
xxxxx@hotmail.com wrote:
> Every kernel component has to be MSFT signed in order to load (since win 7
AFAIR), I guess Nano isnt going to be any different.
Not so. Kernel components need to be signed by someone on all 64-bit
systems, but the requirement to have a Microsoft signature did not arise
until the “anniversary release” 1607 of Windows 10.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
Visit the list online at:
http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at
http:</http:></http:></http:>