Windows Server 2019 build 17643
Build of Windows Server 2019 | |
OS family | Windows 10 (NT 10.0) |
---|---|
Version number | 10.0 |
Build number | 17643 |
Build revision | 1000 |
Architecture | x64 |
Build lab | rs_prerelease |
Compiled on | 2018-04-05 |
Expiration date | |
Timebomb | 2018-07-02 (+88 days) |
SKUs | |
Standard (Core) Datacenter (Core) | |
About dialog | |
Windows Server 2019 build 17643 is a build of Windows Server 2019. It is only officially released as a Docker image. It was later shared on 6 November 2024. Prior to its leak, this build was found by BetaWorld member WoodEar85 on 19 October 2021.[1] Unlike its client counterpart and previous build, this build was not officially released to Insiders.
New changes and fixes[edit | edit source]
Application Compatibility[edit | edit source]
The Application Compatibility Feature on Demand (FoD) has been introduced for Windows Server Core. It includes a set of binaries from the Desktop Experience, without bringing the user interface of the Desktop Experience.
The following components will be added after installing it:
- Event Viewer (
eventvwr.msc
) - Performance Monitor (
perfmon.exe
) - Resource Monitor (
resmon.exe
) - Device Manager (
devmgmt.msc
) - Microsoft Management Console
mmc.exe
) - PowerShell ISE (
powershell_ise.exe
)
At this stage in development, it has to be installed from a separate disk image with the following command: DISM /Online /Add-Capability /CapabilityName:"Server.Appcompat~~~~0.0.1.0" /Source:X: /LimitAccess
, where X is the drive letter of the drive with the FOD files.
Bug fixes[edit | edit source]
- The drivers for a RAID device and network adapters from specific manufacturers were updated.
Bugs[edit | edit source]
- Active Directory Domain Controllers may not be upgraded correctly by an in-place upgrade unless the NT Directory Service is disabled beforehand.
- Editing or creating policies for AppLocker can cause the MMC snap-in to crash when generating rules for a packaged app.
- After upgrading the OS, the AppX database may end up having corrupted entries, which will cause issues with components that use them.
Gallery[edit | edit source]
Images published before publication[edit | edit source]
Docker Layer image[edit | edit source]
About Registry Editor