Author Topic: Microsoft releases Windows Server Insider Preview build 18334  (Read 120 times)

Offline javajolt

  • Administrator
  • Hero Member
  • *****
  • Posts: 35171
  • Gender: Male
  • I Do Windows
    • windows10newsinfo.com
Microsoft releases Windows Server Insider Preview build 18334
« on: February 13, 2019, 07:59:11 PM »
Microsoft is busy today, having released a number of updates as part of Patch Tuesday, as well as a new Windows 10 SDK Preview build. But that's not all, as there's also a new build of Windows Server Insider Preview, which is also number 18334.

It's been a couple of weeks since the last Windows Server preview build was released, but there's not a whole lot that's new here. The only major addition is in the Server Core App Compatibility Feature on Demand (FOD), which now supports the Task Scheduler.

Aside from that, there are a few bugs that have been fixed with this release, including one that prevented users from doing in-place upgrades. Here's the full list:

Quote
• We fixed an issue where In-place upgrade failed.

• We fixed an issue where a CPU spike may happen when Windows Server logs obsolete Windows Error Reporting reports PnPDriverInstallError and PnPDriverImportError.

• We fixed an issue where Dynamic Update Setup on Server shows “Installing Windows 10” instead of Server.

• We fixed an issue where ADFS Requests with invalid domain suffixes fail after a long delay (around 3 minutes) with error DS_NAME_ERROR_DOMAIN_ONLY. This can cause queued legitimate requests to experience delays or also timeout.

• We fixed an issue where Windows may attempt to reuse an expired DHCP lease if the lease expired while the OS was shut down.
As you'd expect with most preview builds, there are still problems you'll want to be aware of, and the list for this build is fairly long:

• [New] A local user’s last login 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 fiber 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

• 19919812 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 an 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.

You can download Windows Server Insider Preview build 18334 here, as well as the same build of Server Core App Compatibility FOD, which you'll probably need for the only new feature in today's release. There's also a new build of the Windows Server Language Packs. The Windows Admin Center is still on version 1812, so you likely don't need to update it yet.

source