Skip to main content
Games that integrate XBOX services must adhere to a set of XBOX Requirements (XRs). PC games must also follow the Microsoft Store policies. A subset of these requirements are build verification tests (BVTs), which are a suite of tests designed to determine a title’s readiness for full Certification testing. All titles must pass BVTs before they enter full Certification testing. Titles that fail BVTs must fix all failures before resubmitting to Certification.

Common BVT failures

This is a list of common BVT failures on console and PC. Differences between devices are called out where they apply.

Unfixed conditions for resubmission (CFRs)

One of the main reasons a title fails BVTs is a new build that doesn’t fix all previously logged conditions for resubmission (CFRs) or BVT failures. The test team verifies that every CFR logged in the previous test pass is fixed before the title is scheduled for full testing. For the test, see BVT-09 Conditions for Resubmission. Guidance:
Make sure all CFRs in a Certification report and all previous BVT failures are fixed before you submit a new build.

Title stability

Titles must remain stable during test and must not have issues that block testing. The BVT team verifies that all menus can be accessed and all game modes are testable. For the test, see BVT-01 Build Stability. Guidance:
Test the title on all supported device types and hardware configurations, and on PC use the latest graphics drivers. Review the test cases for XR-001: Title Stability and focus on the pass and fail examples for each test case.
Example stability issues found during BVTs:
  • Crashes, hangs, or long loading screens when launching the title.
  • Crashes during multiplayer activities, such as sending and receiving game invites, matchmaking, and joining scenarios.
  • Crashes during general gameplay.
  • Crashes or hangs when testing suspend and resume scenarios on console.
  • Crashes or hangs when testing user input on all screens that accept input.
  • Crashes or hangs when rapidly entering and backing out of all game menus.
Additional test scenarios on PC:
  • Install the title from the Store. The test team has seen issues after installing the title from the Store that aren’t seen when side-loading the title in a developer sandbox.
  • Test multiple resolutions, both windowed and full screen.

Required dependencies aren’t installed (PC)

The required dependencies aren’t installed on a clean PC when the title is installed from the Store. For example, after you install the title on a clean PC, it doesn’t launch and displays the following error: The code execution cannot proceed because MSVCP100.dll was not found. Guidance:
Test on a new installation of Windows and make sure all package dependencies are removed from the device. Publish the game to the Store, install it, and verify that all game dependencies are installed. Include whatever dependencies the game requires in the installation directory, or prompt the user to install the dependencies during first boot if the Store doesn’t install them.
Reference: Framework Package Dependencies

Two-factor authentication (PC)

When a profile that hasn’t launched the title before signs in, the user isn’t prompted with the explicit consent dialog. The title enters an indefinite loading screen after launch, before reaching any gameplay or menus. Guidance:
Test sign-in using developer accounts that have two-factor authentication enabled. There’s an option to select two-factor authentication when you create developer accounts in Partner Center. The title is likely calling only XUserAddAsync(AddDefaultUserSilently) and assuming there’s always a user. The title should use XUserAddAsync(AddDefaultUserAllowingUI) and include code to handle any potential error cases. The GDK has samples that show how to use this. This allows UI to appear when there’s no signed-in user, consent is missing, or another authentication issue needs to be resolved.
Reference: XUserAddAsync GDK documentation

Partner-hosted services

Partner services that the game requires, such as multiplayer services, must be running when Certification receives the submission. The BVT team verifies these services before scheduling the title for full testing. The services must remain functional for the entire test pass. For the test, see BVT-12 Partner-Hosted Services. Guidance:
Verify that all partner services required for the game are running when you submit to Certification and for the entire test pass.

Microsoft Store availability and XBOX services gameplay settings

During BVT, the title is downloaded from the Store in the CERT and CERT.DEBUG sandboxes. Once the publish to the CERT sandbox is complete in Partner Center, update the XBOX services gameplay settings in the CERT.DEBUG sandbox as well. This helps ensure there are no delays when acquiring and setting up the title for test. For the test, see BVT-08 XBOX Store Availability. Updating XBOX services gameplay settings in CERT.DEBUG
If this is your first submission, or if you’ve updated your XBOX services gameplay settings since your previous submission, manually publish the settings to the CERT.DEBUG sandbox.
Guidance:
  1. In Partner Center, go to the XBOX services - Gameplay settings page for your product. Select the source sandbox that you selected in the Certify workflow for the packages.
  2. Select Review and Publish to publish your XBOX services gameplay settings to the CERT.DEBUG sandbox destination.

Multiplayer

Titles that support multiplayer experiences must allow a user to successfully start, progress through, and complete multiplayer sessions. The BVT team attempts to match the minimum number of users required to start a session and completes the minimum number of objectives required to end a match. For the test, see BVT-02 Matchmaking. If a title supports multiplayer but not a matchmaking experience, the BVT team uses the system and in-game invite and join features to bring the minimum number of users into a match. Guidance:
Make sure all supported multiplayer features are complete, working, and testable before you submit to Certification.
If a title supports joinable multiplayer experiences, the BVT team also verifies that system joins and invites work as expected. Titles must allow a user to send invites from within the game to those joinable experiences. The most common issues are described in the following sections.

Joinable game sessions

Titles that offer joinable game sessions must enable joinability through the XBOX shell interface. The BVT team verifies joining a session from within the title and from outside the title, when the title is terminated or suspended. Failure examples include:
  • A user can’t join a public lobby from the system shell.
  • The title doesn’t transition a user into a session when they join from the system shell.
Guidance:
Verify that a user can join multiplayer experiences through the XBOX shell interface while the title is running, terminated, and suspended. Verify that each joinable multiplayer experience allows a user to join from the system shell.

Game invitations

Games that support joinable multiplayer experiences must allow players to send game invitations using the XBOX network platform from within the game to other XBOX network users, including scenarios where cross-network players are present. Failure examples include:
  • The title supports joinable multiplayer experiences but doesn’t support game invitations from within the game.
  • The title doesn’t transition a user into the expected multiplayer experience when they accept a game invitation.
Guidance:
For games that support joinable multiplayer experiences, verify that there’s an invite option within the game.

Downloadable content (DLC)

Games that support durable and consumable add-ons must have at least one product for each supported type of downloadable content (DLC) submitted for testing with the game. For example, a racing game that supports track packs, car packs, and packs of virtual currency needs to certify at least one track, one car, and one virtual currency pack add-on. DLC packages must be located in the Store through search or deep-linking, and the BVT team checks their installation and in-title presence. For the test, see BVT-03 DLC. Guidance:
Publish at least one product for each supported DLC type to the CERT and CERT.DEBUG sandboxes before you submit, so the Certification team can download it.

Achievements fail to unlock (PC)

The title doesn’t unlock all achievements when the criteria are met. Guidance:
Verify that all achievements unlock when the criteria are met.

Submission Validator and build ID mismatch

The BVT team verifies that the <BuildId> in the Submission Validator log matches the <BuildId> of the package submitted for Certification. Examine the log for any failures or warnings. Separately, the BVT team checks that the FullName of the installed package matches the package name in your submission documents. For that test, see BVT-10 Version Check. Any <failure> tag designates a condition that causes your submission to be rejected during content ingestion and Certification. Although nothing prevents you from submitting such a package, doing so likely causes delays. Correct the problems identified until the log contains no <failure> tags. You might also see <warning> tags in the log. These generally indicate issues that might require an exception. If you have questions about any warnings, reach out to your Microsoft contact. Even if you’re granted an exception for your title, the <warning> tag still appears in the log file. For a full list of log messages, see Submission Validator Messages.

Basic configuration

Titles must not require any changes to the default device settings to run. The BVT team launches the title and verifies that no device settings need to be changed to test the game. For the test, see BVT-07 Basic Configuration. In rare instances, a title might require the DNS to be changed to connect to partner services. Discuss this with your Microsoft contacts before you submit. An approved exception is required.

Offline availability

The BVT team is the first to check how a title operates in offline scenarios. Some of the most common failures are crashing on launch and becoming indefinitely unresponsive when attempting to get past the initial engagement prompt. Guidance:
Add launching the title in an offline state to your testing before you submit a final package for Certification. Make sure that all menus and game modes can be navigated successfully, or that a user can reach a reasonable location to receive an appropriate error prompt when and where online connectivity is required.

Language support

The BVT team ensures the title launches, remains stable, and is localized to all supported languages. The Submission Validator log and the in-title language picker (if supported) determine the intended language support. For the test, see BVT-05 Languages. Guidance:
Make sure the title launches and can be played as expected in each supported language.

Intelligent Delivery

Titles that support Intelligent Delivery must be configured properly before submission. The BVT team verifies the level of support and that the content installs as expected from the Store. For the test, see BVT-15 Intelligent Delivery.

Pre-order stub files

When you submit a pre-order stub file, the BVT team verifies that the package includes the correct Store ID. Guidance:
Confirm that the correct Store ID is included in the package.
Last modified on November 17, 2026