Windows 10 Fast ring 14986 was this actually tested at all?

Avatar
17

Seems that the builds even the fast ring releases need to be tested more. I have been installing Fast Ring builds for years and the newly released build 14986 is the first one which refuses to install properly.

As I write this there is a 24 page thread with various suggestions from end users including registry hacks to disable Unified Update Platform (UUP) which is apparently in this build. Some have had success while other like myself simply see this build go through the process of installing the update only to have it revert back out. No error messages are displayed.

So far except for the initial post by a Microsoft Forum Moderator/ Support Engineer no followups over the last 3 days from anyone from Microsoft. They have asked for specific information regarding the existing boxes and configuration but that is as far as it has gotten.

I just hope that if this installation issue is related to UUP which appears at least in some cases it is, since registry hacks that bypass UUP, to allow the upgrade to work does not become another AUP.

I have seen this same thing happen with AUP on some systems where the upgrade fails, reverts back to the prior build and without any indication to the end user what the issue is. The system then tries to install the same update over and over again. 

Comments (17)

17 responses to “Windows 10 Fast ring 14986 was this actually tested at all?”

  1. Avatar

    2015

    This is the first build to use an entirely new updating mechanism, of course there were bound to be issues. You are in the fast ring mate, and testing this stuff on a wide scale is exactly what the fast ring is for.  With limited internal testing rings, it's impossible to test on every configuration of PC/software.  That's what we're here for.

    If it offends you, perhaps Fast isn't the right ring for you.  In fact, MS and media commentators specifically warn you not to run Fast ring on your primary PC or "production" machines.  If you have an issue, just blow it away and re-install. Simple. No ifs, no buts.

    Me specifically, I accept the risk and run it on my primary gaming PC. I can't get 14986 to even be offered to my PC, even after a re-install last night. I'm stuck on 14959 and Windows Update says I'm up to date  Clearly they're busy squashing bugs from all the feedback they're getting, so I'm betting it'll sort itself out soon.

    • Avatar

      1377

      In reply to Ryster:

      In my own case, 14986 doesn't work well in VirtualBox VMs nor, from what I've read, in VMWare VMs. That seems to be wide spread, which does raise some concerns that MSFT didn't test 14986 much in VMs.

      I can live with this. There was another flaky build sometime last Spring, and my response this time will be the same as then: give feedback (as long as the app don't crash the VM), then cease using the VM until the next build.

    • Avatar

      3385

      In reply to Ryster:

      There is no way in heck I would put Fast Ring on a production machine. The machine is strictly for testing Fast Ring builds. Its a generic install of Windows 10 Fast Rings and that is all it is used for. The issue is that there are people over in the Insider Build MS Communities and they are without direction from any one from Microsoft. We are going around in circles. I don't expect Microsoft to have a fix but at least have some sort of presence in the Insider Community.

      People keep saying run the Windows Update Troubleshooter. Well I have and each time I have run it finds the same problem and says it fixes it. Yet right after that I run it again and again it finds the same problem.

      I have just reset this box and wiped out all my files. If 14986 reverts back to 14971 on this box then there is definitely something in this build that needs fixing and hopefully Microsoft conveys to us Insiders over on their communities that they do indeed care and are aware of this issue.

       

  2. Avatar

    5447

    Weird how this goes so differently for different people; This build installed overnight without me even seeing it, and my SP4 has been awesome ever since.

  3. Avatar

    2

    I guess I'm of two minds here. On the one hand, this is the point of the Insider program, to test new things. On the other, yes, there are a lot of new features and changes in this one, and it's a mess. I guess it all comes down to tolerance. But if you're in the Fast ring, you should expect this: Fast ring testers see the builds before Microsoft employees, so the testing is happening. We're doing it.

    • Avatar

      3385

      In reply to Paul Thurrott:

      It would not be so bad if the installer / upgrade actually generates an error but it does not. Its the same issue I have seen with the Anniversary Update. They system balks restores the prior build and tells the end user nothing about what is happening.  It then attempts to install the same update over and over again. It even shows that it has successfully installed the update in the Update History list when in fact it never did of course.

       

       

    • Avatar

      1377

      In reply to Paul Thurrott:

      I tolerate a lot in Insider builds, but I cease seeing the point to using Insider builds when they crash minutes apart. Because I don't use Insider builds in production machines (or VMs), I don't have to use it at all, and in this case I've now ceased using it, so also ceased being able to provide feedback, until the next build.

      When Insider builds are as flaky as 14986, I figure the build is so much of a PITA to use that MSFT gets much less useful feedback than they do from more robust builds. Maybe MSFT gets some value I can't comprehend from 10 times as many IT CRASHES feedback posts and 1/10 as many features-related feedback posts. If not, 14986 couldn't have been much use to MSFT.

  4. Avatar

    5496

    Insiders are BETA.

  5. Avatar

    5664

    I had to go back to Release Preview honestly.

    I'm going to miss some the UI niceties that the current builds have, but I'm not going to deal with apps randomly starting in the background lol

  6. Avatar

    250

    This release installed on a Surface Book with no problems other than unexpectedly slow progress, but an old Surface Pro and a Dell XPS15 seemingly froze and refused to initiate the download process for hours. Those two managed to update themselves overnight, and I got the "Hi" screen when I woke them up in the morning. An old HP Stream 8 tablet that I almost never use but keep updating just to see if it has a breaking point ended up in a peculiar hybrid state. The "About" page shows that it is still on 14971, and that is also the last reported installed update. But in the Installed Updates section labeled "Feature Updates," a term I don't completely understand, more than a dozen successful and failed installation attempts are recorded for 14986. On one occasion I saw a brief message about (I think) insufficient RAM and recovery media, but it blanked before I could find my glasses and read it in detail.

    I agree there is a lot going on in this update, but on the machines where I have  explored it a little it seems pretty stable. The update process itself was the most irritating part of the experience.I suspect the 15000 and up releases will install more smoothly when we begin to see them.

Leave a Reply