You're right. We go on what information we can get. Sometimes that doesn't include Major/Minor. Usually, that's pretty safe to guess. I find it concerning that your maths education is so evidently lacking, by saying that it's been 10.0.x since at least 9885, but that this means that as much as 60% of Buildfeed is wrong. BuildFeed currently has 676 builds. Even if we assume that 6.4.9879.x were the last 6.4.x builds, which I doubt strongly, then that means there are 74 builds labelled as 6.4 when they should be 10.0 - or just 11% of builds. BuildFeed is of course an open site anyway. You can either apply for an editor account using the registration form of the site (though I'll only approve people who contact me separately and have some sort of evidence to show they can be trusted), or you can go full hog and completely clone the site, because the entire site source is on GitHub, and there's an API to grab the entire build list (works great with Office 16's Power Query in Excel). Alternatively, you can just contact one of us on Twitter (best people are myself - @tomhounsell, Nick - @nickurtnl, or Ahmed - @AirportsFan, or @buildfeed directly, since we do monitor it). Fwiw, we've noticed (along with others) that there's been very few builds trickling through Windows Update over the past week or so - our guess now is that it's likely related to the Major/Minor change, and that we're not getting notifications through about 10.0.x builds. I also consider it entirely possible that MS have at times reverted to 6.4 temporarily which may explain why we still get an occasional build through, mainly for compatibility testing. And sure, the moment someone does an objectively better job than BuildFeed at doing what BuildFeed does, I'll personally take down the website and just redirect it to this new site.
@hounsell: Cool story bro, it's still containing fake data (not talking about 6.4) so crap site anyway. And LOL, yes MS building sometimes a NT10.0 and sometimes a NT6.4 (depend of the weather) I never said ithome had wrong, from what I remember they always posted legit stuff.
Feel free to point to which data you think they're fake, and we'll look into it. We wrote some info regarding 9891's situation: buildfeed.net/actions/info/680/
MS Logic: Let's skip Windows 9 because awful garbage abandoned code might lazy check Windows 9 as Win 9x, but now we are going to jump the NT Kernel, which we've kept at 6.X for 8 years, straight up to 10.
Hello guys I have a problem since a few day with 9879 build : i cannot open the Settings Modern UI App. I try with an other user, the same problem. Trying SFC/ Scannow and chkdsk /f /r /b, same problem. I run ccleaner in order to clean a lot, but, always the same problem. Anyone had a workaround in order to solve it ? Thanks a lot Best regards, Nixeus
It's because you changed the replacevan key in registry to 0, open regedit as admin browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Settings\Network, change it back to 1 and it will work again
The worst case scenario is that I have none of those drivers installed on my system. Well, I will do the troubleshooting when I am chanced to find out the culprit. I have found the solution after few troubleshooting and it works like a charm. Clear the 'Turn on fast start-up(recommended)' at the Power Option.
Yes, that number change may mean some issues when the build becomes available for testing. This is okay, since the technical preview should only be used for testing. It's drivers that may present the worst issues. Then again, there may be none at all.
From wireless keyboard to smartphone, my Bluetooth devices lag in responding to communication with the system.