Microsoft forces Windows 11 to use a Microsoft Account – removes bypassnro | Hacker News Reader

Microsoft forces Windows 11 to use a Microsoft Account – removes bypassnro

windowscentral.com

10 pointsjosephcsible8 comments

Since bypassnro.cmd is a two line batch script and it isn't clear from the release notes, is this going to also prevent the reg edit from working, or is this simply removing the script? If it is just removing the script, a Shift + F10 should get you going with a cmd prompt where you can edit the registry from there and reboot.

I hope it doesn’t. At times need to run windows stuff and just prefer to just start a vm without networking. I wonder how this impacts people who do testing. Maybe they just have domain joined machines or just use windows accounts.

The only reason anyone uses Windows anymore is for gaming, and that's quickly being vaporized. Yes many corporates still use it, but they HAVE an alternative which is the mac ecosystem.

macOS is not an alternative to Windows in many industries due to lack of available industry-specific applications/hardware; this even applies to Excel, which there is no practical alternative for.

And certainly not for gaming, where Windows remains more popular than ever thanks to Sony 'seeing the light' and starting to port games to Windows. According to the Steam survey, Windows, all versions, make up 97% of users.

https://store.steampowered.com/hwsurvey

>The only reason anyone uses Windows anymore is for gaming

We've been hearing that for 5? 10? 15? 20? years?

Windows is really decent, even for developers since WSL2 is there.

WSL2 is an absolute pile of manure. The last time I attempted to use it only a year or two ago, it regularly ended up in some bizarre unrecoverable state for which the only recourse was completely uninstalling and reinstalling it. And this happened frequently, at least once or twice a week. It is absolutely not a good or useful piece of software and is incredibly unreliable.

N=1

Many developers leverage WSLv2 with no issues, or certainly not that issue.

The only challenge I remember was network part like proxies or communication between Windows and WSL2->Docker

Reply on news.ycombinator.com