MDA Windows Release Testing Notification for Windows 11 22H2

Introduction

This communication serves as a notification of the upcoming Windows release, named “Windows 11 22H2”, and the Market Development Agreement (MDA) Milestone 1 Windows release testing details associated with its release.

Details

MDA testing for Windows 11 22H2 is required testing to meet the milestone requirement.

Windows release testing timeline
The MDA Milestone 1 testing window for Windows 11 22H2 will take place between March 11, 2022, and April 22, 2022. Due to the impact of the global pandemic, the timeline has been extended through till May 20, 2022.

A feature complete build posted to EEAP or WIP at that time will be acceptable to start testing. The feature complete build is expected to be posted by March 11, 2022.

Windows release testing - Test guidance document
The Windows 11 22H2 Test guidance document can be found on Collaborate Jan 25, 2022 for review. Final Windows 11 22H2 test guidance will be posted to DPC no later than March 4, 2022.

Windows release testing requirements
Under MDA Milestone 1, partners are required to test Windows 10 (devices that are still shipping and are Windows 11 capable) and Windows 11 devices distributed two years prior to the latest Windows release to manufacturing (RTM) date to ensure parity of Windows 10 and Windows 11 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 a notification.

In summary, the testing requirements for this milestone are:

• Make commercially reasonable efforts to test distributed (shipping) devices, dating back two years prior to the latest Windows 11 2021 upgrade/update, to ensure the devices will support the Windows 11 22H2 release. This includes devices under development that will be released or are planned to be released to the general public three months after Windows release to manufacture (RTM).
• Ensure that the Commercial ID supplied by Microsoft has been entered into the device Registry. Contact MDAHelp@microsoft.com to request a commercial ID if you have not taken part in MDA release testing in the past.
• Update the status of the tested devices by sending test results to MDAHelp@microsoft.com one time a week during the testing period or until the testing of the devices is completed (all appropriate tests have been passed).
• 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).
• Please submit your final test results for each device that has been tested to Microsoft using the template supplied in the test requirements to MDAHelp@microsoft.com no later than April 29, 2022.

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 Windows 11 22H2 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 (Original Equipment Manufacturers) partners may get access through the Windows Insider Program (WIP).


• Partners are to move to and 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 Windows 11 22H2, there are 2 scenarios that a device can align to. These are listed below with guidance for each scenario.

1. Models shipped with Windows 10 20H2, 21H1 or 21H2 releases preinstalled.


• Start with the respective Windows release which is preinstalled.
• Apply all updates from Windows Update (updates will include Windows 10 21H2).
• Test the upgrade of the customer system with Windows 10 21H2 installed to Windows 11 22H2.


2. Models shipped with Windows 11 21H2 preinstalled.


• Start with the Windows 11 21H2 image installed.
• Apply all updates from Windows Update.
• Test the update of the customer system with Windows 11 21H2 installed to Windows 11 22H2.

Best practice and added guidance

• You are advised to begin testing and filing bugs early in the testing period. You do not need to wait for the start of the official MDA testing timeline.
• You are to enter bugs, especially those related to IHV issues, immediately when they are found and not wait until the end of the testing window.
• You should prioritize testing newer devices (e.g., released in 2021) shipped with Windows 11 21H2 preinstalled, followed by the rest of the devices preinstalled with Windows 10 21H2.
• You are advised to prioritize testing on high-volume and high-risk devices, including systems with minimal storage and systems with custom hardware.
• In the bug filing process, you should include details on whether the issue happens prior to upgrade/update or when the device runs the previous operating system, to ensure the accuracy of the bug statement and to ensure the issue is indeed an upgrade/update related incident.
• You are to attach log files generated by Feedback Hub Advance Diagnostics to each bug and accurately describe each bug.
• When reporting, you are to list any firmware or non-Microsoft drivers that caused the Windows release to fail.
• You should fix identified drivers or application issues prior to Windows 11 22H2 being made available to the general public.