Microsoft Releases Windows 10 Build 20236
Microsoft today is releasing Windows 10 build 20236 to Insiders in the Dev Channel. This build follows up last week’s build 20231. The one key feature of today’s release is that it allows you to change the refresh rate of your display.
Windows 10 Build 20236
Starting with today’s build you can go to Settings > System > Display > Advanced display settings and change the refresh rate of your selected display.
Here is the list of changes and improvements for this new build:
- To improve accessibility of PDFs for Narrator and other screen reader users, in the cases where Unicode is not provided by the printing application, we’re updating our Microsoft Print to PDF option to make an attempt to convert the provided font glyphs to Unicode.
And here is the list of new fixes to expect:
- We’ve fixed an issue where after taking recent builds some Insiders received an unexpected Compatibility Assistant notification that “Microsoft Office is no longer available”.
- We’ve fixed an issue where some Office applications were crashing or missing after updating to a new build.
- We fixed an issue that could result in the same app update installing repeatedly on the previous build.
- We’ve fixed an issue where some devices are experiencing a DPC_WATCHDOG_VIOLATION bugcheck
- We fixed an issue resulting in some Insiders experiencing an UNHANDLED_EXCEPTION in dxgkrnl.sys bugcheck in the last few builds.
- We fixed an issue that could result in a 0x800F0247 error when installing driver updates.
- \We fixed an issue that could result in sihost.exe crashing when trying to share an app via the Share option when right clicking a tile in Start.
- We fixed an issue where if “Animate controls and elements inside windows” was turned off in Performance Options, dragging a tile to another tile group in Start would result in the dragged tile no longer responding to mouse click.
- We fixed an issue resulting in Narrator sometimes reading out an incorrect number of nodes in File Explorer’s navigation pane (for example, saying 1 of 2 items, instead of 1 of 4 items).
- \We fixed an issue that could result in the icon next to “Scan with Microsoft Defender” (when right clicking a file in File Explorer) being very small or large.
- We fixed an issue where the icon next to “Scan with Microsoft Defender” when right clicking a file wasn’t updating to reflect high contrast when high contrast was enabled.
- We fixed an issue that could result in File Explorer crashing when renaming a file.
- We fixed an issue from recent builds resulting in clicking on items in Timeline not launching the corresponding app.
- We fixed an issue from recent builds impacting certain apps with search boxes, where the search box would disappear when scrolling the app even if it was supposed to stay visible.
- We fixed an issue resulting in intermittent connectivity loss when connecting to a PC via remote desktop connection, as a result of the connected PC attempting to sleep.
- We fixed an issue where when using the windns.h API to discover services on the local network, the TTL value of the discovered service wasn’t used – instead using the default value of 120 seconds.
- ]We fixed an issue where the “Listen to this device” checkbox state in microphone properties wasn’t persisted on upgrade and would revert to default.
- We fixed an issue where adjusting volume also muted/unmuted when “App volume and device preferences” was open.
- We fixed an issue that could result in the Network & Internet Settings Status page sometimes unexpectedly not showing all current connections.
- We fixed an issue that could result in your cursor disappearing when typing into Command Prompt with a Chinese IME active.
- We fixed an issue that could result in the touch keyboard sometimes not making any sounds while typing even though the setting to have sound while typing was enabled.
- We fixed an issue where the French AZERTY touch keyboard layout was French keyboard is missing number hint labels on the A/Z keys, and the Select All/Undo labels were at the top instead of bottom.
- We fixed an issue where the child keys on the Japanese 12-key touch keyboard layout weren’t following the updated key design.
- We fixed an issue where Narrator was unexpectedly saying “Expressive Input Panel” when you touched a text candidate in the touch keyboard.
- We fixed an issue that could result in the touch keyboard getting stuck in a suspended state after waking a PC from sleep, leading to it not invoking automatically when setting focus to a text field.
- We fixed an issue with the updated touch keyboard design where when using Arabic the clipboard icon would appear on the wrong side of the copied text in the candidate bar.
- We fixed an issue with the Thai touch keyboard layout, where the shift-state characters were placed in inconsistent locations on the keys.
- We fixed an issue where when using the updated Emoji Panel design, Narrator wasn’t reading the category names in the Most Recently Used section.
- We fixed an issue with the Emoji Panel when using Narrator, where after inserting an emoji, Narrator would then stay silent on navigating further to other emoji.
- We fixed an issue where it wasn’t possible to use the arrow keys to navigate through the gif section of the Emoji Panel.
- We fixed some contrast issues in the updated Emoji Panel and touch keyboard expressive input area when using high contrast.
- We fixed an issue that could result in the Voice Typing settings menu drawing off screen.
- We fixed a regression that was breaking NVIDIA CUDA vGPU acceleration in the Windows Subsystem for Linux. Please see this GitHub thread for full details.
Keep in mind that Insider builds are meant for coders, IT admins, and Windows 10 enthusiasts who want to test new features and submit feedback to Microsoft.
These builds are not meant for inexperienced users. They are also not meant to run on your primary production machine. Insider builds contain many known stability issues that can cause your system to become unstable or even crash.
For more on this build’s full list of changes, known issues, and workarounds make sure to read Microsoft’s full blog post.