Windows Sdk Download Windows 10
Free download kinect sdk 1.5.2.331 for Windows 10. The Kinect for Windows SDK beta is a programming toolkit for application developers. It enables the academic and enthusiast communities easy access to the capabilities offered by the Microsoft Kinect device connected to computers running the Windows 7 ope. There are two ways to get the Windows 10 SDK. You can install it from this web site, by selecting the download link, or you can by select this version of the Windows 10 SDK (10.0.18362.0) in the Visual Studio 2019 Installer optional components. Before you install this SDK: Review all. Note: The Windows Performance Toolkit (WPT better known as WPRUI/WPR/Xperf) that ships with Windows 10 ADK/SDK is not compatible with Windows 7 SP1 or Windows Server 2008 R2 SP1. The stack (module!function) will show up as???!??? Aug 11, 2015 Note: The Windows Performance Toolkit (WPT better known as WPRUI/WPR/Xperf) that ships with Windows 10 ADK/SDK is not compatible with Windows 7 SP1 or Windows Server 2008 R2 SP1. The stack (module!function) will show up as???!???
-->Windows Sdk Download Xp
The WDK is used to develop, test, and deploy Windows drivers. The latest public version of WDK is available below.
Join the Windows Insider Program to get WDK Insider Preview builds. For installation instructions for the Windows Insider Preview builds, see Installing preview versions of the Windows Driver Kit (WDK).
WDK for Windows 10, version 1903
Step 1: Install Visual Studio 2019
The following editions of Visual Studio 2019 support driver development:
When you install Visual Studio 2019, select the Desktop development with C++ workload. The Windows 10 Software Development Kit (SDK) is automatically included, and is displayed in the right-hand Summary pane. However, the version of the SDK that is compatible with the WDK for Windows 10, version 1903 is not currently the default SDK. To select the correct SDK:
- In Visual Studio Installer, on the Workloads tab, under Installation Details, expand Universal Windows Platform development.
- Under Optional, select Windows 10 Preview SDK (10.0.18362.0).
- Continue with the install.
If you already have Visual Studio 2019 installed, you can install the Windows 10 Preview SDK (10.0.18362.0) by using the Modify button in Visual Studio install.
For ARM/ARM64 driver development, choose Individual components and under Compilers, build tools, and runtimes select Visual C++ compilers and libraries for ARM/ARM64.
For each architecture you intend to build drivers for, install the Spectre mitigated libraries thru Individual Components -> Compilers, build tools, and runtimes -> MSVC v142 - VS 2019 C+ x64/x86 Spectre-mitigated libs (v14.21).
Step 2: Install WDK for Windows 10, version 1903
New as of 1709 release: The WDK installation will by default install the WDK Visual Studio extension. This must be done in order for WDK VS integration to work.
Enterprise WDK for Windows 10, version 1903 (EWDK)
Microsoft Windows Xp Sdk Download
The EWDK is a standalone self-contained command-line environment for building drivers. It includes the Visual Studio Build Tools, the SDK, and the WDK. The latest public version of the EWDK contains Visual Studio 2019 Build Tools 16.0.0. To get started, mount the ISO and run LaunchBuildEnv.
EWDK with Visual Studio Build Tools
Additional information
Release notes and run-time requirements
WDK requires Visual Studio, for more information more info on system requirements for Visual Studio please review Visual Studio 2019 System Requirements.
EWDK will additionally need .NET 4.7.2, for more information on what .NET runs on please review .NET Framework system requirements.
You can use the WDK to develop drivers for these operating systems:
| Client OS | Server OS |
|---|---|
| Windows 10 | Windows Server 2019, Windows Server 2016 |
| Windows 8.1 | Windows Server 2012 R2 |
| Windows 8 | Windows Server 2012 |
| Windows 7 | Windows Server 2008 R2 SP1 |
Universal Windows driver samples
To get universal Windows driver samples, do one of the following:
- Go to the driver samples page on GitHub and click Clone or download > Download ZIP on the right side of the page.
- Download the GitHub Extension for Visual Studio to connect to the GitHub repositories.
- Browse the driver samples on the Microsoft Samples portal.
Related downloads
-->The SignTool tool is a command-line tool that digitally signs files, verifies signatures in files, or time stamps files. For information about why signing files is important, see Introduction to Code Signing. The tool is installed in the Bin folder of the Microsoft Windows Software Development Kit (SDK) installation path.
SignTool is available as part of the Windows SDK, which you can download from https://go.microsoft.com/fwlink/p/?linkid=84091.
**Windows Server 2008 R2 and Windows 7: **
If you are using the WinVerifyTrust function to verify multiple embedded signatures or support strong cryptography policy, you must include the following files:
- Microsoft.Windows.Build.Signing.wintrust.dll.manifest
- Wintrust.dll (downlevel version)
If you want to perform dual signing and make SHA256 catalogs, you must include those files and the following additional files:
- Makecat.exe
- Makecat.exe.manifest
- Microsoft.Windows.Build.Signing.mssign32.dll.manifest
- Mssign32.dll (downlevel version)
- Signtool.exe
- Signtool.exe.manifest
Here is the syntax for SignTool:
signtool [Command][Options][FileName …]
The following commands are supported by SignTool.
| Command | Description |
|---|---|
| catdb | Adds or removes a catalog file to or from a catalog database. |
| sign | Digitally signs files. |
| signwizard | This command is not supported. Windows Vista and earlier: Launches the signing wizard. Only a single file can be specified for the file name command-line parameter. |
| timestamp | Time stamps files. |
| verify | Verifies the digital signature of files. |
The following options apply to the catdb command.
| Catdb option | Description |
|---|---|
| /d | Specifies that the default catalog database be updated. If neither the /d nor /g option is used, SignTool updates the system component and driver database. |
| /gGUID | Specifies that the catalog database identified by the GUID be updated. |
| /r | Removes the specified catalog from the catalog database. If this option is not specified, SignTool will add the specified catalog to the catalog database. |
| /u | Specifies that a unique name be automatically generated for the added catalog files. If necessary, the catalog files are renamed to prevent name conflicts with existing catalog files. If this option is not specified, SignTool overwrites any existing catalog that has the same name as the catalog being added. |
Note
Catalog databases are used for automatic lookup of catalog files.
The following options apply to the sign command.
| Sign option | Description |
|---|---|
| /a | Selects the best signing certificate automatically. If this option is not present, SignTool expects to find only one valid signing certificate. |
| /acFileName | Specifies a file that contains an additional certificate to add to the signature block. |
| /as | Appends this signature. If no primary signature is present, this signature is made the primary signature. |
| /cCertTemplateName | Specifies the Certificate Template Name (a Microsoft extension) for the signing certificate. |
| /cspCSPName | Specifies the cryptographic service provider (CSP) that contains the private key container. |
| /dDesc | Specifies a description of the signed content. |
| /dgPath | Generates the to be signed digest and the unsigned PKCS7 files. The output digest and PKCS7 files will be: PathFileName.dig and PathFileName.p7u. To output an additional XML file, see /dxml. |
| /diPath | Creates the signature by ingesting the signed digest to the unsigned PKCS7 file. The input signed digest and unsigned PKCS7 files should be: PathFileName.dig.signed and PathFileName.p7u. |
| /dlibDLL | Specifies the DLL implementing the AuthenticodeDigestSign function to sign the digest with. This option is equivalent to using SignTool separately with the /dg, /ds, and /di switches, except this option invokes all three as one atomic operation. |
| /dmdfFileName | When used with the /dg option, passes the file’s contents to the AuthenticodeDigestSign function without modification. |
| /ds | Signs the digest only. The input file should be the digest generated by the /dg option. The output file will be: File.signed. |
| /duURL | Specifies a URL for expanded description of the signed content. |
| /dxml | When used with the /dg option, produces an XML file. The output file will be: PathFileName.dig.xml. |
| /fSignCertFile | Specifies the signing certificate in a file. Only the Personal Information Exchange (PFX) file format is supported. You can use the PVK2PFX.exe tool to convert SPC and PVK files to PFX format. If the file is in PFX format protected by a password, use the /p option to specify the password. If the file does not contain private keys, use the /csp and /k options to specify the CSP and private key container name, respectively. |
| /iIssuerName | Specifies the name of the issuer of the signing certificate. This value can be a substring of the entire issuer name. |
| /fd | Specifies the file digest algorithm to use to create file signatures. The default algorithm is Secure Hash Algorithm (SHA-1). Windows Vista and earlier: This flag is not supported. |
| /jDLL | This flag is not supported. Windows Vista and earlier: Specifies the name of a DLL that provides attributes of the signature. |
| /jpParameterName | This flag is not supported. Windows Vista and earlier: Specifies a parameter that is passed to the DLL specified by the /j command. |
| /kcName | Specifies the key that contains the name of the private key. |
| /nSubjectName | Specifies the name of the subject of the signing certificate. This value can be a substring of the entire subject name. |
| /nph | If supported, suppresses page hashes for executable files. The default behavior is determined by the SIGNTOOL_PAGE_HASHES environment variable and by the Wintrust.dll version. This option is ignored for non-PE files. |
| /pPassword | Specifies the password to use when opening a PFX file. A PFX file can be specified by using the /f option. For information about protecting passwords, see Handling Passwords. |
| /p7Path | Specifies that for each specified content file, a PKCS #7 file is produced. The produced PKCS #7 file is named PathFileName.p7. |
| /p7ceValue | Specifies options for the signed PKCS #7 content. Set Value to 'Embedded' to embed the signed content in the PKCS #7 file, or set Value to 'DetachedSignedData' to produce the signed data portion of a detached PKCS #7 file. If this option is not used, then the default choice is 'Embedded'. |
| /p7coOID | Specifies the object identifier (OID) that identifies the signed PKCS #7 content. |
| /ph | If supported, generates page hashes for executable files. This option is ignored for non-PE files. |
| /rRootSubjectName | Specifies the name of the subject of the root certificate that the signing certificate must chain to. This value can be a substring of the entire subject name of the root certificate. |
| /sStoreName | Specifies the store to open when searching for the certificate. If this option is not specified, the My store is opened. |
| /sha1Hash | Specifies the SHA1 hash of the signing certificate. |
| /sm | Specifies that a computer store, instead of a user store, be used. |
| /snkFileName | This flag is not supported. Windows Vista and earlier: Specifies the SNK file that contains the strong name private key. |
| /sncspName | This flag is not supported. Windows Vista and earlier.: Specifies the CSP that contains the strong name private key container. |
| /snkcName | This flag is not supported. Windows Vista and earlier: Specifies the key that contains the name of the strong name private key. |
| /snks {12} | This flag is not supported. Windows Vista and earlier: Specifies which strong name private key to use. If this argument is not used, the default value 2 is assumed. The following values are supported:
|
| /tURL | Specifies the URL of the time stamp server. If this option is not present, then the signed file will not be time stamped. A warning is generated if time stamping fails. |
| /tdalg | Used with the /tr switch to request a digest algorithm used by the RFC 3161 time stamp server.[!Note] Windows Vista and earlier: This flag is not supported. |
| /trURL | Specifies the RFC 3161 time stamp server's URL. If this option (or /t) is not specified, the signed file will not be time stamped. A warning is generated if time stamping fails. This switch cannot be used with the /t switch. Windows Vista and earlier: This flag is not supported. |
| /uUsage | Specifies the enhanced key usage (EKU) that must be present in the signing certificate. The usage value can be specified by OID or string. The default usage is 'Code Signing' (1.3.6.1.5.5.7.3.3). |
| /uw | Specifies using 'Windows System Component Verification' (1.3.6.1.4.1.311.10.3.6). |
The following option applies to the timestamp command.
| Timestamp option | Description |
|---|---|
| /tURL | Required. Specifies the URL of the time stamp server. The file being time stamped must have previously been signed. |
| /tdindex | Used with the /tr switch to request a digest algorithm used by the RFC 3161 time stamp server.[!Note] |
| /tpalg | Adds a timestamp to the signature at index. |
| /trURL | Specifies the RFC 3161 time stamp server's URL. The file being time stamped must have previously been signed. Either the /tr or the /t option is required. |
| /p7Path | Adds a timestamp to PKCS #7 files. |
The following options apply to the verify command.
Top 4 Download periodically updates software information of windows 7 tweaker full versions from the publishers,but some information may be slightly out-of-date.Using warez version, crack, warez passwords, patches, serial numbers, registration codes, key generator, pirate key, keymaker or keygen forwindows 7 tweaker license key is illegal. Ultimate windows tweaker.
| Verify option | Description |
|---|---|
| /a | Specifies that all methods can be used to verify the file. First, the catalog databases are searched to determine whether the file is signed in a catalog. If the file is not signed in any catalog, SignTool attempts to verify the file's embedded signature. This option is recommended when verifying files that may or may not be signed in a catalog. Examples of files that may or may not be signed include Windows files or drivers. |
| /ad | Finds the catalog by using the default catalog database. |
| /all | Verifies all signatures in a file with multiple signatures. |
| /as | Finds the catalog by using the system component (driver) catalog database. |
| /agCatDBGUID | Finds the catalog in the catalog database identified by the GUID. |
| /cCatFile | Specifies the catalog file by name. |
| /d | Print the description and description URL. Windows Vista and earlier: This flag is not supported. |
| /dsIndex | Verifies the signature at a certain position. |
| /hash{SHA1SHA256} | Specifies an optional hash algorithm to use when searching for a file in a catalog. |
| /kp | Performs the verification by using the x64 kernel-mode driver signing policy. |
| /ms | Uses multiple verification semantics. This is the default behavior of a WinVerifyTrust call. |
| /oVersion | Verifies the file by operating system version. The version parameter is of the form: PlatformID**:VerMajor.VerMinor.**BuildNumber The use of the /o switch is recommended. If /o is not specified SignTool may return unexpected results. For example, if you do not include the /o switch, then system catalogs that validate correctly on an older OS may not validate correctly on a newer OS. |
| /p7 | Verify PKCS #7 files. No existing policies are used for PKCS #7 validation. The signature is checked and a chain is built for the signing certificate. |
| /pa | Specifies that the Default Authentication Verification Policy is used. If the /pa option is not specified, SignTool uses the Windows Driver Verification Policy. This option cannot be used with the catdb options. |
| /pgPolicyGUID | Specifies a verification policy by GUID. The GUID corresponds to the ActionID of the verification policy. This option cannot be used with the catdb options. |
| /ph | Print and verify page hash values. Windows Vista and earlier: This flag is not supported. |
| /rRootSubjectName | Specifies the name of the subject of the root certificate that the signing certificate must chain to. This value can be a substring of the entire subject name of the root certificate. |
| /tw | Specifies that a warning is generated if the signature is not time stamped. |
The following display options apply to all SignTool commands.
| Global option | Description |
|---|---|
| /debug | Displays debugging information. |
| /q | Displays no output on successful execution and minimal output for failed execution. |
| /v | Displays verbose output for successful execution, failed execution, and warning messages. |
The SignTool verify command determines whether the signing certificate was issued by a trusted authority, whether the signing certificate has been revoked, and, optionally, whether the signing certificate is valid for a specific policy.
SignTool returns an exit code of zero for successful execution, one for failed execution, and two for execution that completed with warnings. If the SignTool encounters an unhandled exception, however, the return value is undefined.
The following command line shows signing a file automatically using the best certificate.
signtool sign/aMyFile.exe
Note
When signing an executable file that is larger than approximately 300 megabytes for use on a computer running Windows XP with Service Pack 2 (SP2) and later, you should use catalog signing with the MakeCat tool rather than use the SignTool tool. Depending on the available system resources of the computer on which the file is verified, some applications may not be able to verify the binary signature of a large file. For more information, see KB article 922225.