.net core 8.0.10 hosting bundle doesn't install components

Hi Neil,

Thank you for sharing your observation regarding the .NET Core 8.0.10 Hosting Bundle.

In earlier versions of the Hosting Bundle, installation typically included:

Both x64 and x86 versions of the .NET Runtime

ASP.NET Core Shared Frameworks (x64 and x86)

With version 8.0.10, it appears that only a single entry — “Microsoft .NET 8.0.10 - Windows Server Hosting” — is shown, and the expected individual runtime components are no longer listed as before.

This behavior could be the result of a few factors:

Changes to the Installer Packaging: Microsoft may have made internal changes to the installer’s structure, affecting how components are registered or displayed after installation.

Silent Install Failures: In some cases, required system components or roles (e.g., IIS-related features) may be missing, preventing parts of the bundle from installing fully.

Visual Reporting Differences: It's possible that the components are installed but no longer listed individually in Programs & Features, due to updates in how the installer chains and reports its components.

Here are some suggested steps for you:

1. Confirm Runtime Availability:

• Open a command prompt and run the following command to check the installed .NET runtimes: dotnet --list-runtimes. This will display a list of all .NET runtimes installed on your system, including versions and architectures (e.g., x64, x86).
• Create a simple .NET application (e.g., a console app with a basic Console.WriteLine("Hello, .NET!");) using a text editor and save it as test.cs. Compile and run it using dotnet run after navigating to the directory in the command prompt. If it executes successfully, the runtime is likely installed.
• For ASP.NET Core, create a minimal API project using dotnet new web -o testapi and run it with dotnet run. Access it via a browser (e.g., https://localhost:5001). Successful execution confirms the ASP.NET Core runtime is available.

2. Review Installer Logs:

• Navigate to the temporary directory where installer logs are stored, typically C:\Users<YourUsername>\AppData\Local\Temp. Look for log files with names containing "dotnet" or "hosting" and a timestamp matching your installation date (e.g., dd_dotnet_sdk_8.0.10.log).
• Open the most recent log file with a text editor and search for keywords like "error," "fail," "skip," or "install" to identify any issues. Note any error codes or missing dependencies.
• Alternatively, check the Windows Event Viewer: Open eventvwr, expand "Windows Logs" > "Application," and filter for events from the installer (look for "Microsoft" or ".NET" sources around the installation time).

At this point, it's unclear whether this is by design or an oversight in packaging for version 8.0.10. Your findings are helpful and worth reporting through official support channels if the issue persists. In the meantime, using the above suggestions should help ensure that your environment is complete and functional.

Hope this helps!

That also seems to be a problem I am encountering as for a successful install we check to see that all 3 are installed and now only one of them is. It looks like the x64/x86 shared frameworks are not getting installed any more or at least are now no longer separate pkgs in the hosting bundle? Thats why its called a bundle as it is 3 pieces.

Hi,

Seems you want to install the latest SDK rather than just the hosting bundle?

Which version of VS do you have? What if you are just using "Visual Studio Installer" and then https://learn.microsoft.com/en-us/dotnet/core/install/how-to-detect-installed-versions?pivots=os-windows#check-sdk-versions to check the latest 8.0.403 is installed?

The hosting bundle is for production servers.

Edit: even if using Visual Studio Code, it seems to me you want to install the SDK rather than only just the hosting bundle.

After the updates installed [Microsoft ASP.NET Core Runtime 8.0 8.0.10] on my machine and when I try running Visual Studio, it just errors with "Unable to connect to web server 'StartUpProject'" After uninstalling the update, then VS worked again