21H1 MDA Windows Release Testing Notification

Introduction

This communication serves as notification of the upcoming Windows Release, named “21H1”, and the Market Development Agreement (MDA) Milestone 1 Windows Release Testing details associated with its release.

Call to action

Review this partner-facing communication and share the link to this page with your applicable accounts, who will see all content appropriate to their roles. Ensure your accounts are made aware of the MDA Milestone 1 Windows Release Testing requirement.

Contact MDA Help with questions.

Details

Upgrade testing for 21H1 release is recommended, but not required.

Windows Release Testing Timeline
The MDA Milestone 1 testing window for 21H1 will take place between February 23, 2021 and April 3, 2021.
A feature complete build posted to EEAP or WIP at that time will be acceptable to start testing.

Windows Release Testing Test Guidance Document
The 21H1 Windows Release Test Guidance document can be found on Collaborate February 17 for review. Final 21H1 Windows Release Test Guidance will be posted to DPC no later than February 22.

Windows Release Testing Requirements
Under MDA Milestone 1, partners are required to test Windows 10 devices distributed two years prior to the latest Windows release to manufacturing (RTM) date to ensure compatibility of Windows 10 devices with the latest Windows Release. Per the MDA Program Letter, Microsoft will provide notification that a Windows Release is forthcoming and requires testing. This communication is to serve as notification.

In summary, the testing requirements for this milestone are:

• Make commercially reasonable efforts to test distributed Windows 10 devices, dating back two years prior to the latest Windows 10 RTM date, to ensure the devices will support the latest Windows Release. This includes devices under development that will release or are planned to be released to the general public three months after the Windows Release RTM.
• Ensure that the Commercial ID supplied by Microsoft has been entered into the device Registry.
• Update the status of the tested devices at least one time a week during the testing period or until the testing of the tested devices is completed.
• File a bug for each issue that is found during testing, and the identified bugs are to be fixed in a mutually agreed upon manner prior to Windows Release RTM (release to manufacturing). This includes bugs found by Independent Hardware Vendors. (IHVs)
• If you choose to participate in this recommended testing, please submit your final test results for each device that has been tested to Microsoft using the template supplied in the test requirements to the MDA Help alias no later than April 9, 2021.

Microsoft Partner Center and Microsoft Collaborate Onboarding
To meet the Windows Release Testing requirements under MDA Milestone 1, it is necessary to create a Microsoft Partner Center account. Microsoft Partner Center is used for submitting bugs and downloading content, both of which are required under MDA Milestone 1. It is also necessary to have access to Microsoft Collaborate. Microsoft Collaborate allows you to download builds, specs, documents, and other information, as well as submit bugs during testing.

• Microsoft Partner Center: If you do not already have access, follow the instructions Create a Partner Center account to create your account. When you have created your Microsoft Partner Center account, request access to the Hardware tab by contacting your Account Manager for details.
• Microsoft Collaborate: To onboard and get access to the Microsoft Partner Center Collaborate tab, follow the Microsoft Collaborate Onboarding Instructions. This will register the Microsoft Partner Center account you created above, with Microsoft Collaborate.

Windows Release Testing Test Builds
Accessing test builds of 21H1 can occur in two ways:

1. Partners who take part in the Enterprise Early Access Program (EEAP) can get access through that program.
2. All OEM partners may get access through the Windows Insider Program (WIP).
   • Partners are to move to utilize the latest build immediately upon its release through EEAP or WIP, to ensure the latest build is used to complete testing.
   • Testing should be performed against a build that is no later than a week old as that latest build will contain bug fixes.

Windows Release Testing Scope
For the 21H1 Windows Release, there are multiple scenarios that a device can align to. These are listed below, and the table provides some guidance for each scenario.

1. Model shipped only with 19H1 preinstalled.
2. Model shipped only with 19H2 preinstalled.
3. Model shipped only with 20H1 preinstalled.
4. Model shipped only with 20H2 preinstalled.
5. Model shipped with 19H1 and 19H2 preinstalled.
6. Model shipped with 19H2 and 20H1 preinstalled.
7. Model shipped with 19H1, 19H2 and 20H1 preinstalled.
8. Model shipped with 19H2, 20H1 and 20H2 preinstalled.
9. Model shipped with 19H1, 19H2, 20H1 and 20H2 preinstalled.

Example of Scenario Nine: Partner has a model that:

• Previously shipped with 19H2 preinstalled prior to 20H1 being released.
• Moved to ship with 20H1 preinstalled after 20H1 RTM.
• Moved to ship with 20H2 preinstalled after 20H2 RTM.
• Has the same hardware throughout the preinstall of all Windows Releases (19H2, 20H1, and 20H2)