Does Microsoft know about » Microsoft Windows Hardware compatibility publishers » and is it affiliated to Microsoft at all ?

Microsoft suggests that the download of any 3rd party products (or even presumably Microsoft products) from non-Microsoft sites — especially sites like brothersoft or download or tucows or other mass download sites is risky and done so at your risk. There are far too many sites to check everything every day. One way is to check is to start here: http://www.microsoft.com/en-us/howtotell/default.aspx. If you think you’ve found a case of software piracy, see: http://www.microsoft.com/en-us/piracy/reporting/default.aspx. (NOTE: We will sometimes recommend 3rd party products where appropriate, but while almost certainly safe if suggested here by verified expert here and even with that recommendation of an expert here, YOU still bear the risk of using 3rd party products.)

The best thing to do aside from avoiding such sites and choosing to download only directly from reputable program producer websites (Microsoft, Sun, Adobe. ) with valid certificates and publishing information is to follow basic security procedures.

Let’s talk about security in general. Because my work entails more risks than the average user, I do more things more frequently than most would need. However, some of this might help (you could reduce the number or the frequency) and some of it applies to everyone (especially the bold section):

Here’s what I do (and it isn’t 100% but nothing is, and in some cases only catches things after they’ve already gotten into the system, but it’s a good process while remaining reasonable and they can all work together — as proven by the fact that I use them):

I use MSE for real-time protection and run scheduled daily quick scans with a scheduled bi-weekly full scan.

I update and periodically (every couple of weeks or so) run full scans with Malwarebytes: http://www.malwarebytes.org/ and SuperAntiSpyware: http://superantispyware.com/ and ESET online scanner: http://www.eset.com/us/online-scanner Get only the free versions. Any that also have paid versions include features like real-time protection that cannot be used along with MSE anyway (in these cases), so there’s no point in spending the money anyway.

I use WOT http://www.mywot.com/en/download to help identify safe and dangerous web sites.

I use Secunia PSI http://secunia.com/vulnerability_scanning/personal/ to make sure all my programs are updated and current (since updates often plug security holes in the software and thus can be important as many people never check and/or update their software unless prompted — and this way I don’t need to check everything since notifications and sometimes updates are automatic).

I always follow the following advice from Stephen Boots — MVP:

-Make sure that the Windows Firewall is enabled. No other firewall truly offers better protection or is needed. This one is perfectly fine.

-Make sure that all important/critical updates, including service packs for the operating system and programs are installed from Microsoft Update (Windows Update).

-Make sure Internet Explorer is at version 8 or 9 and updated with all patches.

-In Internet Explorer 8 or 9, use the SmartScreen Filter.

-Make sure that IE Internet Security settings are at least set to medium-high (default).

-Enable the pop-up blocker in IE.

-On Vista and Windows 7 make sure that User Account Control (UAC) ON and not running with elevated privileges.

-Make sure that Windows Automatic Updates are set to at least notify, but the preferred setting is to download and install automatically. If you update manually, be sure to update as soon as possible after being notified of available updates.

—Make sure that installed applications, especially Adobe Acrobat, Adobe Flash, and Java are at their latest versions. Many vendors are regularly updating and patching for security holes. Secunia PSI mentioned above can help automate this a lot.

-Never click through links from unknown sources and use caution even if they are from a «trusted» source.

-Never open unsolicited email attachments.

-Practice safe web browsing. No adult sites, no peer-to-peer file sharing sites, no sites offering cracks or free software that you know can’t be true, lockdown Facebook to only Friends on EVERYTHING, use WOT mentioned above, use Task Manager to close all open instances of your browsers if you ever get a suspicious pop-up , double check all links in browsers and emails by hovering over them or otherwise checking to see if what they say and where they say they are directed match what is really there and I could go on but you get the idea.

-Always use a standard user account unless you have a specific need for an administrator account. Then switch, do the administrative task, and return to the standard account. This greatly limits the access of any type of infection of intrusion into your system since administrative access isn’t in place.

I hope this helps.

MVP(7/2012-6/2015),MCSE,MCSA,MCC2011,xCMM,xCAM,A+,Net+,Security Expert, xInfluencer. See Profile.

W10Prox64 Fast 16299rs3; Ofc Insider 1710/8613.1000; Edge,IE11,Chrome.

Windows Hardware Compatibility Program Certification Process

The Windows Hardware Compatibility Program lets you show customers that your hardware is reliably compatible with Windows 10. The program contains tools and processes that determine whether your hardware meets Windows 10 quality standards.

Step 1: Review Hardware Requirements

Building a great Windows device starts with understanding the hardware requirements.

Step 2: Register on Hardware Dashboard

Before you start testing for Windows compatibility, you should register with the hardware dashboard. Later, you’ll use the dashboard to submit your hardware for the Hardware Compatibility Program.

Step 3: Install the Windows Hardware Lab Kit

Get ready to test your Windows hardware by installing the Windows Hardware Lab Kit (HLK) and configuring your test environment. The tests that are included in the Windows HLK help you validate compatibility with Windows 10 and get your hardware listed on the certified product list. The HLK Getting Started Guide provides instructions on how to build a test environment, automate driver and system testing, and create the submission package required to participate in the Windows Hardware Compatibility Program.

Step 4: Submit Results

After testing your hardware and packaging the results with the HLK, you can submit the results to the hardware dashboard to qualify for the Windows Hardware Compatibility Program.

Step 5: Manage and Update

After you submit your test results, you can monitor and manage your submission in the dashboard.

Troubleshooting

The dashboard also provides additional services, including:

The Windows Hardware Lab Kit User’s Guide also provides the following guidance on interpreting test failures and bug submission:

Windows Hardware Compatibility Program Specifications and Policies (whcp-specifications-policies)

When products meet the minimum requirements as defined in the below documents, it ensures that applications and devices are compatible. Systems are required to use components which have also passed compatibility testing. Products submitted with passing results will continue to be included on the Certified Products List and Windows Server Catalog.

Specifications and Policies Documents

The specifications define how to build Windows-compatible devices, systems, and filter drivers across all Windows Platforms. They were developed in collaboration with partners, and focus on ensuring compatibility, interoperability, security, and reliability.

The policies and processes provide guidelines on qualification testing and product submission, as well as useful business process requirements.

Certification for Windows Server 2016 and later, the Software Defined Data Center (SDDC) additional qualifications, the Windows Server Software Defined Datacenter (WSSD) program, and Azure Stack.

Products looking to achieve certification and qualification for the above products and programs must:

• Meet the Windows Hardware Compatibility Specifications for the relevant version of Windows Server and these other programs
• Follow the Windows Server Policy document
• Use the relevant version with matching palylist and supplemental content to generate logs

Questions about the Azure Stack or WSSD programs and SDDC Additional Qualifications, or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact.

Hardware submissions

The Windows Hardware Compatibility Program (for Windows 10) and the Windows Hardware Certification Program (for Windows 8/8.1 and older operating systems) enable you to design, create, and test your hardware and drivers before you submit the final version through the Partner Center. For more information, see the Windows hardware certification page. By certifying your hardware device, system, and drivers for Windows, you gain the support of Microsoft marketing resources in the form of compatibility and reliability listings, logo artwork, and promotional partnerships.

To develop your device, download the Windows Driver Kit (WDK).

To test your device, download the Windows Hardware Lab Kit (Windows HLK) for Windows 10.

After you develop and test your product, you can submit the results with a hardware submission.

We strongly encourage you to include public driver symbols as part your HLK package. See Public Symbols and Private Symbols to learn how to create public symbols. See Step 8: Create a submission package to learn how to include symbols with your package. Note that any .pdb files in your submission will be removed before being published.

To submit an HLK or HCK package, see Create a new hardware submission.

To submit a WLK package, see Create a new WLK device certification submission for more information.

Drivers summary page

The Drivers summary page contains a list of all hardware certification submissions that you have created or are shared with you. You can create a new hardware submission by selecting the Create new driver button.

The hardware certification submission list displays the following information about each submission:

ID

The ID of the driver.

Name

The name specified in Driver name during the submission creation process.

State

The current state of the submission. Possible values are:

• Package acceptance: Your submission package has passed initial screening for proper formatting and contents.
• Preparation: We’re preparing your package for further review and signing.
• Validation: We’re validating your package for policy compliance and technical correctness.
• Manual review: We weren’t able to automatically validate the contents of your package, so someone at Microsoft is taking a closer look.
• Catalog creation: We’re creating the security catalog for your driver.
• Sign: We’re applying Microsoft’s signature to your security catalog and binaries.
• Finalize: We’re finishing up and your driver will be ready soon.
• Completed: Your submission is complete.

Certification type

The certification type for your submission. This can be either HLK or HCK.

Created date

The date the driver was added to your account, either by you or by someone sharing the driver with you.

Permission

Your permission for the submission. Possible values are:

• Author: Author of the driver. You can complete all tasks and share the driver with partners.
• Publisher: The driver is shared with you. You can download the driver, create Windows Update shipping labels, and create DUA packages. You can’t share the driver with additional companies.
• Read-only: The driver was submitted to Windows Update on your behalf. You can see the driver details, download the driver, and view the shipping label that was submitted on your behalf. You can’t create shipping labels or create DUA packages.

Source

The author (shown as the organization name) of the submission.

The search box allows you to search for a specific submission or set of submissions. You can search for exact or partial matches for the values in the ID, Name, State, and Certification type columns.

Hardware submission page

A hardware submission page contains information about a specific hardware submission, including status, packages, certification info, and shipping labels. For information about how to create a hardware submission, see Create a new hardware submission.

The left side of the page contains a list of the 10 most recently viewed submissions.

You can monitor the progress of your submission with the progress tracker at the top of the page. Once all steps show a green check, the submission is complete and your company will receive a notification.

Packages and signing properties

This section shows you how to manage your packages.

Select Upload new to upload a new package.

Select Download DUA shell to download the DUA shell package. For information about how to update a submission using DUA, see Manage hardware submissions.

The uploaded package list displays your uploaded packages for this submission. Select the caret to expand a package. This shows you the submission ID and allows you to select Download package to download the package.

Additional certifications displays any chosen additional certifications.

Certification

This section displays certification information. Select See more info to expand this section. You can review the certification information you provided, which includes the following:

Column	Description

Indicates whether or not your driver was compiled with the Retpoline flag. A Check mark = True and an X = False. For more information about this change see our blog post.

Is this a Universal Windows driver?

Indicates whether or not your driver meets the Universal Windows Platform requirements. For more information, see Getting Started with Universal Windows drivers.

What type of device?

Indicates that your device is:

An internal component, if your device is part of a system and connects inside the PC.

An external component, if your device is an external device (peripheral) that connects to a PC.

Both, if your device can be connected internally (inside a PC) and externally (peripheral).

Select metadata category

The device metadata category you selected.

If needed, you can generate a Sysdev reference ID that allows you to link up Dev Center hardware submissions with Sysdev Device Metadata submissions.

The date when you want your product included on the Windows Server Catalog, the Windows Certified Product List, and the Universal Driver List. The default setting is Today.

Your marketing name(s). Marketing names allow you to provide aliases for your product. You can provide as many names as you want.

Submissions are automatically assigned Declarative and Universal attributes based off the entire submission contents. If you want a submission to be marked as Declarative=True and/or Universal=True , all files and INFs within the submission must be compliant with the appropriate attribute(s). For example, a merged HLK package can contain two driver sets for different OS certifiations. If one set is Declarative and another set is not, the entire submission would be marked as Declarative=False . INF only packages will have Universal greyed out as there are no binaries to validate. Each set should be separated into two submissions to ensure they are marked appropriately.

If you want to add or update your announcement date, use the Announcement date (UTC) field and select Submit.

You can also add or remove marketing names. To add a name, enter it in the Marketing name text box and select Add. To remove a name, select the red X button next to the marketing name you want to remove. You can also add multiple names at once by selecting Add multiple names. When you are finished, select Submit.

Distribution

This section displays shipping label information for this submission. For information about how to use shipping labels, see the Manage driver distribution with shipping labels section.

Select New shipping label to create a new shipping label.

Select Publish all pending to publish all shipping labels that are not yet published.

The shipping label list displays the shipping labels for this submission. This list includes shipping labels you created, and partner shipping labels for your shared driver. Select the shipping label name to see details for that shipping label. The shipping label list displays the following information about each label:

Field	Description

The shipping label name. Select this name to see details for the shipping label.

The Publisher display name of the shipping label creator. This allows you to easily keep track of which business partners sent you drivers.

For a Windows Update shipping label, the destination is «Windows Update».

For a shared driver, the destination is the Publisher display name of the company you selected for Who is publishing? when you created the shipping label. This allows you to easily see all companies that you have shared your driver with.

The creation date of the shipping label.

The release date of the shipping label.

If the shipping label was created by your company, you will see the details of the user who created the shipping label. This allows you to follow up if you have any questions about the creation. This field is not applicable if another company created the label.

If the shipping label was created by your company, you will see the details of the user who last modified the shipping label. This allows you to follow up if you have any questions about the changes. This field is not applicable if another company created the label.

The status graphic displays the publish status for each shipping label. A green check means the label has been published. A yellow circle means the label is not published yet.

Field	Description