EFF Petitioned To Investigate Windows 10 Upgrades (change.org)
An anonymous reader writes: One of the most frustrating things about the ongoing stream of stories about Windows 10 upgrades is that there seems to be no way to hold Microsoft to account. Or perhaps there is: a petition asking the Electronic Frontier Foundation to investigate has now been posted on Change.org.
The petition argues "people are being tricked or forced into upgrading to Windows 10 from their current, preferred version of Windows," and describes Microsoft's actions as "ignorantly unethical at best and malicious at worst."
The petition argues "people are being tricked or forced into upgrading to Windows 10 from their current, preferred version of Windows," and describes Microsoft's actions as "ignorantly unethical at best and malicious at worst."
Anything and everything related to Windows 10 is stated plainly in the EULA.
First year law school stuff here folks. A EULA is a contract, and MS is just doing what they stated they have the right to do as per the agreement spelled out quite plainly before someone hits "accept".
Any investigations by the EFF's part or even lawsuits will be smacked into oblivion. In fact, the EULA forces all claims into arbitration anyway, so any judge who has gotten beyond first semester in law would find the EFF culpable for vexatious litigation, and find for MS.
- Back up your data files - Wipe that abusive shit operating system off your machine - Install Linux.
Don't look back.
I have had more clients ask about Linux in the past 3 months then in the past three years prior. With everything moving to the cloud, it is actually happening.
I believe it doesn't send *memory dumps*. It sends crash dumps, also called "mini-dumps" within Visual Studio. They don't have the heap. They include registers. They include callstacks, but I think these only include address pointers not the stackframes themselves (not sure). They include a list of all loaded DLLs/EXEs in the process along with the address at which they're loaded.
(I work at Microsoft, and have had to investigate the occasional crash-dum- to fix whatever bug caused it, and the dumps didn't have any heap, so it's always taken a lot of guesswork and detective work to figure out what the bug was based only on the callstack).