*** Microsoft Windows 11 Thoughts & Discussion Thread ***

So many YT videos and searching to try and figure it out and time lost.
Finding that information in a blog eventually brought a resolve.

If you happen to be on the Home edition of Windows then there is no gpedit tool, you will need to be familiar with Powershell.

It should not have to be so convoluted.
Exactly, I had to read so many articles, why don't Microsoft just provide a clear guide on their website, or better yet, have their own software guide you through it?

A LOT of the articles I found seemed like they were a bad solution to me, e.g. disable/open your firewall, re-enable insecure connections, re-install insecure components and I really just wanted a fix that aligned with whatever changes Microsoft had made, but there wasn't a good guide for that.
 
That's the point, in my case.
I had 24h2 running previously and all seemed well with shares to my WD Cloud devices, that was an updated Windows 11.

This time it was a fresh install of Windows 11 24h2.
When it was time to think about access to the drives I did not realise that those changes had been implemented, as it had previously worked fine.

My, My Cloud drives support SMB 1, 2 and 3. So I'm guessing that it is the SMD signed sharing that was the problem.

The only clue was an error trying to connect.

Whilst there can be reasoning as to why they do these things, it is not reflected when I tried to have access without being given information as to why it had stopped working.

So many YT videos and searching to try and figure it out and time lost.
Finding that information in a blog eventually brought a resolve.

If you happen to be on the Home edition of Windows then there is no gpedit tool, you will need to be familiar with Powershell.

It should not have to be so convoluted.
Got a link to the post at all?

Would be handy just in case anyone else comes across the issue
 
Got a link to the post at all?

Would be handy just in case anyone else comes across the issue

I posted it mate on the previous page :)

 
I posted it mate on the previous page :)

Must have missed that.

Thanks a lot
 
The popular "bypassnro" command, which let users to skip connecting to the Internet and signing into a Microsoft Account, is being removed.

Microsoft has confirmed that it's removing a popular command line that allowed users to bypass connecting to the internet and signing into a Microsoft Account when setting up a new Windows 11 PC.

When Windows 11 version 22H2 launched, Microsoft made it so that both Windows 11 Home and Windows 11 Pro required an internet connection and Microsoft Account during setup, but users quickly discovered workarounds.

The most popular workaround is the command "bypassnro", which when entered into a command prompt while in the Windows setup experience would enable the ability to skip connecting to the internet, therefore bypassing the Microsoft Account requirement.

As noted in the latest Windows 11 preview build, the company is removing the command to "ensure that all users exit setup with internet connectivity and a Microsoft Account."

This change will be controversial among Windows users who don't want to use a Microsoft Account on Windows 11. Going forward, there will be no easy way to bypass this requirement on a new Windows 11 PC.

There are still ways to bypass these requirements, including setting up an unattend.xml installation, which bypasses the setup phase, but this requires a lot more work and includes creating a new Windows installation image from scratch.

Currently, it's also possible to manually re-add the bypassnro command to your system by typing the following into a command prompt: "reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f shutdown /r /t 0"
Microsoft will force Windows 11 installs to use a Microsoft Account — confirms removal of popular setup bypass - Windows Central
 
Last edited:
I have just used Rufus to create the ISO, and it offers options for local account creation, bypass options for Windows requirements etc. If you want them.
I am not sure what MS are heading towards, to limit those options, or even, at some point, to remove them entirely..?!

It has given me an impression for some time now that the biggest concerns I have about Windows, is the seemingly non-optional way of installing it, not everyone is going to be conversant of being able to use Rufus or create an online account and then even know about the possibilities of changing, by doing "things" to have a local one.
I don't have enough knowledge and experience to appreciate this part, but I do use Outlook as my mail client, for some specific reason, and yet the "new" version does seem rather simplistic and lacking compared to the old.

I get the impression, doubt their intention, but MS is doing a great job at making those consider Linux, lol...!

Even I have, and that says something...!
 
Last edited:
From what I read it's just the bypassnro script that's being removed and you can still enable the option with the registry entry listed. They haven't removed the option entirely (yet) but are making it more difficult.
 
Absolute worse case scenario is make a fake MS account to log into during initial set up and then once in the OS, sign out back to local account.

But I'm sure it'll be while before it gets to that.
 
Back
Top Bottom