Microsoft Quickly Spins Up Another Near-Final Windows 10 Insider Preview Build

Microsoft Quickly Spins Up Another Near-Final Windows 10 Insider Preview Build

Just two days after its previous Windows 10 Insider Preview release, Microsoft has queued up build 16294 for testers. Yep. The Windows 10 Fall Creators Update is almost complete.

“We are rolling out Windows 10 Insider Preview Build 16294 for PC to Windows Insiders in the Fast ring only (not Skip Ahead),” Microsoft’s Dona Sarkar noted. “This build might not be available for everyone as it rolls out so just be patient.”

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Windows Insiders are known for their patience, so I’m sure that went well.

Anyway, there are no new features, of course. And Microsoft declines to hide the state of Windows 10 by not providing a known issues list to the public. But the firm did fix the following problems in this build, two of which were very widespread:

  • This build has the fix for the bug that was causing some Surface Pro 3 devices to end up in a “unbootable” [not sure why this is in quotes, as those PCs were, in fact unbootable. –Paul] state where the Windows OS will not load and it appears to be stuck on a “spinning dots” screen. After installing this build, Surface Pro 3 devices should no longer get into this state. If you do have a Surface Pro 3 in a bad state, you can follow the instructions on this forum post to get back up and running.
  • This build fixes an issue resulting in some Insiders seeing error 0x800B010C when attempting to upgrade to the last few builds. I experienced this problem on my Surface Pro 4 for the last two builds, actually.
  • This build fixes an issue on Dutch builds where explorer could go into a crash loop if an app-requested downloads notification popped up from OneDrive.
  • This build fixes an issue where expand.exe couldn’t expand CABs that contained Japanese characters in the file name.
  • This build fixes a rare condition that could result in window content being transparent (but showing the window frame) or stale after unlocking your desktop.


Share post

Please check our Community Guidelines before commenting

Conversation 9 comments

  • UK User

    Premium Member
    21 September, 2017 - 9:14 am

    <p>For me it doesn't really matter anymore as each 'update' breaks something on my i7 core desktop, i3 laptop, and my Windows phone, feedback I don't bother with anymore as my request for Microsoft to take a look at something just comes back with the stupid 'we've got it' or something and nothing is doneby . I now resort to using my still functioning XP desktop with Microsoft software as it was back then, which was just what I needed without all the extra layers added since for which I have no use, oh and by the way the XP is not connected to the Internet in any way.</p><p><br></p><p>At the moment Edge on my desktop doesn't work at all just a blank page when launched, the calendar apps do not let you see multiple entries for a given day as they are obscured by an hourly overlay which you cannot remove, then on my phone the photos app refuses to launch, and as for searching on the Microsoft forums, forget it, people who seem to have similar problems get unfathomable answers but are still left with their problem. All in all I have tired of trying to correct faults after updates and with the apparent ease with which hackers can make a mockery of so called 'security enhancements' by most software vendors.</p><p><br></p><p>I can resort to my XP machine, a Pentium machine, and use the none bloated versions of Office and One Note, still play music but without Groove, Windows media software functions as it should for a multitude of things. And that's another sadness, Microsoft had perfectly good software programs that they threw to one side and introduced something in its place that are appalling, change to Apple or Android? I can't afford to as I'm tied up in the Microsoft eco system but I am just one of millions tossed aside in the name of progress. I long ago realised that I, as a private consumer, am regarded as a pain in the butt by the management of Microsoft, as I now realise that my 2 Lumia phones will join a lot else on the Microsoft scrapheap.</p><p><br></p>

    • Tallin

      22 September, 2017 - 2:55 pm

      <blockquote><a href="#178430"><em>In reply to UK User:</em></a></blockquote><p>Sorry, if you're running an insider build of Windows 10, you need to expect bugs. You absolutely should not run it on a production machine. If you are running a production build of Windows (or even if not), it may be time to do a reset. I have seven machines at home running the latest Windows 10 with no issues like this. Got two i7s, a first gen i3, even a Core 2 Duo. Also, a few AMD machines of various ages. All working great, no problem. </p>

  • JerryH

    Premium Member
    21 September, 2017 - 10:21 am

    <p>The issue with the window content being transparent isn't as rare as that seems to indicate. At work I have 4 team members and I all running these builds and for the last 4 or 5 builds many Outlook (yes, at work) windows such as reminders come up transparent. All of us get this. Glad it is supposedly fixed.</p>

    • Bart

      Premium Member
      21 September, 2017 - 11:49 am

      <blockquote><a href="#178445"><em>In reply to JerryH:</em></a></blockquote><p>You run these on your work machines???? </p>

      • JerryH

        Premium Member
        21 September, 2017 - 12:08 pm

        <blockquote><a href="#178460"><em>In reply to Bart:</em></a></blockquote><p><br></p><p>I am in the group that does the central design and build of our Windows image. I have 6 machines – but yes, I run them on my main production machine. If you don't do that, you don't find all the bugs that relate to your scenarios. For example, we are one of those rare companies that use Smart Cards. We have several other nearly unique scenarios as well. We file A LOT of bugs on Windows 10 builds! But you just don't catch them if you don't do it on your main machine. That said, if something goes terribly wrong I can use another machine or just use Remote Desktop to a different machine.</p>

  • Mestiphal

    21 September, 2017 - 1:35 pm

    <p>The last creator's update finally came down to my daughter's Stream 7 tablets not long ago, wonder how long I'll have to wait to see this one on the update list</p>

  • NW Surface User

    22 September, 2017 - 4:37 pm

    <p>New (disabling) Surface Pro 3 problems – I own a Surface Pro 3 and build <span style="color: rgb(0, 0, 0);">16294 will AGAIN make your machine unusable (different problems but they are show-stoppers) unless you apply the same (forum instructions) fix referred to above. I tried updating from 16291 to 16294 and my Surface was again unusable until I applied the fix. Now build 16294 runs fine and I posted this information to their forum. Clearly they have much more work to do before they are done tuning this update for release. </span></p>

  • kalin27

    11 July, 2018 - 3:54 am

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC