A new build of the Windows Server vNext LTSC has been released with build 17738. Make sure to check the known issues before installing. Also, I believe the old adage “everything can be production if you’re brave enough” doesn’t apply to these builds!
[NEW] Notepad may crash or display an empty pane when a user selects File > Open.
[NEW] Authentication that uses Public Key Cryptography User-to-User (PKU2U) to access an SMB volume can result in an error, STATUS_LOGON_FAILURE, due to an invalid private key in the certificate for a cluster-created user account (CSUSR) on each cluster node. This issue can cause cross-cluster migration in cluster sets to fail, as well as possibly cause global namespace mappings to fail, leading to virtual machines being unable to access storage.
[NEW] The Base Filtering Engine service may consume an inordinate amount of memory after starting and stopping thousands of containers.
[NEW] The operating system has an unnecessary utility account for Windows Defender Application Guard.
The Virtual Hard Disk Miniport Driver (Vhdmp.sys) may experience a bug check, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e).
When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.
On a preview build of the operating system, Narrator is not available by default after installation. On an affected system, the audio service is disabled by default.
On recent preview builds, database applications might not be able to initialize a database and fail with a stack overflow or insufficient privileges when the database is located on an SMB volume.
Shielded VMs running Linux do not boot. The loader (LSVMLoad) waits for a passphrase for the boot partition.
Creating or modifying environment variables by using setx fails on a system running in a Nano Container (that is, Nano Server as a container image). On an affected system, setx requires a specific path in the registry, HKCU\Environment\, to exist by default. You can work around this issue by changing where the variable is stored in the registry, or you can add the expected registry path before executing setx commands. To specify that the variable be set for system-wide use in HKLM rather than in HKCU, the default, add the /M switch to a setx command. To instead add the expected registry path, run reg add HKCU\Environment before executing setx commands.
Another build from the Insider team for Fast ring Insiders. This time, they are preparing for the release of the Fall Creators Update, version 1709.
General changes, improvements, and fixes for Mobile
This build includes all the improvements from KB4038788.
In preparation for the release of the Windows 10 Fall Creators Update, the product version number has been updated to 1709 just like PC.
We fixed an issue where, on powering the screen off/on, high demand for CPU could cause several apps to crash. Background processing of photos is an example of high CPU demand. In a photo shoot session, you may have seen the Camera app crash.
We fixed an issue with the Messaging app where conversation text was displayed incorrectly. Thanks to our Insiders that quickly highlighted this issue.
The Insiders team has released build 17751 to the fast ring today. Some sites have said that this is the final build, but as Brandon LeBlanc has said via Twitter and this blog post :
The build watermark at the lower right-hand corner of the desktop is no longer present in this build. This does not mean this is the final build as we are not done yet. We’re just now beginning the phase of checking in final code to prepare for the final release.
So, we are getting close to the final release to consumer for this latest update, but this build it not quite there yet. As usual, it’s ready when it’s ready. So, what’s the official name of this update? Creators Update, Spring Update, etc.? Just called “Windows 10 October 2018 Update”. Simple and sweet.
Just a few small known issues this build. Make sure they won’t affect you too much before you update!
When you use the Ease of Access Make Text bigger setting, you might see text clipping issues, or find that text is not increasing in size everywhere.
Narrator sometimes does not read in the Settings app when you navigate using Tab and arrow keys. Try switching to Narrator Scan mode temporarily. And when you turn Scan mode off again, Narrator will now read when you navigate using Tab and arrows key. Alternatively, you can restart Narrator to work around this issue.
Clicking on web links in PWAs such as Twitter doesn’t open the browser in this build. We’re working on a fix.