Windows Update fails to install because the update package is for a different operating system.

JIN FUKUMITSU (福光 仁) 0 Reputation points
2026-10-22T04:22:32.74+00:00

Overview

PC Name: r2090549

Departmental server located at TW

OS: Windows Server 2022

Deployed: January 2026

Issue

Windows Updates cannot be applied because all updates distributed to date have been packages intended for Windows 10 or 11.

2021-08 Servicing Stack Update for Windows 10 Version 21H1 for x86-based Systems (KB5005260)

2021-08 Servicing Stack Update for Windows 10 Version 21H1 for ARM64-based Systems (KB5005260)

2021-08 Servicing Stack Update for Windows 10 Version 21H1 for x64-based Systems (KB5005260)

2026-07 Cumulative Update for Windows 10 Version 22H2 for ARM64-based Systems(KB5099539)

2026-07 Cumulative Update for Windows 11, version 23H2 for x64-based Systems (KB5099414)

2026-07 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5099539)

2026-07 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5099414)

2026-07 Cumulative Update for Windows 10 Version 22H2 for x86-based Systems (KB5099539)

<Update Package History for Windows Server 2022 (Official Microsoft Source)>

Release KB OS Build

2026-01-13 KB5073457 20348.4648 ← Currently installed package

2026-01-17 KB5077800(OOB) 20348.4650

2026-01-24 KB5078136(OOB) 20348.4651

2026-02-10 KB5075906 20348.4773

2026-03-02 KB5082314(OOB) 20348.4776

2026-03-10 KB5078766 20348.4893

2026-04-14 KB5082142 20348.5020

2026-04-19 KB5091575(OOB) 20348.5024

2026-05-12 KB5087545 20348.5139

2026-06-09 KB5094128 20348.5256

2026-07-14 KB5099540 20348.5386

2026-08-11 KB5120242 20348.5499

Details


PS C:\Windows\system32> $a = Get-WmiObject -Namespace root\ccm\Policy\Machine\ActualConfig -Class CCM_UpdateCIAssignment PS C:\Windows\system32> "CI count = " + $a.AssignedCIs.Count CI count = 8 PS C:\Windows\system32> $a.AssignedCIs | ForEach-Object { $_ } <?xml version='1.0' ?> <CI> <ID>a5e40bf9-f1dc-4e6d-93e7-b62c6bf1ce3e</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_a5e40bf9-f1dc-4e6d-93e7-b62c6bf1ce3e</ModelName> <Version>1.00</Version> <CIVersion>201</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>a5e40bf9-f1dc-4e6d-93e7-b62c6bf1ce3e</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>1</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2021-08 Servicing Stack Update for Windows 10 Version 21H1 for x86-based Systems (KB5005260)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>7e3f8de3-92dc-4be5-af2a-afe9ee9d99d0</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_7e3f8de3-92dc-4be5-af2a-afe9ee9d99d0</ModelName> <Version>1.00</Version> <CIVersion>201</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>7e3f8de3-92dc-4be5-af2a-afe9ee9d99d0</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>1</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2021-08 Servicing Stack Update for Windows 10 Version 21H1 for ARM64-based Systems (KB5005260)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>c17fa914-7ed2-428f-89a5-1a6131f7e0f1</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_c17fa914-7ed2-428f-89a5-1a6131f7e0f1</ModelName> <Version>1.00</Version> <CIVersion>201</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>c17fa914-7ed2-428f-89a5-1a6131f7e0f1</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>1</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2021-08 Servicing Stack Update for Windows 10 Version 21H1 for x64-based Systems (KB5005260)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>67b5cf89-4ae8-4f88-aff2-6b9ec689cb5e</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_67b5cf89-4ae8-4f88-aff2-6b9ec689cb5e</ModelName> <Version>1.00</Version> <CIVersion>200</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>67b5cf89-4ae8-4f88-aff2-6b9ec689cb5e</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>168</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2026-07 Cumulative Update for Windows 10 Version 22H2 for ARM64-based Systems (KB5099539)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>5ef75f96-f55c-4e0d-bbeb-49256d17417e</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_5ef75f96-f55c-4e0d-bbeb-49256d17417e</ModelName> <Version>1.00</Version> <CIVersion>100</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>5ef75f96-f55c-4e0d-bbeb-49256d17417e</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>168</Version></CISource><ProductId>72e7624a-5b00-45d2-b92f-e561c0a6a160</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2026-07 Cumulative Update for Windows 11, version 23H2 for x64-based Systems (KB5099414)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>0c7356a2-239e-40e5-aa6c-3114ca1bdf83</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_0c7356a2-239e-40e5-aa6c-3114ca1bdf83</ModelName> <Version>1.00</Version> <CIVersion>200</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>0c7356a2-239e-40e5-aa6c-3114ca1bdf83</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>168</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2026-07 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5099539)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>067b706e-432f-442c-b0c1-cf3e1e732aac</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_067b706e-432f-442c-b0c1-cf3e1e732aac</ModelName> <Version>1.00</Version> <CIVersion>100</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>067b706e-432f-442c-b0c1-cf3e1e732aac</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>168</Version></CISource><ProductId>72e7624a-5b00-45d2-b92f-e561c0a6a160</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2026-07 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5099414)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> <?xml version='1.0' ?> <CI> <ID>cb5c5834-a942-470c-b024-656fe4614bf8</ID> <ModelName>Site_69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B/SUM_cb5c5834-a942-470c-b024-656fe4614bf8</ModelName> <Version>1.00</Version> <CIVersion>200</CIVersion> <ApplicabilityCondition> <ApplicabilityRule ExpressionLanguage="Custom" Handler="{2DB70103-3DFB-4806-85B0-B27B561284BB}"><UpdateId>cb5c5834-a942-470c-b024-656fe4614bf8</UpdateId><CISource><Id>{69CE8C9B-37BD-40D8-8184-B8DCEE76ED3B}</Id><Version>168</Version></CISource><ProductId>b3c75dc1-155f-4be4-b015-3f1a91758e52</ProductId></ApplicabilityRule> </ApplicabilityCondition> <EnforcementEnabled>FALSE</EnforcementEnabled> <DisplayName>2026-07 Cumulative Update for Windows 10 Version 22H2 for x86-based Systems (KB5099539)</DisplayName> <UpdateClassification>0fa1201d-4330-4fa8-8ae9-b877473b6441</UpdateClassification> </CI> PS C:\Windows\system32>

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

2 answers

Sort by: Newest
  1. VPHAN 47,440 Reputation points Independent Advisor
    2026-10-22T05:13:22.2233333+00:00

    Your Windows Server 2022 machine cannot install updates because your Configuration Manager environment is deploying the wrong update packages to it. The WMI query results clearly show that the server is successfully receiving management policies, but it is being assigned Windows 10 and 11 patches rather than server updates. The operating system correctly evaluates these workstation packages as inapplicable, leaving your server stranded on the January 2026 build (KB5073457).

    To resolve this, log into your Configuration Manager site server and audit your collection memberships to ensure this machine is not mistakenly grouped into a workstation deployment collection. You must also check the Software Update Point component properties to verify that Windows Server 2022 is selected under the Products tab. If it was missing, check the wsyncmgr.log after making the change to confirm the site server successfully synchronizes the new server catalog metadata from Microsoft.

    Once synchronized, adjust your Automatic Deployment Rules to target the Server 2022 product category and generate a new Software Update Group containing the correct cumulative updates, such as the July 2026 update (KB5099540) or the August 2026 update (KB5120242). If you use an automated rule, you can verify its success by checking the ruleengine.log. After deploying the corrected group to your server collection, run a Machine Policy Retrieval & Evaluation Cycle from the local Configuration Manager Control Panel applet on the affected server to clear the old assignment and retrieve the correct updates.

    Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VPHAN

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-10-22T04:23:35.8166667+00:00

    The Configuration Manager deployment targeting this server must be corrected: its CCM_UpdateCIAssignment policy contains eight Windows 10/11 updates and no Windows Server 2022 cumulative update, so revise the originating software update group or ADR and deploy the Server 2022 update to the correct server collection.

    EnforcementEnabled=FALSE also means the displayed assignment is not currently enabled for enforcement; it does not make those client updates applicable to Server 2022.

    1. Identify and remove the incorrect deployment

    In the Configuration Manager console:

    1. Go to Monitoring → Deployments.
    2. Locate the software-update deployment targeting this device or its collection.
    3. Add or inspect the Deployment Unique ID and compare its assigned updates with the eight CIs shown in WMI.
    4. Open the deployment’s software update group under Software Library → Software Updates → Software Update Groups.
    5. Remove the Windows 10/11 updates from that server-specific group, or disable/delete the deployment if the entire assignment is wrong.
    6. Inspect the target collection membership. Remove the server from any workstation update collection unless membership is intentional.

    Configuration Manager creates deployment assignment policy containing the updates in the software update group, then sends that machine policy to clients in the targeted collection.^1^ The client-side WMI output therefore shows which deployment policy reached this server; it is not evidence that Windows Server considers those packages applicable.

    If an ADR created the deployment:

    1. Go to Software Library → Software Updates → Automatic Deployment Rules.
    2. Open the rule responsible for the July deployment.
    3. On Software Updates, change its criteria so the server ADR selects only the required Windows Server 2022 updates.
    4. On Deployment Settings/Deployment Package, verify it targets the intended server collection.
    5. Run the ADR manually and review the resulting update group before enabling its deployment.

    An ADR evaluates its criteria, downloads matching updates, creates or updates a software update group, and creates the deployment assignment.^2^

    2. Synchronize the Windows Server 2022 catalog

    Perform this at the top-level site:

    1. Open Administration → Site Configuration → Sites.
    2. Select the central administration site or stand-alone primary site.
    3. Select Configure Site Components → Software Update Point.
    4. On Products, select Windows Server 2022.
    5. On Classifications, select the classifications used by your servicing process—normally at least Security Updates, Critical Updates, and Update Rollups where applicable.
    6. Close the properties.
    7. Go to Software Library → Software Updates → All Software Updates and select Synchronize Software Updates.
    8. After synchronization completes, search for the required Windows Server 2022 KB and confirm its metadata appears.

    Configuration Manager retrieves only the update metadata matching the configured products and classifications. After selecting a newly required product, another synchronization is necessary.^3^

    Do not select unnecessary products merely to troubleshoot this server. Clients evaluate synchronized metadata during scans, and excess products increase catalog size and can reduce scan performance.^4^

    Seeing a Windows 10/11 title in the console alone does not always prove incorrect product selection because an update applicable to multiple synchronized products can display all associated products. In this case, however, those updates are present in the client’s assigned deployment, so both deployment contents and collection targeting require inspection.^3^

    3. Create the corrected Server 2022 deployment

    After synchronization:

    1. In All Software Updates, search for the applicable Windows Server 2022 cumulative update.
    2. Confirm it is not Expired or Superseded according to your deployment policy.
    3. Add it to a server-specific software update group.
    4. Download and distribute its content to the distribution point used by the server.
    5. Deploy that group to the Windows Server 2022 collection.
    6. Trigger these client actions from Control Panel → Configuration Manager → Actions:
      • Machine Policy Retrieval & Evaluation Cycle
      • Software Updates Scan Cycle
      • Software Updates Deployment Evaluation Cycle
    7. Confirm the new update appears as Required or Available in Software Center, according to the deployment purpose.

    At evaluation time, Configuration Manager requests another update scan to verify that each deployed update remains applicable before installation.^5^

    4. Trace the boundary if Server 2022 updates remain absent

    Because the assignment has already been inspected, do not reset SoftwareDistribution or the Configuration Manager client yet. Trace where the correct update disappears:

    • Site server
      • wsyncmgr.log: synchronization and metadata import
      • WCM.log: SUP products, classifications, and WSUS connection
      • WSUSCtrl.log: WSUS health and database connectivity
      • ruleengine.log: ADR selection, update-group creation, and deployment
    • Client
      • PolicyAgent.log and PolicyEvaluator.log: receipt/evaluation of corrected policy
      • UpdatesDeployment.log: deployment evaluation
      • WUAHandler.log and ScanAgent.log: applicability scan

    Microsoft documents these server-side log purposes in the Configuration Manager log reference.^6^

    Expected result: the old assignment is withdrawn after policy refresh, a new assignment contains the Windows Server 2022 CI, and the scan reports that update’s applicability. If wsyncmgr.log never imports the Server 2022 KB, the issue remains at SUP/WSUS synchronization; if it imports successfully but ruleengine.log excludes it, correct the ADR criteria; if the correct deployment exists server-side but is absent from client policy, correct collection membership or policy targeting.


    References

    1. Introduction to software updates in Configuration Manager
    2. Automatically deploy software updates
    3. Configure classifications and products to synchronize
    4. Install and configure a software update point
    5. Track the software update deployment process in Configuration Manager
    6. Log file reference
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.