Download Entrust OTP for Windows 10 for Windows to entrust IdentityGuard Mobile is an innovative mobile identity application that enables individuals to strongly authenticate using their Windows. Microsoft® ODBC Driver 13.1 for SQL Server® - Windows, Linux, & macOS. The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows, Linux, & macOS to Microsoft SQL Server and Microsoft Azure SQL Database.

-->

Before you can establish a Partner Center account, you need to get a code signing certificate to secure your digital information. This certificate is the accepted standard for establishing your company’s ownership of the code you submit. It allows you to digitally sign PE binaries, such as .exe, .cab, .dll, .ocx, .msi, .xpi and .xap files.

Step 1: Obtain an EV certificate

• Microsoft requires an extended validation (EV) code signing certificates from partners enrolled and authorized for Kernel Mode Code Signing as part of the Microsoft Trusted Root Certificate Program. If you already have an approved EV certificate from one of these authorities, you can use it to establish a Partner Center account. If you don’t have a certificate, you’ll need to buy a new one.

Step 2: Buy a new code signing certificate

If you don’t have an approved EV code signing certificate, you can buy one from one of the certificate authorities below.

Extended validation code signing certificates

Step 3: Retrieve code signing certificates

Once the certificate authority has verified your contact information and your certificate purchase is approved, follow their directions to retrieve the certificate.

Note

You must use the same computer and browser to retrieve your certificate.

Step 4: Add the certificates to your account on Partner Center

For step-by-step instructions, see Add or Update a code signing certificate.

Next steps

• If you’re setting up a new Partner Center account, follow the steps in Register for the Hardware Program.

• If you’ve already set up a Partner Center account and need to renew a certificate, follow the steps in Add or Update a code signing certificate.

Code Signing FAQ

This section provides answers to frequently asked questions about code signing for Windows 10. Additional code signing information is available on the Windows Hardware Certification blog.

HLK Tested and Dashboard Signed Drivers

• A dashboard signed driver that has passed the HLK tests will work on Windows Vista through Windows 10, including Windows Server editions. This is the recommended method for driver signing, because it allows a single process for all OS versions. In addition, HLK tested drivers demonstrate that a manufacturer has rigorously tested their hardware to meet all of Microsoft's requirements with regards to reliability, security, power efficiency, serviceability, and performance, so as to provide a great Windows experience. This includes compliance with industry standards and adherence with Microsoft specifications for technology-specific features, helping to ensure correct installation, deployment, connectivity and interoperability. For more information about the HLK, see Windows Hardware Compatibility Program.

Windows 10 Desktop Attestation Signing

• A dashboard signed driver using attestation signing will only work on Windows 10 Desktop and later versions of Windows.
• An attestation signed driver will only work for Windows 10 Desktop; it will not work for other versions of Windows, such as Windows Windows 7, Windows 8.1, or Windows Server 2016 and greater.
• Attestation signing supports Windows 10 Desktop kernel mode and user mode drivers.

Windows 10 Earlier Certificate Transition Signing

• The below only applies to Windows 10 1803 and lower. As of Windows 10 1809, these will no longer work.
• A driver signed with any certificate issued after July 29th, 2015, with time stamping, is not recommended for Windows 10.
• A driver signed with any certificate that expires after July 29th, 2015, without time stamping, will work on Windows 10 until the certificate expires.

Cross-Signing and SHA-256 Certificates

Cross-signing describes a process where a driver is signed with a certificate issued by a Certificate Authority (CA) that is trusted by Microsoft. For more information, see Cross-Certificates Overview.

• Windows 8 and later versions support SHA-256.
• Windows 7, if patched, supports SHA-256. If you need to support unpatched devices that run Windows 7, you need to either cross-sign with a SHA-1 certificate or submit to the Dashboard for signing. Otherwise, you can either cross-sign with SHA-1 or SHA-2 certificate or create an HLK/HCK submission for signing.
• Because Windows Vista doesn’t support SHA-256, you need to either cross-sign with a SHA-1 certificate or create an HLK/HCK submission for Windows Vista driver signing.
• A driver cross-signed with a SHA-256 certificate (including an EV certificate) issued prior to July 29th, 2015 will work on Windows 8 and later. It will not work on Windows Vista or Windows Server 2008.
• A driver cross-signed with a SHA-256 certificate (including an EV certificate) issued prior to July 29th, 2015 will work on Windows 7 or Server 2008R2 if the patch issued through Windows Update earlier this year has been applied. For more information, see Availability of SHA-2 Hashing Algorithm for Windows 7 and Windows Server 2008 R2 and Microsoft security advisory: Availability of SHA-2 code signing support for Windows 7 and Windows Server 2008 R2: March 10, 2015.
• A cross-signed driver using a SHA-1 certificate issued prior to July 29th, 2015 will work on all platforms starting with Windows Vista through Windows 10.
• A cross-signed driver using a SHA-1 or SHA-256 certificate issued after July 29th, 2015 is not recommended for Windows 10.
• For more information about the effort to move to SHA-256 Certificates, see Windows Enforcement of Authenticode Code Signing and Timestamping

Windows Defender Application Control

• Enterprises may implement a policy to modify the driver signing requirements using Windows 10 Enterprise edition. Windows Defender Application Control (WDAC) provides an enterprise-defined code integrity policy, which may be configured to require at least an attestation-signed driver. For more information about WDAC, see Planning and getting started on the Windows Defender Application Control deployment process.

Windows Server

• Windows Server 2016 and greater will not accept attested device and filter driver signing submissions.
• The dashboard will only sign device and filter drivers that have successfully passed the HLK tests.
• Windows Server 2016 and greater will only load dashboard signed drivers that have successfully passed the HLK tests.

EV Certs

• As of October 31, 2015, your Hardware Dev Center dashboard account must have at least one EV certificate associated with it to submit binaries for attestation signing or to submit binaries for HLK certification.
• The submitted binaries themselves must be signed.

OS Support Summary

This table summarizes the driver signing requirements for Windows.

Version	Attestation Dashboard Signed	HLK Test Passed Dashboard Signed	Cross-signed using a SHA-1 certificate issued prior to July 29, 2015
Windows Vista	No	Yes	Yes
Windows 7	No	Yes	Yes
Windows 8 / 8.1	No	Yes	Yes
Windows 10	Yes	Yes	No (as of Windows 10 1809)
Windows 10 - DG Enabled	*Configuration Dependent	*Configuration Dependent	*Configuration Dependent
Windows Server 2008 R2	No	Yes	Yes
Windows Server 2012 R2	No	Yes	Yes
Windows Server >= 2016	No	Yes	Yes
Windows Server >= 2016 – DG Enabled	*Configuration Dependent	*Configuration Dependent	*Configuration Dependent
Windows IoT Enterprise	Yes	Yes	Yes
Windows IoT Enterprise- DG Enabled	*Configuration Dependent	*Configuration Dependent	*Configuration Dependent
Windows IoT Core(1)	Yes (Not Required)	Yes (Not Required)	Yes (Cross signing will also work for certificates issued after July 29, 2015)

*Configuration Dependent –With Windows 10 Enterprise edition, organizations can use Windows Defender Application Control (WDAC) to define custom signing requirements. For more information about WDAC, see Planning and getting started on the Windows Defender Application Control deployment process.

(1) Driver signing is required for manufacturers building retail products (i.e. for a non-development purpose) with IoT Core. For a list of approved Certificate Authorities (CAs), see Cross-Certificates for Kernel Mode Code Signing. Note that if UEFI Secure Boot is enabled, then drivers must be signed.

The terms of the software license agreement included with any software you download will control your use of the software.

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not use or load this software and any associated materials (collectively,

the 'Software') until you have carefully read the following terms and

conditions. By loading or using the Software, you agree to the terms of this

Agreement. If you do not wish to so agree, do not install or use the Software.

LICENSES: Please Note:

- If you are a network administrator, the 'Site License' below shall

apply to you.

- If you are an end user, the 'Single User License' shall apply to you.

- If you are an original equipment manufacturer (OEM), the 'OEM License'

shall apply to you.

SITE LICENSE. You may copy the Software onto your organization's computers

for your organization's use, and you may make a reasonable number of

back-up copies of the Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE. You may copy the Software onto a single computer for

your personal, noncommercial use, and you may make one back-up copy of the

Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an

integral part of or incorporated in Your product or as a standalone

Software maintenance update for existing end users of Your products,

excluding any other standalone products, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

Entrust Desktop Download

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may only distribute the Software to your customers pursuant to a

written license agreement. Such license agreement may be a 'break-the-

seal' license agreement. At a minimum such license shall safeguard

Intel's ownership rights to the Software.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to You, expressly

or by implication, with respect to any proprietary information or patent,

copyright, mask work, trademark, trade secret, or other intellectual property

right owned or controlled by Intel, except as expressly provided in this

Agreement.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. Title to all copies of the Software

remains with Intel or its suppliers. The Software is copyrighted and

protected by the laws of the United States and other countries, and

international treaty provisions. You may not remove any copyright notices

Entrust Driver Download For Windows 10

from the Software. Intel may make changes to the Software, or to items

Entrust Identityguard Desktop Download In Windows 10

referenced therein, at any time without notice, but is not obligated to

support or update the Software. Except as otherwise expressly provided, Intel

grants no express or implied right under Intel patents, copyrights,

trademarks, or other intellectual property rights. You may transfer the

Software only if the recipient agrees to be fully bound by these terms and if

you retain no copies of the Software.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on

physical media, Intel warrants the media to be free from material physical

defects for a period of ninety days after delivery by Intel. If such a defect

is found, return the media to Intel for replacement or alternate delivery of

the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS

PROVIDED 'AS IS' WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND

INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A

PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the

accuracy or completeness of any information, text, graphics, links or other

items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE

FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS,

BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR

INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR

LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL

DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE

OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time

if you violate its terms. Upon termination, you will immediately destroy the

Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the

laws of California, excluding its principles of conflict of laws and the

United Nations Convention on Contracts for the Sale of Goods. You may not

export the Software in violation of applicable export laws and regulations.

Intel is not obligated under any other agreements unless they are in writing

and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The Software is provided with 'RESTRICTED

RIGHTS.' Use, duplication, or disclosure by the Government is subject to

restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its

successor. Use of the Software by the Government constitutes acknowledgment

of Intel's proprietary rights therein. Contractor or Manufacturer is Intel

2200 Mission College Blvd., Santa Clara, CA 95052.