Microsoft ends use of "bypassnro.cmd" for Windows 11: Difference between revisions
Added context on why a user would want to use a local account |
Added Consumer response |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
Bypassing this step is popular because linking the login of a Windows installation to a Microsoft account leads to the hard drive encryption keys being sent to Microsoft, loss of access to the system and data if Microsoft blocks the account, allows for telemetry data to be associated with the user's personal information and requires the user to consent to even more terms when creating the account vs. just the EULA for the software. | Bypassing this step is popular because linking the login of a Windows installation to a Microsoft account leads to the hard drive encryption keys being sent to Microsoft, loss of access to the system and data if Microsoft blocks the account, allows for telemetry data to be associated with the user's personal information and requires the user to consent to even more terms when creating the account vs. just the EULA for the software. | ||
== Consumer response == | |||
A new way has been discovered, using Developer Console with Ctrl + Shift + J and enter | |||
WinJS.Application.restart("ms-cxh://LOCALONLY") | |||
Command<ref>{{Cite web |date=9 Apr 2025 |title=WinJS-Microsoft-Account-Bypass |url=https://github.com/the-P1neapple/WinJS-Microsoft-Account-Bypass/blob/main/README.md |url-status=live |archive-url=https://web.archive.org/web/20250828053532/https://github.com/the-P1neapple/WinJS-Microsoft-Account-Bypass/blob/main/README.md |archive-date=28 Aug 2025 |access-date=28 Aug 2025 |website=Github}}</ref>. | |||
=References= | =References= | ||
<references /> | <references /> | ||
[[Category:Microsoft]] | [[Category:Microsoft]] | ||