Regular Windows 10 Users Who Manually Look For Updates May End Up Downloading Beta Code, Microsoft Says (techspot.com)
In addition to relying on Windows Insiders, employees, and willing participants for testing updates, Microsoft is pushing patches before they are known to be stable to regular users too if they opt to click the "check for updates" button on their own, the company said. From a report: In a blog post by Michael Fortin, Corporate Vice President for Windows, it is made clear that home users are intentionally being given updates that are not necessarily ready for deployment. Many power users are familiar with Patch Tuesday. On the second Tuesday of each month, Microsoft pushes out a batch of updates at 10:00 a.m. Pacific time on this day containing security fixes, bug patches, and other non-security fixes. Updates pushed out as part of Patch Tuesday are known as "B" release since it happens during the second week of the month.
During the third and fourth weeks of the month are where things begin to get murky. Microsoft's "C" and "D" releases are considered previews for commercial customers and power users. No security fixes are a part of these updates, but for good reasoning. Microsoft has come out to directly say that some users are the guinea pigs for everyone else. In some fairness to Microsoft, C and D updates are typically only applied when a user manually checks for updates by clicking the button buried within Settings. However, if end users really wanted to be a part of testing the latest features, the Windows Insider Program is designed exactly for that purpose. Further reading: Windows 10's 'Check for updates' button may download beta code.
During the third and fourth weeks of the month are where things begin to get murky. Microsoft's "C" and "D" releases are considered previews for commercial customers and power users. No security fixes are a part of these updates, but for good reasoning. Microsoft has come out to directly say that some users are the guinea pigs for everyone else. In some fairness to Microsoft, C and D updates are typically only applied when a user manually checks for updates by clicking the button buried within Settings. However, if end users really wanted to be a part of testing the latest features, the Windows Insider Program is designed exactly for that purpose. Further reading: Windows 10's 'Check for updates' button may download beta code.
How pathetic. Give it up and switch to Linux.
They've always used their customers as beta testers. That shit started at least as early as the MS-DOS days.
water is wet. Stay tuned to know how wet is it.
That is totally not cool.
...to go away. There is no other explanation.
Microsoft's updates are like a box of chocolates...
Now, you don't even have to sign up for it!
Excuse me, but if you are using Windows 10 because it is production level code which means no surprises - shouldn't you always get production level code?
And my dad asks why I don't trust Windows 10.
Mimetics Inc. Twitter
I think most Windows 10 users are doing everything they can to disable any and all updates of any kind considering Microsoft's track record recently.
Yeah, undermining people's trust in your OS's security update mechanism is great idea. I really hope someone got a raise for this.
F*uking hell. What kind of drugs would any semi-self-respecting developer have to be on to suggest this, and gets it ok'd by multiple managers.
Can we bring public stoning back.
... users ... may end up downloading beta code ...
Microsoft really is trying to be more like Google. :-)
It must have been something you assimilated. . . .
I have a laptop I infrequently use that has Windows 10 (non-Pro) installed on. I boot it up once a month to install updates (so I don't need to wait for update installs when I need to use it for other things) and I always use the "check for updates" button to make sure there aren't any more updates to install. I absolutely do not want beta updates installed on this machine nor would it be good for beta testing them since I hardly use it. This is just giving me more incentive to finally get around to wiping it and putting Linux on it.
What if this signature were clever?
"B", "C", "D"? Heck, I'd give them an "F".
Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
Yeah. M$. No more update for Windows 10 until you actually finish them. Tested them. Tested again. Tested a third time. Sent to the insiders to let them test it.
Repeat this process at least 3 times before releasing to the general public.
I am pretty sure people are getting tired of being your beta testers. Especially when don't listen and release a service pack that delete user data.
You can't comp out with the "Good, fast, cheap, pick 2" excuse. You have the money so you can make a good fast product if you wanted.
Which apparently you don't.
http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
Show me when in the EULA it says this.
http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
Considering not only big things like the whole data deletion thing (which was shipped despite people flagging it in the Windows Insider reporting app) but little things like Notepad defaulting to creating UTF-8 files with a Byte-Order Mark with its new UTF-8 handling (to be fixed in the next release apparently), it seems Microsoft's internal setup is basically unable to see any issues until after they're shipped. So why not ship things to some normal customers earlier, then? It's a classic Microsoftian workaround!
I remember sigs. Oh, a simpler time!
We are all Microsoft Beta testers
Windows 10 Enterprise is the product; along with Office 365 they lock in business users and bring in revenue for Microsoft. The other versions of W10 are various levels of unpaid alpha testing (Insiders) and unpaid beta testing (Home/Pro). Windows 10 Enterprise LTSC is a red-headed step child that Microsoft begrudgingly has around because it has to.
How about you give user's back the ability to fully control their update cycle and clearly liable those updates as beta or release? You literally did that for who knows how many years until M$ decided to take away user choice and started burning users with bad updates often enough that they started to look for ways around the new update cycle.
Having looked into the EULA and its online extensions, yes, Microsoft does claim to pretty much own the data on the PC. Moreover, they claim they can delete any "app" they consider is priated - and - they claim - they can run code remotely. You basically sign away your first born. Have a look:
[quote]
However, before more data is gathered, Microsoft’s privacy governance team, including privacy and other subject matter experts, must approve the diagnostics request made by a Microsoft engineer. If the request is approved, Microsoft engineers can use the following capabilities to get the information:
-Ability to run a limited, pre-approved list of Microsoft certified diagnostic tools, such as msinfo32.exe, powercfg.exe, and dxdiag.exe.
-Ability to get registry keys.
-All crash dump types, including heap dumps and full dumps.
[end quote]
Source:
https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
You can't actually believe that was a legitimate post
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
Mac OS is not too bad.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
Seriously.
Slashdot, fix the reply notifications... You won't get away with it...
In the last month I've build two machines for my family & loaded up two notebooks for friends. One new gaming desktop which seemed to patch fine & reloaded Win 7 on the older one. The notebooks were from friends who wanted me to cleanup, patch, Windows & load, activate, & patch Office.
So of course I "check for updates" over & over until all updates are loaded. Does this mean I possibly loaded beta patches? That last notebook was really a POS, some cheap HP from wallymart sub $300. It took forever to patch & I was seeing weird errors & had to retry many times. I blamed on HP but maybe it was MS.
So what does one do with a new machine? Turn it on & hope for the best? That worked so well in the past.
SLOWER TRAFFIC KEEP RIGHT