Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows 11 Pro will soon require a Microsoft Account during initial setup

theverge.com

Post reply on HN
Print view View original

361–370 of 469 posts

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#361

Post by Kye »

amanzi wrote: post #346
Kye wrote: post #161

Earlier quoted context omitted.

Linux really doesn't have good alternatives for most of the tools I use, and none of it runs in Wine and similar, so I hope not.

What are you missing out the most on Linux? For me, it's really just the Office apps, everything else I've found works just as well on Linux.

Pretty much everything. I've used both Linux and Windows extensively over the last decade plus and am very familiar with the available alternatives and find those that exist for what I use lacking. Trying to list them off just invites people to pick suggestions off whatever list they have ready without regard for the needs of the person they're suggesting at, and it gets tiresome.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#362

Post by michaelmrose »

secondcoming wrote: post #353
michaelmrose wrote: post #200

Earlier quoted context omitted.

Linux actually has excellent 4K support. If you primarily use KDE and QT applications under x11 what you need to do is virtually nothing or set DPI. GTK apps can be adjusted by setting GDK_SCALE=Integer. If you want to tweak text bigger or smaller set your default font size in GTK/KDE settings to be larger or smaller. There is an entire section on handles you can tweak in different environments odds are you need few…

It's 2022. Linux should be past the point of requiring people to hunt for a config file so they can edit it to get a usable display.

It's a free software provided gratis by volunteers. Desktop Linux is mostly by techies and for techies despite any other aspirations. Things that work great but require configuration don't always get looked at or worked on. This is especially true if they only effect a tiny minority of users.

https://linux-hardware.org/?view=mon_resolution

You should absolutely volunteer your time to address high dpi configuration out of the box across several of the most popular distros. I mean for example KDE software already works basically perfectly right out of the box. So all you really need to do is automate the process of choosing ideal font sizes, scaling settings etc.

Push out looks-right.sh to various distros to be run at installation.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#363

Post by Zhyl »

BenjiWiebe wrote: post #336
Dylan16807 wrote: post #297

Earlier quoted context omitted.

That doesn't solve the problem.

You can hammer the keyboard to make a Microsoft account and then delete that account. Microsoft won't have learned much about you except that your name is wduwbe73ne7cn47wh.

I still wouldn't call that "easy" though. Sure it's a small number of steps, but they aren't trivial or immediately obvious and don't escape the basic issue that we're having to evade the operating system here.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#365

Post by _nickwhite »

This news about Windows 11 Pro "requiring" a Microsoft Account is a bit of sensationalism. You can still bypass it and create a local account if you know what you're doing, as has been the case for several years with Windows 10. Here is how:

When you see the “Let’s Connect You To A Network” page, hit “Shift” and “F10” simultaneously. This will bring up the Command Prompt to which you type the command: taskkill /F /IM oobenetworkconnectionflow.exe

When Windows 11 setup detects networking is not possible, it will let you create the local account as always.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#366

Post by Tijdreiziger »

_nickwhite wrote: post #365

This news about Windows 11 Pro "requiring" a Microsoft Account is a bit of sensationalism. You can still bypass it and create a local account if you know what you're doing, as has been the case for several years with Windows 10. Here is how: When you see the “Let’s Connect You To A Network” page, hit “Shift” and “F10” simultaneously. This will bring up the Command Prompt to which you type the command: taskkill /F /IM…

IIUC, the news is that Microsoft will be disabling this workaround and requiring an active network connection on setup.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#367

Post by nneonneo »

_nickwhite wrote: post #365

This news about Windows 11 Pro "requiring" a Microsoft Account is a bit of sensationalism. You can still bypass it and create a local account if you know what you're doing, as has been the case for several years with Windows 10. Here is how: When you see the “Let’s Connect You To A Network” page, hit “Shift” and “F10” simultaneously. This will bring up the Command Prompt to which you type the command: taskkill /F /IM…

I’m not sure whether to take this as a joke or not. Not using a Microsoft account requires using a terminal to kill a process? Is there seriously no other way?

If so, I suspect that Microsoft have succeeded in their goal to get everyone to use their accounts, because I don’t see the vast majority of users going down this route.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#368

Post by judge2020 »

amanzi wrote: post #62

Using Windows with a Microsoft account introduces all sorts of issues that only power users tend to come across, and power users are who Windows Pro is targeted for. For example, RDP'ing to a Windows Pro computer with a Microsoft account becomes a lot more difficult. Another example is that Windows still needs a local username and password, even if you've logged in with a Microsoft account, and this can get out of sy…

The RDP issue is only a problem because the UI doesn't make it clear that you need to have password sign-in enabled to RDP, when setting up a PIN during initial setup disables password sign-in.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#369

Post by Kaze404 »

amanzi wrote: post #345
smoldesu wrote: post #276

Earlier quoted context omitted.

It's not everyone's favorite answer, but LibreOffice works fine for me. I've set a number of documents with it (including my own resume) and it works perfectly fine. It's not the most intuitive program ever made, but it's nothing if not comprehensive.

You're not going to convince hardcore Office users (like me) that LibreOffice is good enough. I try it occasionally on my Linux laptop, and I have nothing good to say about it.

That's interesting, I have the opposite perspective. I'm not a power user in the sense that I use it to write documents, but at work we generate docx files from code (not a good idea) and a significant amount of the time we have perfectly fine files that render as we expect on LibreOffice but break unexpectedly on Word. Sometimes it even renders fine on the web version, but still incorrectly in Word itself.

Edit: I should clarify that I don't mean to contradict you. Just thought it would be an interesting perspective to read about.

Re: Windows 11 Pro will soon require a Microsoft Account during initial setup

#370

Post by freeflight »

amanzi wrote: post #62

Using Windows with a Microsoft account introduces all sorts of issues that only power users tend to come across, and power users are who Windows Pro is targeted for. For example, RDP'ing to a Windows Pro computer with a Microsoft account becomes a lot more difficult. Another example is that Windows still needs a local username and password, even if you've logged in with a Microsoft account, and this can get out of sy…

> Another example is that Windows still needs a local username and password, even if you've logged in with a Microsoft account, and this can get out of sync if you change your Microsoft account password online, meaning you now have a different local password to your online account.

I tripped over this when I first started using Windows 10. It felt so unbelievably frustrating to be locked out of a local system because I couldn't remember my MS account password anymore.

As a reward for that, I discovered MS was indexing the contents of all my hard-drives, could suddenly look at my local hard drives just by logging into my MS account from any other device.

Even tho I went out of my way to disable as much of the home-phone functionality as possible; Just takes one auto-update to default a lot of these settings without ever informing the user about it.

Post reply on HN