Share via

AppX Deployment Service (AppXSVC) andInventory and Compatibility Appraisal service are continuously aborting on OS 2025 especially

Srinivas Dave 0 Reputation points
2026-03-30T10:01:01.7533333+00:00

Hi Team ,

AppX Deployment Service (AppXSVC) andInventory and Compatibility Appraisal service are continuously aborting on OS 2025 especially.

couold soem one share the solution

Windows for business | Windows Server | User experience | Other
0 comments No comments

3 answers

Sort by: Most helpful
  1. Tracy Le 5,295 Reputation points Independent Advisor
    2026-03-31T12:07:16.74+00:00

    Hi Srinivas Dave,

    I just wanted to follow up and see if you had the opportunity to implement the recommendations provided above. Were you able to successfully stabilize the AppX Deployment Service and the Inventory and Compatibility Appraisal service by verifying the physical installation of KB5072033 and ensuring its startup state remains strictly set to Automatic across your server fleet?

    If your organization's GPOs are still overriding these settings causing the services to crash, or if you are still experiencing silent update failures via WSUS and need help checking the local logs, please do not hesitate to reach out. I am always here to help you get this resolved!

    Tracy.

    0 comments No comments

  2. Tracy Le 5,295 Reputation points Independent Advisor
    2026-03-30T10:38:55.05+00:00

    Hi Srinivas Dave,

    The continuous aborting of the AppX Deployment Service (AppXSVC) and the Inventory and Compatibility Appraisal service on Windows Server 2025 is a known stability issue that stems from how the operating system handles component servicing and startup triggers. Microsoft recently addressed this underlying behavior by releasing the December 9, 2025 cumulative update, specifically KB5072033, alongside its mandatory Servicing Stack Update, KB5071142. To resolve these persistent crashes, your primary step must be to verify that both of these specific updates are successfully installed on your affected servers, as they contain critical reliability improvements that directly stabilize the servicing stack and prevent these deployment services from terminating unexpectedly.

    Beyond merely installing the update, it is crucial to understand that KB5072033 explicitly modifies the default operational state of the AppX Deployment Service by changing its startup type directly to Automatic. If your organization utilizes Group Policy Objects (GPOs), automated hardening scripts, or third-party security tools that force AppXSVC back to a Manual or Disabled state, the service will inevitably conflict with the new OS baseline and continue to abort. You must review your server configurations and ensure that the AppXSVC startup type is strictly allowed to remain on Automatic, rebooting the machine afterward to allow the service to initialize cleanly without administrative interference.

    Finally, if your server fleet is managed through Windows Server Update Services (WSUS), you should be aware that recent security mitigations (such as for CVE-2025-59287) have altered how WSUS reports synchronization errors, occasionally causing update deployments to fail silently. Therefore, rather than relying solely on the WSUS dashboard, administrators should manually verify the local update history on the affected Server 2025 machines to guarantee that KB5072033 has been physically applied. Combining the installation of these targeted patches with the strict enforcement of the Automatic startup state will stabilize the appraisal and deployment services across your infrastructure.

    I hope the response provided some helpful insight. If it clarified the issue for you, please consider marking it as Accept Answer so others with the same issue can find the solution. Feel free to leave a comment if you need further information.

    Tracy

    0 comments No comments

  3. Q&A Assist
    2026-03-30T10:01:22.4033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    On Windows Server 2025 and related Windows builds, AppX Deployment Service (AppXSVC) behavior has recently changed via the December 9, 2025 update KB5072033. In this update, AppXSVC was explicitly moved to Automatic startup type to improve reliability in some scenarios.

    If AppXSVC and the Inventory and Compatibility Appraisal service are repeatedly aborting/crashing on OS 2025, recommended actions based on the current servicing guidance are:

    1. Confirm KB5072033 (and latest updates) are installed
      • On affected servers, install the December 9, 2025 update KB5072033 (OS Build 26100.7462 / 26200.7462) and the associated servicing stack update (KB5071142 for Windows Server 2025).
      • These updates include reliability improvements for system components and the servicing stack, which can stabilize services like AppXSVC.
    2. Verify AppXSVC startup configuration
      • After installing KB5072033, confirm that AppX Deployment Service (AppXSVC) is set to Automatic startup type (as intended by the update).
      • If it is set differently (e.g., Disabled or Manual) or controlled by GPO/hardening tools, restore it to Automatic and reboot.
    3. Ensure servicing stack is healthy
      • The Windows Server 2025 servicing stack update (KB5071142) improves the reliability of update and component servicing.
      • Install it if not already present, then recheck whether AppXSVC and the appraisal service still abort.
    4. Check for known WSUS/servicing issues if managed via WSUS
      • If the servers receive updates from WSUS, be aware that after KB5070881 or later, WSUS no longer shows detailed sync error information due to CVE-2025-59287 mitigation.
      • If update deployment is failing silently, that can indirectly affect component servicing and related services. Make sure the servers are actually current with KB5072033 and the latest SSU.

    If, after applying KB5072033 and the latest SSU and confirming AppXSVC is set to Automatic, the services still continuously abort, collect Application and System event logs around the crash times and open a support case, as no further remediation steps are documented in the provided material.


    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.