Thanks for the clarification. Fun fun times ahead...
On 4/14/2016 11:30 AM, Tim Roberts wrote:
Tom Duffy wrote:
>SHA256 works on 7 with KB3033929, 8, 8.1, and 10.
i.e. SHA256 certs that were issued prior to Windows 10 RTM work, but
SHA256 certs that were issued after Windows 10 RTM only work in
Windows 10 if the package is "sysdev'ed", or is that only if
"secure boot" is on?
As of now, all SHA256 certificates work (as do all SHA1 certificates).
Starting with this summer's release of Windows 10, in a fresh
non-upgrade installation, with secure boot enabled, no certificate
issued after the Windows 10 RTM release will work at all. You will need
the attestation signature.
Again, that's ONLY for the Windows 10 Redstone release, ONLY for a fresh
install, and ONLY if secure boot is on. Try to get your technical
support department to put that in a support script.
NOTICE: This electronic mail message and its contents, including any attachments hereto
(collectively, "this e-mail"), is hereby designated as "confidential and
proprietary." This e-mail may be viewed and used only by the person to whom it has been sent
and his/her employer solely for the express purpose for which it has been disclosed and only in
accordance with any confidentiality or non-disclosure (or similar) agreement between TEAC
Corporation or its affiliates and said employer, and may not be disclosed to any other person or
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
URL to WDMAUDIODEV page: