Home Windows 10 News Windows 10 Builds Fixes & Known Issues in Windows 10 Build 17063

Fixes & Known Issues in Windows 10 Build 17063

0

Microsoft pushed Windows 10 Build 17063 (Version 1803) to insiders in the Fast ring and Skip Ahead and you can read all the changes in detail that this build brings by clicking here. The Build brings many fixes too for the issues faced by insiders on the previous insider build. You can check the full list of fixes below.

Windows 10 Build 17063 Fixes:

  • We fixed an issue where all types of dynamic volumes listed here wouldn’t mount properly or be accessible from Windows (the data remained intact but inaccessible on the volume on impacted builds).
  • We fixed an issue where after opening and closing the People flyout notification toasts might stop appearing until the computer had been rebooted.
  • We fixed an issue where Cortana’s notification settings were unexpectedly missing in Settings after upgrading to recent builds.
  • We fixed an issue where when there was a problem with Cortana’s speech resources not being available, she could end up blocking Start.
  • We fixed an issue resulting in potentially not receiving all of your notifications from Cortana in the last first flights. We fixed an issue where when using Windows in Hebrew no search results were shown in Search until a space was entered.
  • We fixed an issue such that Recycle Bin will now show up in the search results when typing in Cortana. This was a server-side change so you will see it outside the bounds of this flight.
  • We fixed an issue where opening the Action Center while there was a notification toast visible could result in the Action Center unexpectedly animating in from the bottom corner rather than the side.
  • We fixed an issue where if you reinstalled or reset your PC without internet in the last few flights the default tiles in Start could get stuck as downward arrows.
  • We fixed an issue where if the system was low on memory context menus might display in a narrow width missing all text.
  • We fixed an issue with the File Picker dialog from recent builds where saving file names that included an additional period in the name (like A.ver2.exe) would result in the file extension not being included with the saved file (A.ver2).
  • We fixed an issue where certain videos when watching in Microsoft Edge would stop playing and become unresponsive upon altering play speed to 4x or 8x.
  • We fixed an issue resulting the expected tooltip not appearing when hovering the mouse over images on certain sites in Microsoft Edge.
  • We fixed an issue where no search suggestions were displayed while typing in the Microsoft Edge address bar if the PC was set to a region not currently supported by Cortana.
  • We fixed an issue that could result in an error message saying “device does not respond” when attempting to use Near Share.
  • We fixed an issue where nearby devices that had near share enabled might not be listed in Share.
  • We fixed an issue resulting in cursor lags on some devices when night light was transitioning.
  • We fixed an issue resulting in some Insiders finding that Outlook 2016 crashed frequently on the previous flight.
  • We fixed an issue where the group policy to set a custom lock screen image wouldn’t work if you had also set a policy that disabled the image on the login screen.
  • We fixed an issue resulting in docker not working in the last few flights.
  • We fixed an issue from recently flights where the Emoji Panel’s most frequently used page wasn’t updating.
  • We fixed an issue where the touch keyboard showed a very small size on large monitors.
  • We’ve updated the touch keyboard to now have an animation when invoking and dismissing.
  • We fixed an issue where keys on the full touch keyboard might become stuck in a visually pressed state.
  • We fixed an issue where the Chinese (Simplified) Pinyin IME might hang when typing quickly into Cortana.
  • We fixed the issue where VPNs that used custom pop-up windows during connection were failing with error 720 when attempting to connect.
  • We fixed the issue causing users that have enabled the legacy console to be unable to launch any command line application.

Windows 10 Build 17063 also comes with some known issues that you may like to read before installing this build.

Windows 10 Build 17063 Known issues:

  • Popular Tencent games like League of Legends and NBA2k Online may cause 64-bit PCs to bugcheck (GSOD).
  • [DEVELOPERS] Deploying an x86 app to a x64 PC remotely result in “FileNotFound” deployment failures if the target PC is running Build 17040. Deploying an x64 app to a x64 PC remotely or a x86 app to a x86 PC will work fine.
  • Microsoft Edge may not receive Push Notifications from websites in this flight, due to an issue saving permissions on a per-site basis. We expect this issue to be resolved in the next preview build.
  • Launching an immersive 360 degree video from the Movies and TV app within Windows Mixed Reality will result in the video facing the wrong way. Subsequent launches of 360 degree videos will work correctly.
  • When users try to create a Microsoft Edge InPrivate window from inside a Mixed Reality headset, a regular window will get created instead. Users won’t be able to use InPrivate inside Mixed Reality in this build. InPrivate on desktop is not affected.
  • We’re preparing for the inclusion of OpenSSH Server as a deployment mechanism in Developer Mode. However the UI code got checked in ahead of the components, and so while there is a “Use OpenSSH (Beta) for remote deployment” switch in the UI under Settings, it won’t work, and turning it on will break remote deployment to that device until the switch is turned off.
  • If you’re using any EUDC fonts Microsoft Edge, Cortana, and other apps that use a webview won’t launch. You can resolve this issue by deleting the HKCU\EUDC key in Registry Editor. Note, if you do this, you won’t be able to see EUDC characters. We recommend you export this regkey before deleting it, so it’s easy to reapply the key in a future flight once the issue has been fixed.
  • After upgrading to this build you may find touch and pen to not work on the non-primary display. Related to this, mouse, touch, and pen input might not happen in the right place after an orientation change or if you’re using a non-native aspect ratio. We’re working on a fix.

 

Exit mobile version