Windows-Containers License Activation error in windows container

We are using windows 2022 image from Microsoft registry and running it as windows container. As soon as we start it as container, we see error for license activation inside container event logs.

image we are using : mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2022 Activate license Error we are getting in container:

{"Source": "EventLog","LogEntry": {"EventSource": "Microsoft-Windows-Security-SPP","Time": "2025-04-09T14:30:48.000Z","Channel": "Application","Level": "Error","EventId": 8198,"Message": "License Activation (slui.exe) failed with the following error code:\r\nhr=0x8007232B\r\nCommand-line arguments:\r\nRuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=ef6cfc9f-8c5d-44ac-9aad-de6a2ea0ae03;NotificationInterval=1440;Trigger=TimerEvent"}}

Using below in docker file: FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2022 AS runtime

docker version: Client: Version: 27.3.1 API version: 1.47 Go version: go1.22.7 Git commit: ce12230 Built: Fri Sep 20 11:42:27 2024 OS/Arch: windows/amd64 Context: desktop-windows

Server: Docker Desktop 4.35.1 (173168) Engine: Version: 27.3.1 API version: 1.47 (minimum version 1.24) Go version: go1.22.7 Git commit: 41ca978 Built: Fri Sep 20 11:40:58 2024 OS/Arch: windows/amd64 Experimental: false

docker info
Client: Version: 27.3.1 Context: desktop-windows Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.17.1-desktop.1 Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe compose: Docker Compose (Docker Inc.) Version: v2.29.7-desktop.1 Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe debug: Get a shell into any image or container (Docker Inc.) Version: 0.0.37 Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe desktop: Docker Desktop commands (Alpha) (Docker Inc.) Version: v0.0.15 Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe dev: Docker Dev Environments (Docker Inc.) Version: v0.1.2 Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe extension: Manages Docker extensions (Docker Inc.) Version: v0.2.27 Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe feedback: Provide feedback, right in your terminal! (Docker Inc.) Version: v1.0.5 Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe init: Creates Docker-related starter files for your project (Docker Inc.) Version: v1.3.0 Path: C:\Program Files\Docker\cli-plugins\docker-init.exe sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.) Version: 0.6.0 Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe scout: Docker Scout (Docker Inc.) Version: v1.14.0 Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server: Containers: 2 Running: 0 Paused: 0 Stopped: 2 Images: 150 Server Version: 27.3.1 Storage Driver: windowsfilter Windows: Logging Driver: json-file Plugins: Volume: local Network: ics internal l2bridge l2tunnel nat null overlay private transparent Log: awslogs etwlogs fluentd gcplogs gelf json-file local splunk syslog Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 22631 (22621.1.amd64fre.ni_release.220506-1250) Operating System: Microsoft Windows Version 23H2 (OS Build 22631.5039) OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 15.95GiB Name: CZDC36A-1001471 ID: 5e5be910-73d9-461e-80fa-711b84543c44 Docker Root Dir: C:\ProgramData\Docker Debug Mode: false Labels: com.docker.desktop.address=npipe://\.\pipe\docker_cli Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine

Apr 16 '25 13:04 nikunjrc-azcli

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

Apr 16 '25 13:04 github-actions[bot]

Thanks for sharing the details. From what we've observed, it looks like the license activation error is baked into the image itself. We ran a few different versions of the mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2022 image across releases from 2022, 2023, 2024, and 2025. In each, we see the same activation error in the event logs. After running the containers for a few days, we also see that the container tries to activate the license every 24h, which leads to the same error showing up repeatedly.

Just wanted to clarify—are you seeing any functional impact from this error or is it just something you noticed in the logs?