Right now, Microsoft is inspiring horror stories with "forced upgrades" and/or incessant nagging to upgrade to Windows 10. Yet more horror stories are being generated with the invasive "telemetry", and the personalized advertising found within the OS.
In recent weeks, the wife has complained about the Windows 10 nag. She runs Win7 Home Premium, and got the nag until I "fixed" it. I run Win7 Pro in my virtual machines, and I don't get the nag. I got the telemetry updates, but not the nag.
Those of us over a certain age remember the original separation between enterprise grade Windows NT (NT3, NT4, Win2000) and the consumer grade Windows (Win 1, 2, 3, 3.11, 95, 98, 98SE and Millenium) until they were joined together with WinXP. With WinXP, we saw the same OS used for consumer and enterprise, with advanced features enabled in Pro and Enterprise, and the same features disabled in consumer versions.
So, here we are today, with MS trying to phase out Win7, and force feeding Windows 10 to the world.
Going forward - is MS also going to force feed Win10 to the professional/enterprise world? Or, will they send the consumer and enterprise OS's down divergent paths? Are we going to see insecurity built into the consumer line of products, and better security and features built into the professional lines?
What does the future hold? Any guesses?
(Score: 5, Informative) by Jiro on Saturday December 26 2015, @01:21AM
They're already doing this without bothering with firmware updates. Look up UEFI Secure Boot.
(Score: 2, Informative) by frojack on Saturday December 26 2015, @02:27AM
UEFI does not prevent Linux or BSD from booting.
UEFI is really a useless addition, offering no believable protection. But it also does not prevent the installation of other OSes.
Not only does windows offer to sign any linux distro shims (to avoid the FTC perhaps) but there is also a pure linux UEFI signing project as well as a FreeBSD project underway.
You do know, don't you, that Microsoft can't just flip a switch and force the entire world to run Windows because of UEFI?
No, you are mistaken. I've always had this sig.
(Score: 0) by Anonymous Coward on Saturday December 26 2015, @09:53AM
You do know, don't you, that Microsoft can't just flip a switch and force the entire world to run Windows because of UEFI?
Of course I know that. If they could they already would have flipped that switch.
(Score: 1, Informative) by Anonymous Coward on Saturday December 26 2015, @04:21PM
The important issue is who controls the signing keys: Microsoft and Intel or the user/owner of the computer.
If the owner of the computer is not allowed to tell the BIOS which signing keys they trust, then yes, Microsoft can "flip a switch" and refuse to boot other OSs. I suspect it would require cooperation with hardware vendors, which hopefully would not be forthcoming.
BTW, Microsoft already tried to lock out other OSs with UEFI; with their Windows RT flop.
Microsoft mandating Secure Boot on ARM, making Linux installs difficult [arstechnica.com]
(Score: 2) by Jiro on Saturday December 26 2015, @06:12PM
The statement wasn't about preventing Linux or BSD from booting, it was about preventing "(non-signed) Linux or BSD" from booting. UEFI secure boot does prevent non-signed Linux oir BSD from booting.
(Score: 2, Disagree) by frojack on Saturday December 26 2015, @08:20PM
Seems pretty clear to me that the statement made no such distinction, and was a blanket assertion that Microsoft was in a position to enforce Windows as the ONLY operating system allowed in the world.
But I'll go back and re-read what was actually written, if you promise to do the same.
No, you are mistaken. I've always had this sig.