Windows 10 Build 17107 Released to Insiders in the Fast ring

Microsoft today released Windows 10 Insider Preview Build 17107 (RS4) to Windows Insiders in the Fast ring. There won’t be a new build this week for Windows Insiders who opted into Skip Ahead. Let's see what are the key changes.

Windows 10 Build 17107

This build comes with one new change made to Windows Update delivery, however, there are tons of fixes and small improvements. Here is the change log.

Windows Update Improvements

Keeping PCs Up-to-date: In an effort to prevent PCs from becoming out of date, we are introducing a change in behavior to Windows Update that is designed to be more proactive at keeping PCs updated. In RS4, now when Windows Update scans, downloads, and installs on a PC with AC power – it will prevent the PC from going to sleep when it is not in active use, for up to 2 hours when receiving an update in order to give Windows Update more opportunity to succeed. If you are not seeing this new behavior, let us know by sending in feedback via Feedback Hub.

General changes, improvements, and fixes for PC

  • We fixed an issue where Settings would crash when you tried to open Themes.
  • We fixed an issue where the Settings tile didn’t have a name if you pinned it to Start.
  • We’ve updated About Settings to include at a glance entries for the two new Windows Defender pillars (Account Protection and Device Security).
  • We fixed a typo in Storage Sense Settings.
  • We fixed an issue resulting in all dropdowns in Settings appearing blank until clicked.
  • We fixed an issue that could result in Settings crashing after having navigated to and left Sound Settings.
  • We fixed an issue where closing certain apps after using in-app search could result in them hanging on the splash screen the next time they were launched.
  • We fixed an issue where plugging in an external optical drive (DVD) will cause an Explorer.exe crash.
  • We fixed an issue resulting in the hamburger button in Windows Defender overlapping the home button.
  • We fixed an issue where certain games using Easy Anti Cheat could result in the system experiencing a bugcheck (KMODE_EXCEPTION_NOT_HANDLED).
  • We fixed an issue where we had observed seeing longer-than-normal delays during install at the 88% mark. Some delays were as long as 90 minutes before moving forward.
  • We fixed an issue resulting in the Windows Defender offline scan not working in recent builds.
  • Some Insiders may have noticed a new message when holding down the power button which says “Please release the power button. We just need a few more seconds to shut down”. This is an Insider-only feature that gathers additional diagnostic data for situations where holding down the power button was used to recover an unresponsive or nonfunctional system.  It is important to note that holding down the power button is not the appropriate way to shutdown/reboot a system that is functioning properly. See this support page for additional information on how to properly shutdown your PC.

Known issues

  • Buttons on Game bar are not centered correctly.
  • Selecting a notification after taking a screenshot or game clip opens the Xbox app’s home screen instead of opening the screenshot or game clip.
  • Post-install at the first user-prompted reboot or shutdown, a small number of devices have experienced a scenario wherein the OS fails to load properly and may enter a reboot loop state. For affected PCs, turning off fast boot may bypass the issue. If not, it is necessary to create a bootable ISO on a USB drive, boot into recovery mode, and this this will allow bypass.
  • Tearing a PDF tab in Microsoft Edge will result in a bugcheck (GSOD).

If you are Windows Insider in the Fast ring, you'll get this build automatically via the Windows Update service.

13 thoughts on “Windows 10 Build 17107 Released to Insiders in the Fast ring

  1. Brennan Torres

    Does anybody know the update name for Redstone 4? Also one known issue I have is “An app default was reset” since I used Fall Creators Update. Does anybody have this issue when your app default keeps resetting? I think this is a known issue I should report in the Feedback Hub app.

    Reply
  2. Shyam Reddy

    Thanks Sergey! On this build, looks stable to me. 17101 had many issues.

    Reply
    1. Sergey Tkachenko Post author

      Yeah, the OS is coming to its final version.

      Reply
  3. boink182

    Winaero Tweaker is not working for me on this build. Is this to be expected, or a problem on my end? It was working on previous Insider builds.

    Reply
    1. Sergey Tkachenko Post author

      I have not tested the app in this build yet.
      Which exactly issues you are running into?

      Reply
      1. boink182

        Unhandled exception in .NET on launch. If ignored, trying to do just about anything in the app will lead to the same result, and no changes are applied.

        Reply
        1. Sergey Tkachenko Post author

          Could you please share the error message text?

          Reply
          1. boink182

            See the end of this message for details on invoking
            just-in-time (JIT) debugging instead of this dialog box.
            Show/Hide

          2. Sergey Tkachenko Post author

            Thank you very much for this report.
            It is a bug in the app, definitely.
            I will fix it asap!

          3. boink182

            I tried to post it, but I’m not sure if it went through? Trying to post it again the site tells me I already said that, so I’m assuming it’s available for mods to see.

            In any case, feel free to email me if you need anything else, and thanks for your work on Winaero Tweaker. Windows 10 is hardly usable for me without it, and many of your other offerings ;)

          4. boink182

            I have a little more info regarding this error: I just updated to build 17110 and initially Winaero Tweaker seemed to be working again. I realized this was on a different user account than the one I was seeing the error on initially. Sure enough I was still seeing the error on that user. The problem user has a zero as the first character in the username. I set up another user with a leading zero and got the same error, but other users seem to be working. This was never a problem for me before recent Insider builds.

            I hope this helps.

          5. Sergey Tkachenko Post author

            Thank you mate. I will try to reproduce this issue. I have some ideas why it can be so.

Leave a Reply

Your email address will not be published. Required fields are marked *