Yes your right that the majority probably is unaware. And yes because I am on this forum I see a lot of stuff discussed. But it still can create confusion, at least it does occasionally for me. sometimes something will become a topic and it's not always apparent it's insider related. I think the point I was trying to make with MS is there are so many different versions of Windows and/or rings going on that it isn't that clear. Although I am not into trying insider stuff on my own machine as I have little spare time to be worrying about so many updates and even less to worry about bugs or side effects I try to take an interest in it. Just so I know what to expect. I watch carefully for news of public updates on here, so I am prepared that should I login I know one is coming. This forum does decent job of segregating it but on occasion it does confuse. And unfortunately as much as try with tech I do get confused easily!!!
Last edited by Scottyboy99; 04 Sep 2016 at 16:54.
This is going to sound rude, but I'm going to say it anyway. Everyone needs to understand the difference between being an Insider and a regular user. Learn which build you're on . . . the Build alone will tell you if you're using the Insider version or the End User version. If you are using Build 10586.xxx (July 29 Update) or Build 14393.xxx (2016 Anniversary Update), then you're an End User.
Someone on the Insider Program is, purely and simply, a Windows 10 Beta Tester. We're all gluttons for punishment. The Fast Ring is for those of us who like to live on the "bleeding edge" while the Slow Ring is for those who are of a more cautious nature, but still wish to be on the leading edge.
Watch Windows 10 News; the announcements are very clear as to what the subject is. When posting, give the Build you're using; since I'm an Insider, I will try to remember to preface my question or answer with the Build I'm on. IOW, I may ask this:
Insider Build 14905 - When clicking on the Power Button to shut down my machine, nothing happens. Is anyone else experiencing this?
FYI, in actuality, that was an issue with Insider Build 14905; however, with the release of Insider Build 14915, the issue was resolved.
I'd do the same if I were using the Anniversary Update Build 14393.xxx.
I'm grateful that John has seen fit to provide these forums at no cost to us. He is absorbing the cost, which in my estimation, must be considerable. I, for one, won't ask for more . . .
It's been unfortunate that the Windows 10 News section is now more about problems with both RTM and Insider versions, not so much about news anymore.
Will someone that knows, please explain why the Anniverary update was almost immediately followed a pretty large update ( this one) within the same month of release??
I see two possibilities here:
(1) That all the beta testers and MS involved missed a massive problem which non testers unearthed almost immediately --- A very unlikely possibility.
(2) The royal "Everyone" knew about the problem. However, Marketing was NOT prepared to delay the release, telling "everyone" that they can fix it with an update, but the Anniversary release WILL go ahead regardless ... ??