Sujet : Re: The problem with not owning the software
De : nospam (at) *nospam* needed.invalid (Paul)
Groupes : alt.comp.os.windows-11 comp.os.linux.advocacyDate : 31. Dec 2024, 17:01:01
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vl14ft$2a7g9$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Ratcatcher/2.0.0.25 (Windows/20130802)
On Mon, 12/30/2024 9:06 PM, Andrzej Matuch wrote:
On 2024-12-30 19:53, Lawrence D'Oliveiro wrote:
On Mon, 30 Dec 2024 19:12:32 -0500, Paul wrote:
>
https://www.ghacks.net/2022/06/27/bypass-windows-11-microsoft-account-requirement-and-deny-privacy-questions-during-setup-with-rufus/
>
"Remove requirement for Secure Boot and TPM 2.0"
>
This is why they say, Windows is a great OS -- if your time is worth
nothing.
And there is no reason to believe that circumventing both Secure Boot and TPM will lead to a Windows installation which will respect your decision not to use either feature. Any update you are forced to install might suddenly lock you out of the system. Microsoft confirmed quite recently that despite news that they were easing the TPM requirement, they're not actually planning on doing so. <https://windowsforum.com/threads/windows-11-installation-no-easing-of-hardware-requirements-confirmed.347806/>
The message here is clear: if you like AMD but don't want fTPM stuttering, your best choice is Linux.
You are aware of course, that inconveniencing large numbers of
customers, or even the hint of damage to user data (accessibility),
leads to class action lawsuits.
People even resorted to small claims courts, to get
even with Microsoft.
The people in the windows group, do not worry too much about
the poorly handled messaging. If they release four P.R. messages,
and the message in each one is different, you're free to latch
onto one of them and run with it.
For the time being, Rufus works. Why does Rufus continue to work ?
Do you see the message yet ? The two faces of Microsoft.
Microsoft *have* been quietly closing doors behind the scenes.
The activity aligns with the directive to "do security".
For example, some easy ways of "becoming administrator", so you
can recover from deleting administrator by accident, have been
removed. In addition, psexec no longer works, and another piece
of code that could make you TrustedInstaller, similarly no longer
works. these are baby steps, but they're also a "message" to
customers at large.
Paul