Join the tech community for Windows hardware manufacturers. WinHEC Online. Use Microsoft's Intelligent Edge tools to quickly move from pencil sketch to deployment. AI Edge community. Join the tech community for IoT and Intelligent Edge hardware manufacturers. This means that the file has been published by Microsoft Windows Hardware Compatibility Publisher and that no one has tampered with the file.
If you click the View Certificate button shown in the screenshot above, you can examine all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, and so on. You can also see the address for Microsoft Windows Hardware Compatibility Publisher, such as the street name, city and country.
You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above. The FreeFixer tool treats files from Microsoft Windows Hardware Compatibility Publisher as trusted, which means that the Microsoft Windows Hardware Compatibility Publisher files will appear with a green background and that there's no removal checkbox for the file.
However, as you can see in the scan results below, a few of the anti-virus scanners detects the Microsoft Windows Hardware Compatibility Publisher file s. My guess is that those detections are incorrect and that the files are safe. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
As mentioned above, I think these detections are false positives since it is very unlikely that Microsoft Windows Hardware Compatibility Publisher would ship a malware file. The detection percentage is based on the fact that I've collected scan reports for the Microsoft Windows Hardware Compatibility Publisher files. You can review the full details of the scan results by examining the files listed above.
Google translate of Tito's comment above: "the driver seems to be the one of the problem, supplied by ESET version For dashboard purposes, the most interesting part of an HLK project is the Package tab:. Now is you first chance to make declarations about the OS versions that are supported for your submission. In this case, the submission has been tested for Windows 10 x64 and earlier versions of Windows.
You also need to make declarations for locales. For example, depending on the design and architecture of your driver, you may choose to display different strings in different locales. In that case, you might actually have different compiled binaries for different locales. So for one device, you might have a hundred different drivers; one for each locale. Select Add Supplemental Folder to submit other files that are important to the submission but are not actually part of the submission itself.
You can add any content you want to the package. This is a way for you to get other items to the Dashboard that are important for the submission, such as a readme file for a driver submission. The next step is to specify a certificate that you will you use to sign the package — this is the first of the two code signing operations that were covered at the start of this topic.
You can select Use a certificate file to specify a certificate that is stored on something like a USB drive, or select Use the certificate store to specify a certificate that has been imported into the certificate store of the local computer.
The next steps occur in the Partner Center dashboard. Sign in and follow the instructions in Create a new hardware submission to upload your HLK package. Inside the submission folder will be the package files. These files are signed by Microsoft. The partner does not have to sign the returned payload.
0コメント