.NET 10.0.12 Hosting Bundle Installation Success but Application Failures After .NET 10.0.11 Removal

Ravi Chandra Parepalli 0 Reputation points
2026-10-09T00:39:10.1933333+00:00

We recently deployed the .NET 10.0.12 Hosting Bundle to our servers via Tanium. Although the deployment status indicates a successful installation, we have observed that some servers still retain older .NET Hosting Bundle versions.

After identifying this, we manually removed the .NET 10.0.11 Hosting Bundle from the affected servers. Following the removal, only a small subset of applications started returning HTTP 500 errors, while several other applications running on .NET 10 continue to function without any issues.

Could you please help us understand:

  • Why only specific applications were impacted after the removal of the .NET 10.0.11 Hosting Bundle, while other .NET 10 applications remain unaffected?
  • What could be the possible reasons for the .NET 10.0.12 Hosting Bundle installation not being fully applied on some servers despite Tanium reporting a successful installation?
  • Are there any known dependencies, runtime binding, IIS hosting configuration, or deployment-specific factors that could cause this behavior?
Developer technologies | ASP.NET Core | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-09T00:39:31.0933333+00:00

    The most likely explanation is that the affected apps depended on components or configuration that were no longer available or correctly registered after the 10.0.11 removal, while the unaffected apps either targeted frameworks still present on the server or didn’t rely on the missing pieces.

    Supported causes from the documented behavior:

    1. Servicing updates replace prior updates, but only after successful installation .NET 10 servicing updates are upgrades, and installing 10.0.12 should remove 10.0.11 automatically upon successful installation. If 10.0.11 remained on some servers, that indicates the update may not have been fully applied on those machines.
    2. Some apps can fail if the required runtime or shared framework isn’t present A common startup failure is that the app targets a version of the ASP.NET Core shared framework that isn’t installed on the target machine. In IIS, this can surface as startup failures or HTTP 500 errors.
    3. Framework-dependent deployments are sensitive to server runtime state If an app is framework-dependent and the required .NET runtime isn’t installed, the app can fail to launch. For IIS-hosted ASP.NET Core apps, the documented fix is to install the .NET Hosting Bundle on the server.
    4. IIS/ANCM registration can be incomplete until repair or restart If the Hosting Bundle is installed before IIS, the bundle installation must be repaired after IIS is installed. Also, after installing a required runtime, the installation should be completed by restarting the system or restarting IIS with: net stop was /y net start w3svc
    5. Hosting Bundle corruption or incomplete registration can affect only some apps Documented startup guidance states that installing or repairing the .NET Hosting Bundle may fix app startup problems. This aligns with cases where only a subset of apps fail because their startup path exercises the broken dependency or module registration.
    6. Older Windows servers may also require the VC++ redistributable On older Windows versions such as Windows Server 2012 R2, the Visual Studio C++ Redistributable is required. Without it, the Windows Event Log can show the confusing message The data is the error.

    Why only some applications were impacted:

    • They may target a shared framework version not present after the removal.
    • They may be framework-dependent, while others are less dependent on the server-installed runtime state.
    • They may hit startup paths that expose Hosting Bundle or ASP.NET Core Module registration problems.
    • They may require native dependencies that other .NET 10 apps on the same server don’t use.

    Why 10.0.12 may have appeared successful but not fully applied:

    • The servicing update did not complete successfully on those servers, since 10.0.11 should have been removed automatically after a successful 10.0.12 installation.
    • IIS or the system may not have been restarted after installation.
    • The Hosting Bundle may need a repair, especially if IIS was installed after the bundle.
    • On older Windows versions, missing VC++ redistributables can leave the environment unusable even when the bundle install reports success.

    Recommended verification path:

    1. On an affected server, check the Application Event Log for startup errors.
    2. Confirm the app is not failing because the targeted ASP.NET Core shared framework is missing.
    3. Repair the installed .NET Hosting Bundle.
    4. Restart the server or restart IIS using: net stop was /y net start w3svc
    5. If the server is an older Windows version, verify the Visual C++ Redistributable is installed.
    6. If the issue is isolated to specific apps, run the app from a command prompt on the server or enable ASP.NET Core Module stdout logging to identify the exact startup failure.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Nguyen Dam (WICLOUD CORPORATION) 685 Reputation points Microsoft External Staff Moderator
    2026-10-09T03:37:39.4433333+00:00

    Hello @Ravi Chandra Parepalli and thank you for your questions. 

    From what you've described, this seems to be a broken/incomplete Hosting Bundle deployment. You will want to check around that by doing the following: 

    1. Run dotnet --list-runtimes on one broken server 
    2. Compare that against a working server. 
    3. Check the exact IIS error and Windows Application Event Log entry for the failing application.
    4. Repair/re-run the 10.0.12 Hosting Bundle installer, then restart IIS/the server as appropriate. 
    5. Check whether the failing apps are framework-dependent vs self-contained, and x86 vs x64. 

    For how to do the above, you can refer to the ASP.NET Core troubleshoot on AAS and IIS guide.
    Also, there's still a lack of data to know what really happened, so you may want to use the same guide to gather more diagnostic information and narrow down the cause. Other than that, you could check through the AI answer and see if anything there provides you with useful information - I won't repeat it here to avoid redundancy. 
    (I also highly recommend reading through the Hosting Bundle guide as it may contain helpful information.) 

    So that's the tentative answer for your 1st and 2nd questions: broken/incomplete deployment. The 3rd question is quite broad, and I wouldn't rule out any of these without further diagnostics. 

    If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.

    Was this answer helpful?

    0 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.