Fix 25H2 Enablement Package Pre-Check Failing on a Domain PC on Windows 11

When you attempt to install the 25H2 enablement package on a domain-joined Windows 11 PC, the pre-check may fail without a clear error message. This failure typically occurs because Group Policy blocks feature updates through the “Select the target Feature Update version” policy or because the system lacks the required 25H2 baseline build. Domain PCs often have stricter update controls than consumer devices, and the enablement package pre-check is designed to verify both the current OS build and policy compliance. This article explains why the pre-check fails on domain PCs and provides the specific Group Policy and registry changes to resolve the issue.

Why the 25H2 Enablement Package Pre-Check Fails on Domain PCs

The 25H2 enablement package is a small update that activates features already present in the 24H2 baseline build. The pre-check runs a series of validation steps before the package is applied. On domain PCs, two factors cause most failures.

First, many domain environments use Group Policy to control which feature update version the PC can install. The policy “Select the target Feature Update version” (TargetReleaseVersion) restricts the OS to a specific version. If this policy points to 24H2 or an earlier version, the pre-check detects the mismatch and blocks the enablement package.

Second, the enablement package requires the PC to be running Windows 11 build 26100 or higher. Domain PCs that were not updated to the latest 24H2 cumulative update may still be on build 22631 or lower. The pre-check will fail in this case because the enablement package cannot apply to an unsupported baseline.

Other causes include a corrupted Windows Update cache, missing required servicing stack updates, and third-party security software that intercepts update checks. These are less common on domain PCs but should be considered if Group Policy and build version are correct.

Steps to Fix the 25H2 Enablement Package Pre-Check on a Domain PC

Follow these steps in order. You need local administrator rights on the domain PC and the ability to modify Group Policy. If you cannot change Group Policy yourself, contact your domain administrator.

Step 1: Verify the Current Windows 11 Build

1. Open the Run dialog
   Press Windows key + R on your keyboard. Type winver and press Enter. A dialog box shows the Windows version and OS build number.
2. Check the build number
   Look for “Version 24H2” and a build number starting with 26100. If you see a lower build like 22631, the PC does not have the 24H2 baseline. Install all pending Windows updates until the build reaches 26100.
3. Install missing cumulative updates
   Open Settings > Windows Update and click Check for updates. Install any available cumulative updates. Restart the PC if prompted. Repeat until no more updates are offered and the build is 26100 or higher.

Step 2: Check and Update the Target Feature Update Version Policy

1. Open the Local Group Policy Editor
   Press Windows key + R, type gpedit.msc, and press Enter. If gpedit.msc is not available, you are on Windows 11 Home edition and must use the registry method in Step 3.
2. Navigate to the Target Release Version policy
   Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business. Double-click the policy named Select the target Feature Update version.
3. Set the policy to Not configured or update the version
   To allow any feature update, select Not configured and click OK. To keep version control but allow 25H2, select Enabled, set Target Version for Feature Updates to 25H2, and click OK.
4. Apply the change
   Close the Local Group Policy Editor. Open a Command Prompt as administrator and run gpupdate /force. Wait for the update to complete.

Step 3: Remove or Update the TargetReleaseVersionInfo Registry Value

1. Open Registry Editor
   Press Windows key + R, type regedit, and press Enter. Click Yes if prompted by User Account Control.
2. Navigate to the WindowsUpdate key
   Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. If the WindowsUpdate key does not exist, skip this step.
3. Modify the TargetReleaseVersionInfo value
   In the right pane, double-click TargetReleaseVersionInfo. If the value data is set to a version older than 25H2, change it to 25H2 and click OK. To remove the restriction entirely, delete the TargetReleaseVersionInfo value by right-clicking it and selecting Delete. Also delete the TargetReleaseVersion DWORD value if it exists.
4. Restart the PC
   Close Registry Editor and restart the computer to apply the registry changes.

Step 4: Run the Windows Update Troubleshooter

1. Open Settings
   Press Windows key + I, then go to System > Troubleshoot > Other troubleshooters.
2. Run the Windows Update troubleshooter
   Find Windows Update in the list and click Run. Follow the on-screen instructions. The troubleshooter will reset the Windows Update cache and repair corrupted components.
3. Restart and retry the enablement package
   After the troubleshooter completes, restart the PC. Go to Settings > Windows Update and click Check for updates. The 25H2 enablement package should now appear and install without the pre-check failure.

If the 25H2 Enablement Package Pre-Check Still Fails on a Domain PC

Pre-check fails with error 0x800f0922

Error 0x800f0922 indicates that the enablement package could not be applied because a required component is missing. This often occurs when the servicing stack update is not installed. Go to Settings > Windows Update > Advanced options > Optional updates. Look for a servicing stack update and install it. Then retry the enablement package.

Pre-check fails with error 0x80070005

Error 0x80070005 means access is denied. This happens when a third-party security application or a domain policy blocks the update. Temporarily disable any third-party antivirus software and retry. If the error persists, check the Event Viewer under Windows Logs > Application for events from source “Windows Update Client” with event ID 20 or 41. These events often contain the exact policy name or registry key that is blocking the update.

Group Policy is enforced by the domain controller and cannot be changed locally

If the domain administrator has locked the target version policy through a central Group Policy Object, local changes to gpedit.msc or the registry will be overwritten at the next policy refresh. In this case, contact your domain administrator and request that the policy be updated to allow version 25H2. Alternatively, ask for an exception for your specific PC using a security group and a filtered GPO.

Enablement package does not appear even after pre-check passes

If the pre-check no longer fails but the 25H2 enablement package does not appear in Windows Update, the PC may be in a deferral period set by Group Policy. Check the policy “Select when Preview Builds and Feature Updates are received” under the same Windows Update for Business path. Set it to not configured or ensure the deferral period is set to 0 days.

Item	Setting Before Fix	Setting After Fix
TargetReleaseVersion policy	Enabled with version 24H2 or older	Not configured or enabled with version 25H2
TargetReleaseVersionInfo registry value	Set to 24H2 or older	Deleted or set to 25H2
Windows 11 build number	22631 or lower	26100 or higher
Servicing stack update	Missing or outdated	Installed latest version

After completing these steps, the 25H2 enablement package pre-check on your domain PC should pass and the update should install successfully. If the issue persists, run the Windows Update troubleshooter again and verify that no third-party security software is interfering. For domain PCs with locked Group Policy, work with your IT administrator to update the target version policy to 25H2 or remove it entirely.