Windows Server 2022 stuck with Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package. Cannot remove it (0x800f0825) and cannot install cumulative updates like KB5078766. Already tried DISM Set-Edition and Remove-Package."

Question

Windows Server 2022 stuck with Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package. Cannot remove it (0x800f0825) and cannot install cumulative updates like KB5078766. Already tried DISM Set-Edition and Remove-Package."

OEM Key.

Answer 1

Hi,

Problem: Impossible to install Cumulative Updates (specifically KB5078766) after converting Windows Server 2022 from "Evaluation" to "Standard" edition. DISM commands fail with "Component Store Corrupt" (0x80073712 / 0x800f081f), usually hanging at 3.0%.

Step-by-step Solution:

1. Identify the culprit: Analyze C:\Windows\Logs\CBS\CBS.log and search for the CorruptManifest error. Identify the exact name of the missing component. (In my case: amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.20348.3451_none_f0240fd1de32a8f6.manifest).
2. Get a clean source: Copy the matching .manifest file from a healthy, fully updated identical server (Path: C:\Windows\WinSxS\Manifests\).
3. Force Injection: Use a tool like PowerRun (to gain TrustedInstaller privileges) or boot into Command Prompt to copy the manifest into the destination folder, as it is protected by system permissions.
4. Repair the Store: Run the repair command pointing to your healthy server as a source: Dism /Online /Cleanup-Image /RestoreHealth /Source:\\HealthyServer\C$\Windows\WinSxS /LimitAccess
5. Reboot server
6. Finalize & Install:
   • Download the KB (.msu) from the Microsoft Update Catalog and extract it: expand -f:* C:\Path\To\KB_File.msu C:\temp\
   • First, install the SSU (Servicing Stack Update): dism /online /add-package /packagepath:C:\temp\SSU-20348.4880-x64.cab
   • Reboot the server.
   • Finally, install the Cumulative Update: Dism /Online /Add-Package /PackagePath:C:\Temp\Windows10.0-KB5078766-x64.cab

In the hope that this might help others !

Answer 2

Hello Jan Vidar Solberg, thank you for posting in the Microsoft Q&A community. I understand you are running Windows Server 2022 Standard and are currently unable to install cumulative updates like KB5078766 due to a leftover ServerStandardEval-Eval-Package, which returns error 0x800f0825 when you try to remove it. You are also looking for a way to obtain the correct non-Evaluation media since you only have an OEM license.

When converting an Evaluation edition to a Retail or Standard edition using the DISM /Set-Edition command, the servicing stack successfully updates the system's licensing and registry values. However, in some instances, it fails to completely purge the Evaluation licensing packages from the Component-Based Servicing (CBS) store. The error code 0x800f0825 translates to CBS_E_CANNOT_UNINSTALL. This indicates the package is marked as a permanent foundation package in the system and is locked by the servicing stack. When Cumulative Updates subsequently attempt to install, they detect a mismatch between your currently active OS edition (Standard) and these locked evaluation packages, causing the installation to roll back or fail.

Since the servicing stack is currently locked in an inconsistent state, the officially supported resolution is to perform an in-place repair upgrade. Because you have an OEM license and require the non-Evaluation ISO, you can obtain this directly from your hardware manufacturer. Microsoft provides OEM media securely to original equipment manufacturers. You can download the correct Retail/OEM ISO by visiting your specific server manufacturer's support portal (such as the Dell OS Recovery Tool, HPE My Enterprise Software center, or Lenovo Digital Download Recovery Service) and entering your server's hardware Service Tag or Serial Number. Alternatively, if your organization has any active standard business agreements or volume licensing, the identical non-Evaluation ISO can be downloaded from the Microsoft 365 Admin Center under Billing > Your products > Volume licensing. Once you have obtained the correct ISO, mount it and run setup.exe, making sure to select Keep personal files and apps to perform the in-place repair without losing your roles, features, or data.

If you are unable to obtain the ISO immediately and need an alternative method to force the package removal, you can modify the CBS registry state. Please note that this is an advanced step, and you must ensure you have a full backup or VM snapshot before proceeding.

1. Open Registry Editor (regedit.exe) as an Administrator.
2. Navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1
3. You will need to take ownership of this registry key to modify it: Right-click the package key, select Permissions, and click Advanced. Change the Owner at the top to the Administrators group. Check the box for Replace owner on subcontainers and objects, click Apply, and then grant Full Control to the Administrators group.
4. Inside the key, locate the Visibility DWORD value. Double-click it and change the value data from 2 (Hidden/Locked) to 1 (Visible).
5. Open an elevated Command Prompt and attempt to remove the package again using the following command:

DISM /Online /Remove-Package /PackageName:Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1

6. Restart your server and attempt to install the latest Cumulative Update.

To help us further isolate the issue if the above steps do not immediately resolve the problem, could you please provide the specific error code that Windows Update throws when KB5078766 fails to install (for example, 0x80070003 or 0x800f0988)? Additionally, please attempt the update and share the most recent log snippet from C:\Windows\Logs\CBS\CBS.log capturing the failure.

I will follow up on this thread to ensure your issue is resolved. If this helps, please consider 'Accepting' the answer.

For more details on best practices and servicing stack troubleshooting, please refer to the following official Microsoft documentation:

• Upgrade and conversion options for Windows Server
• Troubleshoot Windows Server Update issues

Answer 3

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.

Answer 4

The Microsoft-Windows-Security-SPP-Component-SKU-ServerStandardEval-Eval-Package is part of the licensing and editioning stack. It cannot be removed directly with DISM, and cumulative updates will fail if the image is in an inconsistent or blocked licensing state.

Because DISM /Set-Edition and /Remove-Package have already been tried and the package still cannot be removed (0x800f0825) and updates like KB5078766 will not install, the supported path is to repair or reinstall the current Windows Server installation so that the licensing and servicing stack are reset to a clean state.

Relevant points from the servicing and licensing components:

• The Microsoft-Windows-Security-SPP component is responsible for resetting licensing values and restoring the computer to a clean-install licensing state. When the licensing state is corrupted or blocked, servicing (including cumulative updates) can fail.
• Edition changes are supported only in the direction of a higher edition and must follow DISM edition-servicing rules. Once an image has been changed, /Set-Edition should not be used again on the same image.
• When the edition or licensing state is not aligned with what the servicing stack expects, cumulative updates may fail and cannot be fixed by package removal alone.

Given that:

1. The eval SKU package is still present and cannot be removed.
2. DISM /Set-Edition has already been attempted.
3. Cumulative updates fail repeatedly.

The practical resolution is to:

1. Perform an in-place repair/reinstall of the current Windows Server 2022 installation from matching media, keeping roles, features, and data.
2. After the repair, confirm the edition and licensing state are correct (OEM key applied to the non-eval edition).
3. Run Windows Update again to install the latest cumulative updates.

If the in-place repair does not clear the eval SKU package or servicing errors, a clean installation of Windows Server 2022 with the OEM key, followed by role/data migration, is required to fully remove the evaluation SKU remnants and restore normal update behavior.

---

References:

• Microsoft-Windows-Security-SPP
• DISM Windows Edition-Servicing Command-Line Options
• KB5079473 fail with 0x80073712 while inplace upgrade fail with 0x8007042B - Microsoft Q&A
• Latest Security Update KB5079473 (26200.8037) Fails to Install - Microsoft Q&A
• Windows 11, version 25H2 Install error - 0x800f081f BE FIXED? - Microsoft Q&A
• windows 11version 25H2 couldn't install, error 0x80070476 - Microsoft Q&A