With an underscore (_) and used as the destination. Last character of the source file name is replaced MAKECAB ] /F directive_file ĭestination File name to give compressed file. Open a Command Prompt window as Administrator.Įnter MakeCab /? to view the MakeCab options: C:\Echo> MakeCab /?Ĭabinet Maker - Lossless Data Compression Tool Gather the binaries to be signed into a single directory. You must use a mapped drive letter for the CAB to be valid. For example, they must support x86, 圆4, or they all must support both x86 and 圆4.ĭo not use UNC file share paths when referencing your driver locations ( \\\server\share). Microsoft regenerates catalog files and replaces any catalog files that were submitted.Įach driver folder in your CAB file must support the same set of architectures. CAT files are required and used for company verification only. pdb file is required for Microsoft's automated crash analysis tools.Ĭatalog.
The symbol file that is used for debugging information. The driver INF file that is used by the dashboard to facilitate the signing process. We'll be using the echo driver sample to illustrate the process.Ī typical CAB file submission must contain the following: In this section, we'll step through the process of creating a CAB files submission. (Optional) Download the echo driver sample that is used in this article. If your organization doesn't have a certificate, you'll need to purchase an EV certificate.įollow the process described in Download kits and tools for Windows 10 to download and install the Windows Driver Kit (WDK). If your company already has a certificate, have the certificate available. Check whether your organization already has a code signing certificate. You must have an Extended Validation (EV) code signing certificate. If you're not yet registered, follow the steps in How to register for the Microsoft Windows Hardware Developer Program. Register for the Hardware Developer program. Read and understand the requirements for Windows 10 attestation signed drivers. Attestation signed drivers for testing scenarios are still supported when selecting CoDev or Test Registry Key / Surface SSRK options. As of March 1, 2023, attestation signed drivers targeting retail audiences are no longer published on Windows Update.
0 kommentar(er)
