Windows 10: Windows 10 build 9879 going out to 'slow ring' participant

More

 

Thanks for the information.
Jeff

:)

 

Grey screen after login Windows 10

But Windows 10 1709 was just released to the slow ring this week and has only been available to Windows 10 Insider participants on the fast ring prior to that. Have you been running Windows 10 Insider builds all along?

 

Is Windows Phone really unpopular or is it just that they arent available in any stores you can walk into?

According to the Windows Insider Blog here:

Announcing Windows 10 Insider Preview Build 16288 for PC & Build 15250 for Mobile - Windows Experience Blog

the latest available Insider build for the Fast ring (which runs ahead of the Slow ring) is 15250 - are you sure you have 16236 on your Lumia 950 ?

 

They should be warned about how buggy it is, so they can avoid it...

 

New icons, being able to hide the search and task view buttons, a buggier version of IE, and a crippled OneDrive does not count as "a vast amount of improvements" in my book. Supposedly they are working on a "hotfix" for all the issues people have been having, but I doubt it could fix most of the issues in this build.

 

The only thing that W10 brings to the table for me is windowed APP's that I do not use.

 

I was referring specifically to build 9879 vs 9860. The four things I listed pretty much some up the "improvements" between the two builds. The Neowin refers to those changes as "a vast amount," which I think is hyperbole to an extreme.

 

Unless MS fixes the bugs in 9879 they shouldn't release it to the slow ring. Each release has more bugs than the last. Adding more features is nice but fixing bugs is just as important if not more. I thought the whole idea of a slow release was to introduce more features with less bugs.

 

Nothing quite like running a "preview," emphatically beta OS but then expecting it to be bug free, is there?...*Wink

 

Well put. Given the point in the life cycle of this "preview" I have to say it's doing rather well.
I've stayed away from third party tools: AV's, firewalls, and tools like classic shell and guess what?? I've had minimal issues. Sooner or later those items will work fine with Win10 but for now I'm simply testing out what MS provides with the preview and programs that I run on a daily basis. Stuff like Python, PyScripter and Java development tools(Eclipse). And they work for me.

Yes, it still has a hick-up from time to time but I expect that and when it happens I report what occurred to MS.

Jeff

 

Well put. Given the point in the life cycle of this "preview" I have to say it's doing rather well.
I've stayed away from third party tools: AV's, firewalls, and tools like classic shell and guess what?? I've had minimal issues. Sooner or later those items will work fine with Win10 but for now I'm simply testing out what MS provides with the preview and programs that I run on a daily basis. Stuff like Python, PyScripter and Java development tools(Eclipse). And they work for me.

Yes, it still has a hick-up from time to time but I expect that and when it happens I report what occurred to MS.

Jeff I'm surprised it's running as well as it is, too...*Wink Only things that bug me are things like the "CPU-Z won't run until I rename the executable" conundrum...! It's a little utility I run every now and then to amuse myself...nothing to it--id's your cpu, ram buses, etc. That's it--a pure read-only kind of application. Ran great under 8.1 and all previous iterations of Windows. Author updates the program regularly. Free ware. Win10 (all builds so far) refuses to install it because of "compatibility" reasons--but soon as I rename the install exe all is well--program installs and runs like it always has. Why would Microsoft not want me to run a read-only hardware config program? Love to be the fly on the wall there...

 

Waltc, it is not that anyone doesn't understand that there are going to be bugs. We all accept, and fully expect, that it will have them. What doesn't make sense however, is that this current build has a LOT more bugs than the previous one, and has gotten a lot of complaints about the so called "improvements", and MS, in its infinite wisdom, responds by saying "Great! Sounds like its ready for the people who have decided they'd whether wait longer between builds than have more bugs. Oh, but don't worry, we're working on an update to fix one of the minor ones."

 

the reason for this update being more buggy than the first 2 is because the first 2 updates was just windows 8.1 with a few minor changes, bugs should be expected as they more away from the windows 8 kernel.

 

Agreed. And no one said this was going to be an improved "stable" version. Somehow people conveniently forget this is STILL a beta program. And as such, those "new improvements" may not work as well either. This is why you fill out a bug report.

I say again, if Microsoft laid the golden OS, people would still complain because MS hadn't handed it to them personally.