Update ASP.net Core

What the ASP.NET Core Updater does

This Automox Worklet™ identifies endpoints with outdated ASP.NET Core runtime installations and upgrades them to a version you specify. The Worklet queries the registry path SOFTWARE\Microsoft\ASP.NET Core\Shared Framework to detect installed versions for both x86 and x64 architectures.

When an installed version is older than your target version, the Worklet runs the appropriate installer (32-bit or 64-bit) silently with logging enabled. Endpoints that do not have ASP.NET Core installed are marked as not applicable, allowing you to target only endpoints that actually use the runtime.

The Worklet requires you to download the official ASP.NET Core installers from Microsoft and upload them to the Automox console. You must download the "Installers" rather than the "Binaries" to support in-place upgrades on endpoints with mixed architectures.

Why upgrade ASP.NET Core through Automox

Microsoft regularly releases ASP.NET Core updates that address security vulnerabilities, performance improvements, and bug fixes. Older runtime versions may contain known vulnerabilities that attackers can exploit in web applications running on your endpoints. Keeping runtimes current is a key part of maintaining application security.

Development teams often deploy applications that depend on specific ASP.NET Core versions. Automating runtime updates prevents version drift across your environment and reduces compatibility issues when deploying new applications that require recent runtime features.

The Worklet handles both workstations (developer machines) and servers (production environments), giving you a single tool to manage ASP.NET Core versions across your entire infrastructure.

How ASP.NET Core upgrades work

1. Evaluation phase: The Worklet reads the registry at HKLM:\SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v{major} for both 32-bit and 64-bit hives. It compares each installed version against the target version you specify in the $fVersion variable. Endpoints with older versions are flagged for remediation. Endpoints without ASP.NET Core installed exit as not applicable.

2. Remediation phase: The Worklet runs the uploaded installer files with /quiet /norestart flags. For 64-bit systems with outdated x64 runtimes, it executes the x64 installer. For outdated x86 runtimes (on either 32-bit or 64-bit systems), it executes the x86 installer. Installation logs are written to the Windows TEMP directory for troubleshooting.

ASP.NET Core upgrade requirements

• Windows 7 or later, or Windows Server

• PowerShell 2.0 or later

• ASP.NET Core runtime already installed (Worklet only upgrades existing installations)

• Upload both x86 and x64 installer EXEs to the Automox console

• Configure $fVersion variable with target version (e.g., '3.1.14')

• Configure $x64Fname and $x86Fname variables with installer filenames

Expected state after ASP.NET Core upgrade

After successful remediation, endpoints run the target ASP.NET Core runtime version. Applications depending on the runtime continue to function with access to security patches and improvements included in the new version. The Worklet creates installation logs at %WINDIR%\TEMP\{installer-name}.log for verification and troubleshooting. You can verify this change through the Automox Activity Log or by checking the endpoint configuration directly.

If installation fails, the log file contains detailed error information. Common issues include insufficient disk space, missing dependencies, or file-in-use conflicts with running applications. Review the log to identify the specific failure reason before retrying.

How to validate update asp.net core changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for update asp.net core.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Test-Path, Get-ChildItem, Write-Output.

4. Validate remediation effects from script operations such as Test-Path, Split-Path, Start-Process, then rerun evaluation for compliance.