This new build release doesn’t bring any major features to the table, just a few minor improvements. Microsoft Edge can now save and automatically fill your preferred information in addresses and related forms and lets you adjust text spacing when you’re in Reading View. In other words, Edge can now replace dedicated form filler software. Windows Shell now allows you to access advanced UWP app options from Start. Microsoft also improved emoji design and added an interesting feature that predicts what emoji you want to insert based on what you type.

As always, build 17046 also fixed a bevy of bugs that annoyed many Insiders. The most important fixes include:

Microsoft fixed the issue where certain third party antiviruses and OneDrive Files on Demand enabled triggered the error “OneDrive cannot connect to Windows”. Build 17046 fixed the issue that could result in delays during logoff and shutdown when a UWP app was open and in suspended state. Fixed an issue resulting in the mouse noticeably flickering.

Speaking of mouse bugs, these troubleshooting guides will help you the most common mouse issues on Windows PCs:

How to fix mouse lags in Windows 10 (and make it fast again) How to fix mouse jumps on Windows 10 How to fix mouse movement issues on your Windows PC

Windows 10 build 17046 issues

As expected, Windows 10 build 17046 also brings issues of its own. The list of known issues is quite long this time and includes the following bugs:

 Broken functionality in Mail, Cortana, Narrator Some features, like Windows Media Player, are missing> Popular Tencent games like League of Legends and NBA2k Online may cause 64-bit PCs to bugcheck (GSOD). We do have a dedicated troubleshooting guide on how to fix Green Screen of Death issues. Check it out and tell us if it helped you fix the problem. VPNs which use custom pop-up windows during connection attempts may fail to connect with error 720. You may not receive all of your notifications from Cortana.<!–li>

  • 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. You may lose certain dictionary files, and you may not be able to input Japanese or Traditional Chinese via IME, Touch Keyboard, or Handwriting on non-Japanese or non-Traditional Chinese language-based OS (like an English-based OS).<!–li>The good news is that you can fix this issue by using the following workaround: Go to Start > Settings > Time & Language > Region & language.
    •  Under Language, select your language Click [Option] and if the [Download] button is available for “Basic typing” under the Language options, please click it to start the download process.<!–li> You can check the status of feature in Settings > Apps > Apps & features > Manage optional features”. If the feature is available, the name will be “Japanese typing”or “Chinese typing”. On the other hand, Insiders also encountered a series of bugs that Microsoft didn’t list on the official build release notes. Windows 10 build 17046 reported bugs
      Build 17046 won’t install</stron

      Many Insiders are still struggling to install the latest Windows 10 build on their devices. The install process suddenly stops and Windows returns to desktop or restores the previous OS version.

      Windows 10 build 17046 reported bugs

        SPONSORED “Yesterday the new build 17046 was released and so I went through the exercise of trying to install it. […] It goes through phase 1 to 100% in a slightly faster time, it seems to me, and then reboots and does phase 2 to 30% and that takes about 15 seconds, much faster than it used to, then reboots and the next phase is so fast I cannot read what it says. Then it reboots and says it is restoring back to previous operating system.”m> Other users could install the build due to error 0xc1900101. If you experienced this error, here is a troubleshooting guide on how to fix it.

        Windows 10pan> won’t shut down correctlyg>i>

        Some users also reported that Windows 10 fails to shut down correctly after installing build 17046. The error ‘Windows was not properly shutdown’ is visible on the log. “17046 downloaded and installed flawlessly. All was well until I restarted the computer in the normal manner. It restarted in the totally familiar and expected way. What I didn’t see until later checking the reliability history was that it was recorded as a Critical error, “Windows was not properly shutdown”, aka a dirty shutdown. To make sure, I restarted again. Sure enough, the same exact scenario, “Windows was not properly shut down”. We all know that there were shutdown issues with the last two builds doing this for normal shutdowns, but now restarts too?”

          Slow boot up

          If Windows 10 starts slower than on the previous build, you’re not alone. Other Insiders noticed this issue as well. “I have a little problem. When starting the Welcome after log-on is slower than 17040 by a lot. On one laptop the titles on the Start screen were replaced with the generic titles not my titles. All of the others came up fine” If you installed Windows 10 build 17046 on your computer, use the comment section below to tell us more about your experience.

          Name * Email * Commenting as . Not you? Save information for future comments
          Comment

          Δ