Enhancements to Windows Containers
Everyone, I have created a github issue list for getting Windows Containers on par with linux containers: Here are the issues I documented: Syscall/capability-scoped restriction policy for process-isolated containers (seccomp/capabilities parity) #649 — Syscall/capability-scoped restriction policy for process-isolated containers (seccomp/capabilities parity) True PID namespace isolation for process-isolated containers (server silos) #650 — True PID namespace isolation for process-isolated containers (server silos) CimFS-backed overlay mount performance parity with Linux overlayfs for container image layers #651 — CimFS-backed overlay mount performance parity with Linux overlayfs for container image layers Decouple container base image version from host OS version for process-isolated containers #652 — Decouple container base image version from host OS version for process-isolated containers Please check them out and upvote them. We need to make Windows containers as capable as Linux containers.
nltest /dclist command on some sites
The Active Directory(Domain Controller) configuration is as follows. ~~~ siteA : AD1(FSMO) siteB : AD2 siteC : AD3 PC4 ~~~ Running the "nltest / dclist" command on PC4 gives the following result. === AD1 siteA AD3 siteC AD2 siteB === Considering the site structure of AD, I think that AD of the same site(AD3 siteC) will be output at the beginning, but is my understanding wrong? Or is it output in a random order?
Create a CLI and API like wslc but for Windows containers
The current issue is the dependency on Docker and the docker cli for Windows Containers. We would like a native solution from Microsoft for Windows Containers. This would be similar to wslc, but fully compatible for Windows containers. This could be done by leveraging existing Windows container APIs and the containerd container engine for Windows containers. I have also opened an enhancement feature on github for Windows Containers a month ago but there has been no feedback. https://github.com/microsoft/Windows-Containers/issues/643 Microsoft needs to step up and make Windows/ Windows Server containers on par with linux containers
in-place upgrade fails from b29574 to latest vnext b29595
Hi all, is anyone facing the same issue IPU fails on a fresh b29574 upgrading to latest using WU? provided more information in feedback hub. Thanks for sharing your experience. as a next attempt I will mount ISO and upgrade. mind b29574 was the base bare metal installation so no previous IPUs involved. related feedback https://aka.ms/AA11g03n Tested Upgrade Paths Baseline TargetOS Result 29574 29595 fails 29574 29602 fails 29595 29602 fails Installed roles: - Hyper-V Specialities: tried SysWOW64 removal but failed to do so https://aka.ms/AA11eyy5 OS Drive is ReFS, potientially related https://aka.ms/AA11eyy8 <?xml version="1.0" encoding="utf-16"?> <SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag"> <Version>1.7.0.0</Version> <ProfileName>FindRollbackFailure</ProfileName> <ProfileGuid>3A43C9B5-05B3-4F7C-A955-88F991BB5A48</ProfileGuid> <FailureData>0xc1900101-0x20017 Error: SetupDiag reports rollback failure found.Last Phase = FinalizeLast Operation = Cleanup external drivers after installationError = 0xC1900101-0x20017</FailureData> <FailureData>LogEntry: </FailureData> <FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData> <FailureDetails>RollbackErrorCode = 0xC1900101, ExtendedCode = 0x20017, LastOperation = Cleanup external drivers after installation, LastPhase = Finalize</FailureDetails> <Setup360Result>0xc1900101</Setup360Result> <Setup360Extended>0x20017</Setup360Extended> <SetupPhaseInfo> <PhaseName>Finalize</PhaseName> <PhaseStartTime>06/06/2026 13:16:53</PhaseStartTime> <PhaseEndTime>06/06/2026 13:17:35</PhaseEndTime> <PhaseTimeDelta>0:00:00:42.0000000</PhaseTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupPhaseInfo> <SetupOperationInfo> <OperationName>Cleanup external drivers after installation</OperationName> <OperationStartTime>06/06/2026 13:17:35</OperationStartTime> <OperationEndTime>06/06/2026 13:17:35</OperationEndTime> <OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupOperationInfo> </SetupDiag> also noticing uncommon links in root as if I were using FAT32.
