deif writes:
A recent Windows 8 update detects other OS installs as a "security problem", erases non-windows bootloaders and enables UEFI Secure Boot, all without user intervention.
I contacted MS by chat (in Dutch, so of no use to you) and asked them about this. They vehemently denied this was possible at all. Multiple times, in no uncertain terms. Same results were acquired by phone: denial, denial, denial.
I pointed out that it did actually happen, and that it wan't the first time such a thing had happened in the history of MS updates -so "impossible" was BS, to put it shortly.
Then came a chat reply which amounted to "MS updates makes sure W8 functions fine, it does not look at other OS's integrity". This is, in my opinion, a de-facto admission that yes, the update had changed the bootloader back to the W8 version that ignores other OS's, and yes, it had set the UEFI setting back to "secure boot."
(Score: 4, Informative) by DarkMorph on Wednesday March 26 2014, @10:37AM
Now, this was strictly about installing the OS. For an update for the OS, which is already installed, to act this way seems really aggressive which is why I'm sure many are doubting that the claim in TFA is true... Should be easy to verify though - if it's true it should be reproducible.
(Score: 0) by Anonymous Coward on Wednesday March 26 2014, @10:01PM
Older Windows installers would clobber your MBR silently almost immediately
From what I've seen in forums, this is not just a legacy problem. [google.com]
this was strictly about installing the OS
Yeah, the very first stuff I read about Linux said in bold INSTALL WINDOZE FIRST. [google.com]
-- gewg_
(Score: 0) by Anonymous Coward on Thursday March 27 2014, @10:15PM
This has been documented many times.
Page with multiple links. [techrights.org]
-- gewg_