Jump to content

Check us out:

Photo
- - - - -

Here's what's fixed, improved, and still broken in Windows 10 build 18277

windows

  • Please log in to reply
No replies to this topic

#1
Falkes

Falkes
  • Tb:30445
  • Discord:Falkes#6861
  • Gender:Male
  • Location:Paris/France
  • Server:Bunker #4
Click to view battle stats

gallery_328_43_3780.jpg

Microsoft today released Windows 10 build 18277 to Insiders in the Fast ring. The build is from the 19H1 development branch, meaning it is a preview build for the next major update to Windows 10 that is expected to be rolled out sometime next year. As the development of 19H1 catches pace, major features will begin showing up in these builds.

However, today’s build contains a bunch of new features that include improved Focus Assist, Action Center improvements with the inclusion of a brightness slider, high DPI improvements and more. As usual, there is a long list of fixes and known issues that you have to be aware of that accompany the new features.

Here is the list of what’s fixed in build 18277:

We fixed the issue causing WSL to not work in Build 18272. Thanks for your patience.
We fixed an issue resulting in text not rendering on the screen if you had a large number of OTF fonts, or had OTF fonts that support the extended East Asian character set.
We fixed a recent issue where Task View failed to show the + button under New Desktop after creating 2 Virtual Desktops.
We fixed an issue resulting in Timeline crashing explorer.exe if you pressed ALT+F4 while it was visible.
We fixed an issue significantly impacting Start menu reliability in recent builds when pinning, unpinning, or uninstalling apps.
We fixed an issue where the expected context menu wouldn’t appear after right-clicking on a folder in File Explorer from a network location.
Some Insiders may notice small differences in File Explorer over the coming flights – we’ll have more to share later about this later.
We fixed an issue resulting in the home page of Settings having no visible scrollbar in recent flights if the window was small enough to need one.
We’re updating the icon used to identify the Region page in Settings.
We fixed an issue resulting in Settings crashing sometimes in recent flights when going to Sign-in Settings.
We fixed an issue where Settings would crash if you were typing in the search box with the embedded handwriting panel and went to switch languages within the panel.
We fixed an issue where playing videos might unexpectedly show a few frames in the wrong orientation when maximizing the window after changing the orientation of your screen.
We fixed an issue impacting Emoji Panel reliability in recent flights.
The touch keyboard’s feature to input a period after two quick taps on the spacebar was recently also accidentally enabled when typing with the hardware keyboard and has now been disabled.
We’ve made some adjustments to improve the performance of WIN+Shift+S bringing up snipping.
Some Insiders may notice changes to our snipping experiences, as we explore ideas for the future – we’ll have more details to share later.
We fixed an issue that caused Far Manager to have a significant pause during a long running command like ‘dir’ (see Microsoft/console#279).
We fixed an issue that caused Windows applications running from WSL through interop and applications using the *PseudoConsole APIs to redraw the top left corner excessively (see Microsoft/console#235).
We fixed an issue resulting in running “start .” from Command Prompt failing in the previous flight with an access denied error.
We fixed an issue resulting in some Insiders experiencing bug checks (green screens) with the error KMODE_EXCEPTION_NOT_HANDLED on the previous flight.
We fixed an issue where certain devices might hit a bug check (GSOD) when shutting down or when switching from a Microsoft account to a local admin account.
We fixed an issue resulting in wuaueng.dll repeatedly crashing in the background for some Insiders in the last few flights.

Here are the known issues from today’s release:

Some users will notice the update status cycling between Getting Things Ready, Downloading, and Installing. This is often accompanied with error 0x8024200d caused by a failed express package download.
PDFs opened in Microsoft Edge may not display correctly (small, instead of using the entire space).
We’re investigating a race condition resulting in blue screens if your PC is set up to dual boot. If you’re impacted the workaround is to disable dual boot for now, we’ll let you know when the fix flights.
The hyperlink colors need to be refined in Dark Mode in Sticky Notes if the Insights are enabled.
Settings page will crash after changing the account password or PIN, we recommend using the CTRL + ALT + DEL method to change the password
Due to a merge conflict, the settings for enabling/disabling Dynamic Lock are missing from Sign-in Settings. We’re working on a fix, appreciate your patience.

Additionally, there is one known issue for developers:

If you install any of the recent builds from the Fast ring and switch to the Slow ring – optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.

It is advised that you go through the list of known issues if you intend to install the preview build, as they include update status issues and blue screens on PCs that are set up to dual boot. There may be risks involved in installed preview software, especially if you’re running them on your daily driver.

However, if you aren’t enrolled in the Fast ring on the Windows Insider Program yet, you can do so by heading into Settings > Windows Insider Program > Clicking on “Get Started” and enrolling into the Fast ring.







Also tagged with one or more of these keywords: windows