Share via

Cannot install windows update Server 2022

Jan Vidar Solberg 0 Reputation points
2026-04-09T07:01:03.13+00:00

Problem description:

I am running Windows Server 2022 Standard with a valid OEM product key. The server was originally installed from an Evaluation ISO and later converted using DISM /Set-Edition:ServerStandard + OEM key.

The following Eval package is still present and cannot be removed:

Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1

I have already tried the following without success:

  • DISM /Cleanup-Image /StartComponentCleanup /ResetBase
  • DISM /Remove-Package → Error 0x800f0825
  • DISM /Set-Edition:ServerStandard (multiple times)
  • /RevertPendingActions, SFC /scannow, component store reset, etc.

Because of this leftover Eval licensing package, cumulative updates (including the latest KB5078766) fail to install.

I do not have access to a non-Evaluation Windows Server 2022 ISO for an in-place repair upgrade. I only have a standard OEM product key (partial key ends with -F3PX2) and the Evaluation ISO.

My questions to Microsoft Support:

  1. How can I obtain the correct non-Evaluation Windows Server 2022 Standard ISO when I only have an OEM license?
  2. Is there another supported way to remove the remaining Eval-SPP package or reset the licensing/servicing stack without a full clean install?

I would prefer an in-place repair upgrade that keeps all roles, features, applications and data.

Additional information:

  • Current edition: ServerStandard (confirmed with dism /online /Get-CurrentEdition)
  • Product key is OEM (not Volume Licensing)
  • No Contract-ID / Access-ID available (OEM license only)

I can provide CBS.log, DISM.log, slmgr /dlv output or any other logs if needed.

Thank you for your assistance.Problem description:

I am running Windows Server 2022 Standard with a valid OEM product key. The server was originally installed from an Evaluation ISO and later converted using DISM /Set-Edition:ServerStandard + OEM key.

The following Eval package is still present and cannot be removed:

Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1

I have already tried the following without success:

  • DISM /Cleanup-Image /StartComponentCleanup /ResetBase
  • DISM /Remove-Package → Error 0x800f0825
  • DISM /Set-Edition:ServerStandard (multiple times)
  • /RevertPendingActions, SFC /scannow, component store reset, etc.

Because of this leftover Eval licensing package, cumulative updates (including the latest KB5078766) fail to install.

I do not have access to a non-Evaluation Windows Server 2022 ISO for an in-place repair upgrade. I only have a standard OEM product key (partial key ends with -F3PX2) and the Evaluation ISO.

My questions to Microsoft Support:

  1. How can I obtain the correct non-Evaluation Windows Server 2022 Standard ISO when I only have an OEM license?
  2. Is there another supported way to remove the remaining Eval-SPP package or reset the licensing/servicing stack without a full clean install?

I would prefer an in-place repair upgrade that keeps all roles, features, applications and data.

Additional information:

  • Current edition: ServerStandard (confirmed with dism /online /Get-CurrentEdition)
  • Product key is OEM (not Volume Licensing)
  • No Contract-ID / Access-ID available (OEM license only)

I can provide CBS.log, DISM.log, slmgr /dlv output or any other logs if needed.

Thank you for your assistance.

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

2 answers

Sort by: Most helpful
  1. Harry Phan 17,050 Reputation points Independent Advisor
    2026-04-09T08:58:43.29+00:00

    Hi Jan

    The leftover ServerStandardEval SPP package cannot be removed with DISM because it is tied to the servicing stack from the Evaluation media. Once the system is converted with /Set-Edition, the edition changes, but the evaluation licensing component remains in the component store and blocks cumulative updates. Microsoft does not provide a supported way to strip that package manually. The only supported resolution is an in‑place repair upgrade using non‑Evaluation installation media. Since you have an OEM key, you are entitled to the full Windows Server 2022 Standard ISO, but OEM media is not distributed directly by Microsoft—it must be obtained from your OEM vendor or through the Volume Licensing Service Center if you had VL rights. Without that ISO, there is no supported path to repair the servicing stack.

    In short, you need proper non‑Evaluation installation media to perform a repair upgrade; DISM cannot remove the Eval SPP package. If your OEM does not provide the ISO, the only alternative is a clean install with the correct media. There is no Microsoft‑supported method to reset the licensing stack or remove the Eval package in place.

    I hope it's helpful to you.

    0 comments No comments

  2. Q&A Assist
    2026-04-09T07:01:22.2366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    There is no supported method in the provided documentation to remove a leftover *Eval* SPP package from a converted Windows Server 2022 installation or to repair the servicing stack without using proper non‑evaluation installation media.

    The documented and supported paths for edition and license changes are:

    1. Convert an evaluation to a retail edition using DISM with a retail key:
      • Save and accept the EULA, then set the edition with product key:
             DISM /online /Set-Edition:<target edition> /GetEula:C:\license.rtf
             DISM /online /Set-Edition:<target edition> /ProductKey:<product key> /AcceptEula
        
      • Example for Datacenter:
             DISM /online /Set-Edition:ServerDatacenter /ProductKey:ABCDE-12345-ABCDE-12345-ABCDE /AcceptEula
        
    2. Convert between retail, volume, and OEM licenses (edition remains the same):
         slmgr.vbs /ipk <product key>
      
    3. Convert Windows Server Standard to Datacenter (same family, higher edition):
      • Confirm current edition:
             DISM /online /Get-CurrentEdition
        
      • Confirm valid target editions:
             DISM /online /Get-TargetEditions
        
      • Set edition with product key:
             DISM /online /Set-Edition:ServerDatacenter /ProductKey:<product key> /AcceptEula
        

    The DISM edition‑servicing options that are supported online are limited to:

    DISM.exe /Online {
      /Get-CurrentEdition |
      /Get-TargetEditions |
      /Set-ProductKey:<product_key> |
      /Set-Edition:<target_edition> {/GetEula:<path> | /AcceptEula /ProductKey:<product_key>}
    }
    

    There is no supported DISM command in the referenced documentation to selectively remove the evaluation SPP package from an already converted online image.

    For installation/servicing failures caused by product key or media mismatch, the documented resolution is to ensure that the product key and media match by using the correct EditionID and channel (OEM/Retail, VL) in EI.cfg or PID.txt, or by changing the product key to match the media being used. However, this guidance applies at install time, not to retroactively cleaning an already converted evaluation installation.

    The documentation also notes that in‑place repair using setup.exe from installation media keeps the same edition that is already installed, but it assumes access to the correct non‑evaluation media; it does not describe a way to generate or obtain that media from an OEM key alone.

    Based on the provided material:

    • How to obtain non‑evaluation ISO with only an OEM key is not covered.
    • A supported method to remove the remaining *Eval* SPP package or fully reset licensing/servicing without proper media or a clean install is not documented.

    References:

    0 comments No comments

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.