The Windows Insider team is starting the week off right today with a new 19H1 build for Fast Ring Insiders, as well as a new Insider build of the Windows Server VNext Semi-Annual Channel release. Indeed, Windows Server vNext preview Build 18346 is now available to download for Windows Server Insiders, bringing improvements to the Server Core App Compatibility feature on demand (FOD) that was introduced in in Windows Server 2019 and Windows Server, version 1809.
Microsoft previously added a Task Scheduler (Taskschd.msc) feature for for App Compatibility FOD in the previous Windows Server vNext Insider build 18334, and the new bits today add a Hyper-V Manager (Virtmgmt.msc) feature for creating and connecting to virtual machines hosted on Server Core and the App Compatibility FOD. This new Windows Server build also comes with the following bug fixes:
- (New) Error after remoting to machine with RDP post FOD installation. The error message indicates immediately that the remote session has ended with potential reasons, followed by a black RDP screen. This only impacts remoting to a physical machine with Server Core + FOD.
- (New) Applies to App Compat FOD MMC.exe only: Multiple Active Directory Users and Computers snap-ins added to the same MMC.exe instance could show inconsistent or no data on part of the snap-ins after adding extra columns to the UI view. Wokaround: for UI user management, use a separate MMC for each ADUC (DSA.MSC) snap-in.
- A local user’s last logon time output from “net user username” may not be recorded even when the user has accessed the server’s network share.
- Scheduled startup tasks may fail to run. An event is logged, ID 101 with the error code ERROR_LOGON_FAILURE when the failure occurs.
- A virtual machine may not report all virtual fibre channel (vfc) LUNs after powering on if there are 2000+ vfc LUNs. WMI queries from the host show the LUNS available. Restarting the VMMs may show the LUNS again as available.
- DCPromo fails if the interface metric of the physical NIC is larger than Loopback Interface.
- Third-party password filter dlls may not be notified when the local Administrator account’s password was changed.
- [New] Attempting system image recovery from an image located on a network share may result in error “A specified logon session does not exist. It may already have been terminated”
- Server FODs are not retained after in-place (or B2B) upgrade.
- Domain Controller rename updates incorrect attributes in AD leaving orphaned data behind (ValidateSPNsAndDNSHostNameActual). This can be reproduced by adding a new FQDN, setting it as primary, restarting the domain controller, then removing the current FQDN. Checking the msDS-AdditionalDnsHostName, msDS-AdditionalSamAccountName and servicePrincipalName attributes will incorrect values.
- Invalid file may be created in %Systemroot%\System32\LogFiles\Sum by User Access Logging.
- Self-service users cannot install Feature on Demand (FOD) packages and Language Packs for Windows Server Update Service (WSUS), System Center Configuration Manager (SCCM), and Autopilot scenarios.
- A container host may become unresponsive due to a deadlock when attempting to mount a volume. On an affected system, Docker hangs on all commands.
- When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.
As usual, registered Windows Server Insiders can download this new build from the Windows Insider Preview Downloads page. If you have yet to sign up for testing new Windows Server builds, you can do so on the Windows Insiders for Business portal.Further reading: Microsoft, Windows Insider, Windows Server