Windows 10 Build 17074.1002 Comes to the Slow Ring

Posted on January 20, 2018 by Paul Thurrott in Windows 10 with 16 Comments

Windows 10 Build 17074.1002 Comes to the Slow Ring

Windows Insider Preview releases to the Slow ring are few and far between, but this one is particularly notable: Build 17074, which hit the Fast ring just a week earlier, is packed with new features. This is especially true when you consider that it builds on five previous Fast ring builds that never came to the Slow ring.

“We have released Windows 10 Insider Preview Build 17074.1002 to Windows Insiders in the Slow ring,” Microsoft’s Dona Sarkar wrote in an update to the original post about build 17074 arriving for Fast ring testers.

That “.1002” bit is important, too: Microsoft previously updated build 17074 to address some problems with AMD systems.

“This build is the same as the version of Build 17074 released last week with 2 additional fixes,” Ms. Sarkar noted at the time. “We have fixed the issue causing AMD PCs to become unbootable – which means we have removed the block for AMD PCs we put in place last week. And we also fixed the issue causing certain devices to hang on the boot screen after upgrading if virtualization is enabled in the BIOS.”

To understand the changes that Slow ring testers will see in Windows 10 Insider Preview build 17074.1002, you will need to go back and review the changes that occurred in builds 17035 (November 8), 17040 (November 16), 17046 (November 22), 17063 (December 19), and 17074 (January 12). That is over two months of feature updates and additions, and a much more complete picture of what Windows 10 version 1803 will contain. So you’ve got your work set out for you.



Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (16)

16 responses to “Windows 10 Build 17074.1002 Comes to the Slow Ring”

  1. glenn8878

    These Windows changes are a blur. I can no longer keep track. Many are minor UI enhancements. What we need is a tally sheet that can track year to year updates.

  2. MentalPatient

    This is what I got...

    Windows 10 Insider Preview 17074.1002 (rs_prerelease_flt)

    Failed to install on ‎1/‎20/‎2018 - 0xc1900101 just hangs on the boot screen

    • TerryTurbo930

      In reply to MentalPatient:

      MP, Here’s my routine that I complete before each and every update for Win 10 Home Insider Preview Eval. Run Settings >Update &Security >Troubleshoot>Windows Update OK/Apply Fixes (2) that pop up, then when it cleans up, run it again to make it absolutely pristine and ready for the Update. Also run sfc/scannow from right click Win start button >Command Prompt (Admin). I run a multiple repeat of HDD cleaning scrubbing and so far my updates have uploaded and installed 98% successfuly without me pulling out what little hair I have left on my head! I hope my suggestions and tips work for you, if not just chuck em. I saw your post and it reminded me of where I was last year, and I posted a question on the MS Win 10 Insider Dev Board. I guess I posted it on the “wrong” board and was made acutely aware of my unforgivable mistake. So I posted my god damn strongest apology to the moderator and swore I’d never post a single solution to a more pompous group of sanctimonious assholes who don’t deserve my insides that work with little input. The other sure fire tip is, copy/paste the error code when the install fails and Google it. Select the Microsoft knowledge base link usually the second entry down and double check the error against the KB file that will lead you to a MS tool for you to download and run that app and that will corrrct and/or repair the error i.e. database, definition base, and then I always perform a complete shutdown not just a reboot. I hope these ideas work for you. It has taken me awhile to learn them. I only wish I had someone to hold my hand back in the day and helped in my understanding of computer science instead of being 95% self-taught. Take care, be well and pass along what you have learned to someone who is struggling with computer basics. Terry

  3. michael

    my brother's pushing 70 and still using WinXP because he can't handle all these new OS changes.

    • wright_is

      In reply to [email protected]:

      It's not like Windows 8, where the menu disappeared, Windows 10 is pretty much the same, apart from the control panel being split in two. If he can use XP, then he shouldn't have any problems with Windows 10. :-S

  4. hrlngrv

    Maybe a dumb question, but who uses Insider Slow Ring? Even Slow Ring would be unwise on production systems, and I can't figure much point to testing usually out-of-date Insider builds. Besides, isn't it now the Super Slow Ring now that there's a Wink-Wink-Nudge-Nudge-Know-What-I-Mean Faster than Fast Ring?

    • wright_is

      In reply to hrlngrv:

      Testers, businesses using a test environment to make sure their applications work with the new version, when it comes out. Trainers as well, so they can get an idea of what is to come and prepare their courses.

      Enthusiasts who want to see what is coming, but can't afford the time or money required for a dedicated test rig, so want the new features before they are in the release version, but want some trade-off for stability in every day life.

      • hrlngrv

        In reply to wright_is:

        I understand testing, but aside from the LAST slow ring build before a mass market build, what are the benefits of the previous slow ring builds? IOW, would fast ring builds provide better basis for testing and preparing trainers?

        As for enthusiasts, they're unwise to use even slow ring builds on production/work machines. TBH, if one has 8GB RAM, one could use VMs to test Insider builds while using presumed stable builds for work. With less than 8GB RAM, one shouldn't be taking chances or perhaps even considering oneself an enthusiast.

        • wright_is

          In reply to hrlngrv:

          Not really, things are too fluid in Fast Ring for most of those things.

          Testing software stability on an unfinished OS isn't that useful, you don't know if it is the OS or the application that is causing problems.

          Testing also takes a long time (weeks or months) and you need a stable baseline, so getting weekly OS changes doesn't help. Especially if you find there are major problems that need addressing.