Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #18070 > unrolled thread

A new, potentially better Windows account bypass has been discovered

Back to article view | Back to alt.comp.os.windows-11

Contents

  A new, potentially better Windows account bypass has been discovered CrudeSausage <crude@sausa.ge> - 2025-03-30 07:24 -0400
    Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-03-30 05:00 -0700
      Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-30 15:28 -0700
        Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-03-30 22:42 -0700
          Re: A new, potentially better Windows account bypass has been discovered Newyana2 <newyana@invalid.nospam> - 2025-03-31 08:05 -0400
            Re: A new, potentially better Windows account bypass has been discovered Frank Slootweg <this@ddress.is.invalid> - 2025-03-31 12:46 +0000
            Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 11:07 -0700
              Re: A new, potentially better Windows account bypass has been discovered Newyana2 <newyana@invalid.nospam> - 2025-03-31 14:59 -0400
                Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 13:00 -0700
            Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-03-31 11:15 -0700
              Re: A new, potentially better Windows account bypass has been discovered Newyana2 <newyana@invalid.nospam> - 2025-03-31 14:56 -0400
                Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 13:03 -0700
                Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-04-01 05:24 -0700
                  Re: A new, potentially better Windows account bypass has been discovered Newyana2 <newyana@invalid.nospam> - 2025-04-01 09:30 -0400
        Re: A new, potentially better Windows account bypass has been discovered Jack <Jack@invalid.invalid> - 2025-04-02 05:39 +0100
      Re: A new, potentially better Windows account bypass has been   discovered Stan Brown <the_stan_brown@fastmail.fm> - 2025-03-31 12:12 -0700
        Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 13:10 -0700
    Re: A new, potentially better Windows account bypass has been discovered pothead <pothead@snakebite.com> - 2025-03-30 13:49 +0000
      Re: A new, potentially better Windows account bypass has been discovered Borax Man <rotflol2@hotmail.com> - 2025-03-31 09:21 +0000
        Re: A new, potentially better Windows account bypass has been discovered Paul <nospam@needed.invalid> - 2025-03-31 07:05 -0400
      Re: A new, potentially better Windows account bypass has been discovered CrudeSausage <crude@sausa.ge> - 2025-03-31 09:09 -0400
    Re: A new, potentially better Windows account bypass has been discovered micky <NONONOmisc07@fmguy.com> - 2025-03-31 12:57 -0400
      Re: A new, potentially better Windows account bypass has been discovered CrudeSausage <crude@sausa.ge> - 2025-03-31 13:55 -0400
        Re: A new, potentially better Windows account bypass has been discovered micky <NONONOmisc07@fmguy.com> - 2025-03-31 21:50 -0400
          Re: A new, potentially better Windows account bypass has been discovered Paul <nospam@needed.invalid> - 2025-03-31 22:59 -0400
          Re: A new, potentially better Windows account bypass has been discovered CrudeSausage <crude@sausa.ge> - 2025-04-01 08:45 -0400
            Re: A new, potentially better Windows account bypass has been discovered micky <NONONOmisc07@fmguy.com> - 2025-04-01 18:00 -0400
              Re: A new, potentially better Windows account bypass has been discovered CrudeSausage <crude@sausa.ge> - 2025-04-01 20:17 -0400
                Re: A new, potentially better Windows account bypass has been discovered micky <NONONOmisc07@fmguy.com> - 2025-04-06 22:19 -0400
      Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 11:13 -0700
        Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-03-31 11:23 -0700
          Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-31 13:23 -0700
            Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-04-01 01:59 -0700
              Re: A new, potentially better Windows account bypass has been discovered ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-04-01 09:01 -0700
                Re: A new, potentially better Windows account bypass has been discovered T <T@invalid.invalid> - 2025-04-01 20:34 -0700

Page 1 of 2  [1] 2  Next page →

#18070 — A new, potentially better Windows account bypass has been discovered

<https://www.windowscentral.com/software-apps/windows-11/an-even-better-microsoft-account-bypass-for-windows-11-has-already-been-discovered>

Earlier this week, Microsoft announced that it was removing a popular 
command line that allowed users to bypass connecting to the internet and 
signing into a Microsoft Account during the setup phase on Windows 11.

Since 2022, Windows 11 has required both an internet connection and 
Microsoft Account when setting up a new PC. Naturally, not everybody 
wants this, and so workarounds and bypasses have been discovered.

The most popular bypass was "oobe\bypassnro" which, when typed into the 
command prompt during the Windows 11 setup experience, would enable a 
button that let you skip connecting to the internet, thus bypassing the 
Microsoft Account requirement.

Microsoft has said that it is removing this command to push more users 
to connect to the internet and sign in with a Microsoft Account during 
the setup phase. Understandably, the internet is outraged.

While oobe\bypassnro is being removed, the actual registry entry that 
enables the button to skip connecting to the internet isn't, at least 
not yet. So you can still manually create the registry edit yourself, 
but that's a much longer and tedious process.

But fret not, as a new, perhaps better bypass has already been 
discovered that still uses the command prompt (which you can open with 
Shift + F10) and makes skipping the Microsoft Account sign-in step a 
total breeze.

Discovered by user @witherornot1337 on X, typing "start 
ms-cxh:localonly" into the command prompt during the Windows 11 setup 
experience will allow you to create a local account directly without 
needing to skip connecting to the internet first.

The new bypass involves creating a local account via the older Windows 
10 interface. (Image credit: Windows Central)
The command will pop up an older, Windows 10 style interface that lets 
you specify a username and password for the local account. Then, 
clicking next will take you straight to preparing the desktop, before 
being asked to specify your privacy settings.

We tested this method on the latest Windows 11 preview build 26200 and 
can confirm that it works. It's a much more streamlined process compared 
to the old oobe\bypassnro method, which required the PC to restart and 
to slowly progress through the Windows 11 setup experience before 
landing on the desktop.

This new method doesn't require a restart and skips straight to the end 
of the setup experience, landing just at the point where Windows asks 
you to configure privacy settings. It's a win all around!

While this new workaround works for now, something tells me that 
Microsoft is likely going to crack down on these bypasses more often 
going forward. So, it's unknown how long this new bypass will work, so 
use it while you can!
-- 
God be with you,

CrudeSausage
John 14:6

[toc] | [next] | [standalone]

#18072

On 3/30/25 4:24 AM, CrudeSausage wrote:
> <https://www.windowscentral.com/software-apps/windows-11/an-even-better- 
> microsoft-account-bypass-for-windows-11-has-already-been-discovered>
> 
> Earlier this week, Microsoft announced that it was removing a popular 
> command line that allowed users to bypass connecting to the internet and 
> signing into a Microsoft Account during the setup phase on Windows 11.
> 
> Since 2022, Windows 11 has required both an internet connection and 
> Microsoft Account when setting up a new PC. Naturally, not everybody 
> wants this, and so workarounds and bypasses have been discovered.
> 
> The most popular bypass was "oobe\bypassnro" which, when typed into the 
> command prompt during the Windows 11 setup experience, would enable a 
> button that let you skip connecting to the internet, thus bypassing the 
> Microsoft Account requirement.
> 
> Microsoft has said that it is removing this command to push more users 
> to connect to the internet and sign in with a Microsoft Account during 
> the setup phase. Understandably, the internet is outraged.
> 
> While oobe\bypassnro is being removed, the actual registry entry that 
> enables the button to skip connecting to the internet isn't, at least 
> not yet. So you can still manually create the registry edit yourself, 
> but that's a much longer and tedious process.
> 
> But fret not, as a new, perhaps better bypass has already been 
> discovered that still uses the command prompt (which you can open with 
> Shift + F10) and makes skipping the Microsoft Account sign-in step a 
> total breeze.
> 
> Discovered by user @witherornot1337 on X, typing "start ms- 
> cxh:localonly" into the command prompt during the Windows 11 setup 
> experience will allow you to create a local account directly without 
> needing to skip connecting to the internet first.
> 
> The new bypass involves creating a local account via the older Windows 
> 10 interface. (Image credit: Windows Central)
> The command will pop up an older, Windows 10 style interface that lets 
> you specify a username and password for the local account. Then, 
> clicking next will take you straight to preparing the desktop, before 
> being asked to specify your privacy settings.
> 
> We tested this method on the latest Windows 11 preview build 26200 and 
> can confirm that it works. It's a much more streamlined process compared 
> to the old oobe\bypassnro method, which required the PC to restart and 
> to slowly progress through the Windows 11 setup experience before 
> landing on the desktop.
> 
> This new method doesn't require a restart and skips straight to the end 
> of the setup experience, landing just at the point where Windows asks 
> you to configure privacy settings. It's a win all around!
> 
> While this new workaround works for now, something tells me that 
> Microsoft is likely going to crack down on these bypasses more often 
> going forward. So, it's unknown how long this new bypass will work, so 
> use it while you can!


It is so, so much easier just to tell the installer that you
are on a domain.

[toc] | [prev] | [next] | [standalone]

#18082

T wrote on 3/30/2025 5:00 AM:
>>
>> Earlier this week, Microsoft announced that it was removing a popular 
>> command line that allowed users to bypass connecting to the internet 
>> and signing into a Microsoft Account during the setup phase on Windows 11.

> 
> It is so, so much easier just to tell the installer that you
> are on a domain.
> 

Left out a fews critical pieces of necessary information.

   => Requires Pro, Enterprise or Edu SKU
   => Don't join the domain and pay attention to the the provided options
-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#18088

On 3/30/25 3:28 PM, ...w¡ñ§±¤ñ wrote:
> T wrote on 3/30/2025 5:00 AM:
>>>
>>> Earlier this week, Microsoft announced that it was removing a popular 
>>> command line that allowed users to bypass connecting to the internet 
>>> and signing into a Microsoft Account during the setup phase on 
>>> Windows 11.
> 
>>
>> It is so, so much easier just to tell the installer that you
>> are on a domain.
>>
> 
> Left out a fews critical pieces of necessary information.
> 
>    => Requires Pro, Enterprise or Edu SKU
>    => Don't join the domain and pay attention to the the provided options


you are correct.  I can't stand the home edition, so
when I assist someone with a new computer, I have them
get the pro version.  So I often forget about the
home edition.

And a lot of my customers opt for Tiny 11 when they hear
the difference.

[toc] | [prev] | [next] | [standalone]

#18101

On 3/31/2025 1:42 AM, T wrote:

>>    => Requires Pro, Enterprise or Edu SKU
>>    => Don't join the domain and pay attention to the the provided options
> 
> 
> you are correct.  I can't stand the home edition, so
> when I assist someone with a new computer, I have them
> get the pro version.  So I often forget about the
> home edition.
> 

  I use only Home, since it's essentially the same as Pro
for less money. I add a copy of gpedit, don't use bitlocker,
and don't know of anything else I'm missing.

   But I'm wondering about all this fretting. I've updated to
Win11 three times and just left the ethernet unplugged. I
choose the option to not allow updates while installing and
just do it offline. Is that no longer available?

[toc] | [prev] | [next] | [standalone]

#18103

Newyana2 <newyana@invalid.nospam> wrote:
[...]

>   I use only Home, since it's essentially the same as Pro
> for less money. I add a copy of gpedit, don't use bitlocker,
> and don't know of anything else I'm missing.
> 
>    But I'm wondering about all this fretting. I've updated to
> Win11 three times and just left the ethernet unplugged. I
> choose the option to not allow updates while installing and
> just do it offline. Is that no longer available?

  I also had no problem. I used a similar disconnect from the network at
the right time (just before "Who is going to use this device?"), but
that was two and a half years ago.

  Also: It used to be possible to convert a Microsoft Account to a local
account. I used this on Windows 8.1 [1] when some app install had
tricked me into switching my local account into a Microsoft Account.

  Is that no longer possible (in Windows 10/11)?

[1] It got the info from
<https://www.technorms.com/30853/switch-between-local-and-microsoft-accounts>
but that's a dead link.
If needed/wanted, I can post my notes of what I did.

[toc] | [prev] | [next] | [standalone]

#18115

Newyana2 wrote on 3/31/2025 5:05 AM:
> On 3/31/2025 1:42 AM, T wrote:
> 
>>>    => Requires Pro, Enterprise or Edu SKU
>>>    => Don't join the domain and pay attention to the the provided options
>>
>>
>> you are correct.  I can't stand the home edition, so
>> when I assist someone with a new computer, I have them
>> get the pro version.  So I often forget about the
>> home edition.
>>
> 
>   I use only Home, since it's essentially the same as Pro
> for less money. I add a copy of gpedit, don't use bitlocker,
> and don't know of anything else I'm missing.
> 
>    But I'm wondering about all this fretting. I've updated to
> Win11 three times and just left the ethernet unplugged. I
> choose the option to not allow updates while installing and
> just do it offline. Is that no longer available?
> 

<qp>
We’re removing the bypassnro.cmd script from the build to enhance 
security and user experience of Windows 11. This change ensures that all 
users exit setup with internet connectivity and a Microsoft Account.
</qp>

cf.
<https://blogs.windows.com/windows-insider/2025/03/28/announcing-windows-11-insider-preview-build-26200-5516-dev-channel/>

The change in 24H2 noted in above Insider article eliminates the no 
internet connection(i.e. ethernet not connected, wifi disabled via router 
etc.) method.
  - the current discussion in the Enterprise community appears to 
indicate this change removes the build code(script) in Windows 24H2 that 
calls the  registry values that permitted use of the 'no internet 
connection' for creating a local account => script removed, registry 
values remain intact
  - that same discussion also indicates that other methods may still be 
available.
  a. the one noted earlier(choose domain option route) in this thread for 
Pro/Enterprise/Edu SKU's

  b. the possibility of command line approach by manually entering the 
following commands to achieve the same functionality as the now-removed 
script
  reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v 
BypassNRO /t REG_DWORD /d 1 /f
  shutdown /r /t 0

  c. Pausing setup at the Secondary Layout Screen and use the Developer 
Console(entering a restart command and executing the command), exit the 
Developer Console to a refreshed Secondary Layout Screen with the Win10- 
style Local Account setup option
   WinJS.Application.restart("ms-cxh://LOCALONLY")

Note: yymv if MSFT, in the future, if code changes to Windows 11 24H2 
removes the ability for any or all the above methods(a, b, c)

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#18123

On 3/31/2025 2:07 PM, ...w¡ñ§±¤ñ wrote:
> Newyana2 wrote on 3/31/2025 5:05 AM:
>> On 3/31/2025 1:42 AM, T wrote:
>>
>>>>    => Requires Pro, Enterprise or Edu SKU
>>>>    => Don't join the domain and pay attention to the the provided 
>>>> options
>>>
>>>
>>> you are correct.  I can't stand the home edition, so
>>> when I assist someone with a new computer, I have them
>>> get the pro version.  So I often forget about the
>>> home edition.
>>>
>>
>>   I use only Home, since it's essentially the same as Pro
>> for less money. I add a copy of gpedit, don't use bitlocker,
>> and don't know of anything else I'm missing.
>>
>>    But I'm wondering about all this fretting. I've updated to
>> Win11 three times and just left the ethernet unplugged. I
>> choose the option to not allow updates while installing and
>> just do it offline. Is that no longer available?
>>
> 
> <qp>
> We’re removing the bypassnro.cmd script from the build to enhance 
> security and user experience of Windows 11. This change ensures that all 
> users exit setup with internet connectivity and a Microsoft Account.
> </qp>
> 
> cf.
> <https://blogs.windows.com/windows-insider/2025/03/28/announcing-windows-11-insider-preview-build-26200-5516-dev-channel/> 
> 
> 
> The change in 24H2 noted in above Insider article eliminates the no 
> internet connection(i.e. ethernet not connected, wifi disabled via 
> router etc.) method.
>   - the current discussion in the Enterprise community appears to 
> indicate this change removes the build code(script) in Windows 24H2 that 
> calls the  registry values that permitted use of the 'no internet 
> connection' for creating a local account => script removed, registry 
> values remain intact
>   - that same discussion also indicates that other methods may still be 
> available.
>   a. the one noted earlier(choose domain option route) in this thread 
> for Pro/Enterprise/Edu SKU's
> 
>   b. the possibility of command line approach by manually entering the 
> following commands to achieve the same functionality as the now-removed 
> script
>   reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v 
> BypassNRO /t REG_DWORD /d 1 /f
>   shutdown /r /t 0
> 
>   c. Pausing setup at the Secondary Layout Screen and use the Developer 
> Console(entering a restart command and executing the command), exit the 
> Developer Console to a refreshed Secondary Layout Screen with the Win10- 
> style Local Account setup option
>    WinJS.Application.restart("ms-cxh://LOCALONLY")
> 
> Note: yymv if MSFT, in the future, if code changes to Windows 11 24H2 
> removes the ability for any or all the above methods(a, b, c)
> 
     Thanks. I expect I'll have to thoroughly research this if
and when I build another system.

[toc] | [prev] | [next] | [standalone]

#18129

Newyana2 wrote on 3/31/2025 11:59 AM:
> On 3/31/2025 2:07 PM, ...w¡ñ§±¤ñ wrote:
>> Newyana2 wrote on 3/31/2025 5:05 AM:
>>> On 3/31/2025 1:42 AM, T wrote:
>>>
>>>>>    => Requires Pro, Enterprise or Edu SKU
>>>>>    => Don't join the domain and pay attention to the the provided 
>>>>> options
>>>>
>>>>
>>>> you are correct.  I can't stand the home edition, so
>>>> when I assist someone with a new computer, I have them
>>>> get the pro version.  So I often forget about the
>>>> home edition.
>>>>
>>>
>>>   I use only Home, since it's essentially the same as Pro
>>> for less money. I add a copy of gpedit, don't use bitlocker,
>>> and don't know of anything else I'm missing.
>>>
>>>    But I'm wondering about all this fretting. I've updated to
>>> Win11 three times and just left the ethernet unplugged. I
>>> choose the option to not allow updates while installing and
>>> just do it offline. Is that no longer available?
>>>
>>
>> <qp>
>> We’re removing the bypassnro.cmd script from the build to enhance 
>> security and user experience of Windows 11. This change ensures that 
>> all users exit setup with internet connectivity and a Microsoft Account.
>> </qp>
>>
>> cf.
>> <https://blogs.windows.com/windows-insider/2025/03/28/announcing-windows-11-insider-preview-build-26200-5516-dev-channel/> 
>>
>>
>> The change in 24H2 noted in above Insider article eliminates the no 
>> internet connection(i.e. ethernet not connected, wifi disabled via 
>> router etc.) method.
>>   - the current discussion in the Enterprise community appears to 
>> indicate this change removes the build code(script) in Windows 24H2 
>> that calls the  registry values that permitted use of the 'no internet 
>> connection' for creating a local account => script removed, registry 
>> values remain intact
>>   - that same discussion also indicates that other methods may still be 
>> available.
>>   a. the one noted earlier(choose domain option route) in this thread 
>> for Pro/Enterprise/Edu SKU's
>>
>>   b. the possibility of command line approach by manually entering the 
>> following commands to achieve the same functionality as the now-removed 
>> script
>>   reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v 
>> BypassNRO /t REG_DWORD /d 1 /f
>>   shutdown /r /t 0
>>
>>   c. Pausing setup at the Secondary Layout Screen and use the Developer 
>> Console(entering a restart command and executing the command), exit the 
>> Developer Console to a refreshed Secondary Layout Screen with the 
>> Win10- style Local Account setup option
>>    WinJS.Application.restart("ms-cxh://LOCALONLY")
>>
>> Note: yymv if MSFT, in the future, if code changes to Windows 11 24H2 
>> removes the ability for any or all the above methods(a, b, c)
>>
>      Thanks. I expect I'll have to thoroughly research this if
> and when I build another system.

Also, atm, it's unclear(different reports) about retaining the registry 
value. Four different pieces of feedback indicate different scenarios for 
these two items on Win11 24H2
  1. Registry value present
  2. Registry value not present

Discussion on the above centers on the use of the script.
  - script(first use) creates registry values when BypassNRO method is used
  - script after having been used in the past, Windows retains registry 
values
  - no prior use of the script, no registry value present.
  - no prior use of the script, registry value present

The variation around those four has too many possibilities when one 
considers the source of the Windows image placed on the device
  - BYO with media (clean install)
  - BYO by an OEM system builder (clean install with setup b/f system 
delivery but with a Local Account created
  - OEM built device for consumers
  - OEM built device for business
  i.e. the OOBE experience can/may be different

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#18117

On 3/31/25 5:05 AM, Newyana2 wrote:
> I've updated to
> Win11 three times and just left the ethernet unplugged

That was my trick.  But M$ caught on to it and insists now.

This is one of the reason I adore Tiny-11.  No Bull S***!

[toc] | [prev] | [next] | [standalone]

#18122

On 3/31/2025 2:15 PM, T wrote:
> On 3/31/25 5:05 AM, Newyana2 wrote:
>> I've updated to
>> Win11 three times and just left the ethernet unplugged
> 
> That was my trick.  But M$ caught on to it and insists now.
> 
> This is one of the reason I adore Tiny-11.  No Bull S***!

   Are you builing it yourself with scripts or downloading? I've
come across several options, but no complete list. The github
site listys what's not in it, but I've already removed all those
things. It doesn't explain details like why it doesn't require an MS
account.

   I guess I must have got in under the wire. The latest box
I built was only 2 months ago. At the time I had no trouble
just leaving it unplugged. It's very creepy to think that I
might pay for software that won't work unless I let it call
home and give them personal info.

[toc] | [prev] | [next] | [standalone]

#18130

Newyana2 wrote on 3/31/2025 11:56 AM:
> On 3/31/2025 2:15 PM, T wrote:
>> On 3/31/25 5:05 AM, Newyana2 wrote:
>>> I've updated to
>>> Win11 three times and just left the ethernet unplugged
>>
>> That was my trick.  But M$ caught on to it and insists now.
>>
>> This is one of the reason I adore Tiny-11.  No Bull S***!
> 
>    Are you builing it yourself with scripts or downloading? I've
> come across several options, but no complete list. The github
> site listys what's not in it, but I've already removed all those
> things. It doesn't explain details like why it doesn't require an MS
> account.
> 
>    I guess I must have got in under the wire. The latest box
> I built was only 2 months ago. At the time I had no trouble
> just leaving it unplugged. It's very creepy to think that I
> might pay for software that won't work unless I let it call
> home and give them personal info.

Under the wire?
  The change was released in the Insider Dev build.
  => roll out to all 24H2 devices will(like in the past) be a staged 
deployment.
  i.e. under the wire, atm, is a moving target for both consumer and 
business SKU's

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#18153

On 3/31/25 11:56 AM, Newyana2 wrote:
> On 3/31/2025 2:15 PM, T wrote:
>> On 3/31/25 5:05 AM, Newyana2 wrote:
>>> I've updated to
>>> Win11 three times and just left the ethernet unplugged
>>
>> That was my trick.  But M$ caught on to it and insists now.
>>
>> This is one of the reason I adore Tiny-11.  No Bull S***!
> 
>    Are you builing it yourself with scripts or downloading? I've
> come across several options, but no complete list. The github
> site listys what's not in it, but I've already removed all those
> things. It doesn't explain details like why it doesn't require an MS
> account.
> 
>    I guess I must have got in under the wire. The latest box
> I built was only 2 months ago. At the time I had no trouble
> just leaving it unplugged. It's very creepy to think that I
> might pay for software that won't work unless I let it call
> home and give them personal info.

https://www.auslogics.com/en/articles/what-is-tiny11-install-tiny-windows-11-to-lightweight-your-os/
https://archive.org/details/tiny11-2311
https://archive.org/download/tiny11-2311

[toc] | [prev] | [next] | [standalone]

#18156

On 4/1/2025 8:24 AM, T wrote:

> 
> https://www.auslogics.com/en/articles/what-is-tiny11-install-tiny-windows-11-to-lightweight-your-os/ 
> 
> https://archive.org/details/tiny11-2311
> https://archive.org/download/tiny11-2311

    That first one is informative, but what I was hoping for
is a more technical description of *exactly* what's different.
The list of what's removed is a partial list of what I've
already removed, but I'm guessing there are more under-the-
hood changes. For example, the matter at hand: Installing
without an MS account.

[toc] | [prev] | [next] | [standalone]

#18174

> Earlier this week, Microsoft announced that it was removing a popular 
> command line that allowed users to bypass connecting to the internet 
> and signing into a Microsoft Account during the setup phase on 
> Windows 11.
Not a big deal. There is nothing in this because it was the official 
script from Microsoft and you can still see it on your Windows 11 at 
this link on your machine: 
<"C:\Windows\System32\oobe\BypassNRO.cmd">
It is a script so DON'T Click on it but just go to the folder and open 
in Notepad to see what is in it. You will find it is a very simple 
script that anyone can still type it out when installing Windows 11. It 
is just this in the script:

> @echo off
> reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
> shutdown /r /t 0

Microsoft has stopped putting that script in the Insider's Version but 
users can still type it out by pressing Shift+F10 at the time of 
installing windows 11 or use the simple version posted by "Wither OrNot" on <https://x.com/witherornot1337/status/1906050664741937328>.

Please also note that the Insider's build is just that. It is not the 
final version and you should expect many changes by the time 25H2 is released by November.

[toc] | [prev] | [next] | [standalone]

#18127 — Re: A new, potentially better Windows account bypass has been discovered

On Sun, 30 Mar 2025 05:00:54 -0700, T wrote:
> 
> It is so, so much easier just to tell the installer that you
> are on a domain.

And it doesn't check?

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

[toc] | [prev] | [next] | [standalone]

#18131

Stan Brown wrote on 3/31/2025 12:12 PM:
> On Sun, 30 Mar 2025 05:00:54 -0700, T wrote:
>>
>> It is so, so much easier just to tell the installer that you
>> are on a domain.
> 
> And it doesn't check?
> 
Using the domain method and not joining provides the ability to create a 
local account.
i.e. when setting up one chooses the work option , a subsequent screen 
provides Sign-in option to choose Domain Join, once chosen that is 
followed by another screen that provides the ability to setup a local 
account.
  - i.e. use the Domain Join option but don't join the domain by setting 
up a Local Account.

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#18075

On 2025-03-30, CrudeSausage <crude@sausa.ge> wrote:
><https://www.windowscentral.com/software-apps/windows-11/an-even-better-microsoft-account-bypass-for-windows-11-has-already-been-discovered>
>
> Earlier this week, Microsoft announced that it was removing a popular 
> command line that allowed users to bypass connecting to the internet and 
> signing into a Microsoft Account during the setup phase on Windows 11.
>
> Since 2022, Windows 11 has required both an internet connection and 
> Microsoft Account when setting up a new PC. Naturally, not everybody 
> wants this, and so workarounds and bypasses have been discovered.
>
> The most popular bypass was "oobe\bypassnro" which, when typed into the 
> command prompt during the Windows 11 setup experience, would enable a 
> button that let you skip connecting to the internet, thus bypassing the 
> Microsoft Account requirement.
>
> Microsoft has said that it is removing this command to push more users 
> to connect to the internet and sign in with a Microsoft Account during 
> the setup phase. Understandably, the internet is outraged.
>
> While oobe\bypassnro is being removed, the actual registry entry that 
> enables the button to skip connecting to the internet isn't, at least 
> not yet. So you can still manually create the registry edit yourself, 
> but that's a much longer and tedious process.
>
> But fret not, as a new, perhaps better bypass has already been 
> discovered that still uses the command prompt (which you can open with 
> Shift + F10) and makes skipping the Microsoft Account sign-in step a 
> total breeze.
>
> Discovered by user @witherornot1337 on X, typing "start 
> ms-cxh:localonly" into the command prompt during the Windows 11 setup 
> experience will allow you to create a local account directly without 
> needing to skip connecting to the internet first.
>
> The new bypass involves creating a local account via the older Windows 
> 10 interface. (Image credit: Windows Central)
> The command will pop up an older, Windows 10 style interface that lets 
> you specify a username and password for the local account. Then, 
> clicking next will take you straight to preparing the desktop, before 
> being asked to specify your privacy settings.
>
> We tested this method on the latest Windows 11 preview build 26200 and 
> can confirm that it works. It's a much more streamlined process compared 
> to the old oobe\bypassnro method, which required the PC to restart and 
> to slowly progress through the Windows 11 setup experience before 
> landing on the desktop.
>
> This new method doesn't require a restart and skips straight to the end 
> of the setup experience, landing just at the point where Windows asks 
> you to configure privacy settings. It's a win all around!
>
> While this new workaround works for now, something tells me that 
> Microsoft is likely going to crack down on these bypasses more often 
> going forward. So, it's unknown how long this new bypass will work, so 
> use it while you can!

The oobe\bypassnro method is the only one that worked for me. That was a couple
of weeks ago. 
All the others, fake emails etc failed to work.

The easy solution is to install the professional version of Windows.
At least until they screw with that as well.



-- 
pothead
Liberalism Is A Mental Disease
Treat it accordingly
<https://www.dailymail.co.uk/health/article-14512427/Doctors-reveal-symptoms-Trump-Derangement-Syndrome-tell-youve-got-it.html>

[toc] | [prev] | [next] | [standalone]

#18097

["Followup-To:" header set to comp.os.linux.advocacy.]
On 2025-03-30, pothead <pothead@snakebite.com> wrote:
> On 2025-03-30, CrudeSausage <crude@sausa.ge> wrote:
>><https://www.windowscentral.com/software-apps/windows-11/an-even-better-microsoft-account-bypass-for-windows-11-has-already-been-discovered>
>>
>> Earlier this week, Microsoft announced that it was removing a popular 
>> command line that allowed users to bypass connecting to the internet and 
>> signing into a Microsoft Account during the setup phase on Windows 11.
>>
>> Since 2022, Windows 11 has required both an internet connection and 
>> Microsoft Account when setting up a new PC. Naturally, not everybody 
>> wants this, and so workarounds and bypasses have been discovered.
>>
>> The most popular bypass was "oobe\bypassnro" which, when typed into the 
>> command prompt during the Windows 11 setup experience, would enable a 
>> button that let you skip connecting to the internet, thus bypassing the 
>> Microsoft Account requirement.
>>
>> Microsoft has said that it is removing this command to push more users 
>> to connect to the internet and sign in with a Microsoft Account during 
>> the setup phase. Understandably, the internet is outraged.
>>
>> While oobe\bypassnro is being removed, the actual registry entry that 
>> enables the button to skip connecting to the internet isn't, at least 
>> not yet. So you can still manually create the registry edit yourself, 
>> but that's a much longer and tedious process.
>>
>> But fret not, as a new, perhaps better bypass has already been 
>> discovered that still uses the command prompt (which you can open with 
>> Shift + F10) and makes skipping the Microsoft Account sign-in step a 
>> total breeze.
>>
>> Discovered by user @witherornot1337 on X, typing "start 
>> ms-cxh:localonly" into the command prompt during the Windows 11 setup 
>> experience will allow you to create a local account directly without 
>> needing to skip connecting to the internet first.
>>
>> The new bypass involves creating a local account via the older Windows 
>> 10 interface. (Image credit: Windows Central)
>> The command will pop up an older, Windows 10 style interface that lets 
>> you specify a username and password for the local account. Then, 
>> clicking next will take you straight to preparing the desktop, before 
>> being asked to specify your privacy settings.
>>
>> We tested this method on the latest Windows 11 preview build 26200 and 
>> can confirm that it works. It's a much more streamlined process compared 
>> to the old oobe\bypassnro method, which required the PC to restart and 
>> to slowly progress through the Windows 11 setup experience before 
>> landing on the desktop.
>>
>> This new method doesn't require a restart and skips straight to the end 
>> of the setup experience, landing just at the point where Windows asks 
>> you to configure privacy settings. It's a win all around!
>>
>> While this new workaround works for now, something tells me that 
>> Microsoft is likely going to crack down on these bypasses more often 
>> going forward. So, it's unknown how long this new bypass will work, so 
>> use it while you can!
>
> The oobe\bypassnro method is the only one that worked for me. That was a couple
> of weeks ago. 
> All the others, fake emails etc failed to work.
>
> The easy solution is to install the professional version of Windows.
> At least until they screw with that as well.
>
>
>

Which they will.  These workarounds is just backing yourself into a
corner.  They'll go further and further to lock you down, force you to
use their services and cajole you into computing as per THEIR vision.
No point trying to stay afloat a sinking ship.  Abandon Windows now.

[toc] | [prev] | [next] | [standalone]

#18100

On Mon, 3/31/2025 5:21 AM, Borax Man wrote:
> ["Followup-To:" header set to comp.os.linux.advocacy.]
> On 2025-03-30, pothead <pothead@snakebite.com> wrote:
>> On 2025-03-30, CrudeSausage <crude@sausa.ge> wrote:
>>> <https://www.windowscentral.com/software-apps/windows-11/an-even-better-microsoft-account-bypass-for-windows-11-has-already-been-discovered>
>>>
>>> Earlier this week, Microsoft announced that it was removing a popular 
>>> command line that allowed users to bypass connecting to the internet and 
>>> signing into a Microsoft Account during the setup phase on Windows 11.
>>>
>>> Since 2022, Windows 11 has required both an internet connection and 
>>> Microsoft Account when setting up a new PC. Naturally, not everybody 
>>> wants this, and so workarounds and bypasses have been discovered.
>>>
>>> The most popular bypass was "oobe\bypassnro" which, when typed into the 
>>> command prompt during the Windows 11 setup experience, would enable a 
>>> button that let you skip connecting to the internet, thus bypassing the 
>>> Microsoft Account requirement.
>>>
>>> Microsoft has said that it is removing this command to push more users 
>>> to connect to the internet and sign in with a Microsoft Account during 
>>> the setup phase. Understandably, the internet is outraged.
>>>
>>> While oobe\bypassnro is being removed, the actual registry entry that 
>>> enables the button to skip connecting to the internet isn't, at least 
>>> not yet. So you can still manually create the registry edit yourself, 
>>> but that's a much longer and tedious process.
>>>
>>> But fret not, as a new, perhaps better bypass has already been 
>>> discovered that still uses the command prompt (which you can open with 
>>> Shift + F10) and makes skipping the Microsoft Account sign-in step a 
>>> total breeze.
>>>
>>> Discovered by user @witherornot1337 on X, typing "start 
>>> ms-cxh:localonly" into the command prompt during the Windows 11 setup 
>>> experience will allow you to create a local account directly without 
>>> needing to skip connecting to the internet first.
>>>
>>> The new bypass involves creating a local account via the older Windows 
>>> 10 interface. (Image credit: Windows Central)
>>> The command will pop up an older, Windows 10 style interface that lets 
>>> you specify a username and password for the local account. Then, 
>>> clicking next will take you straight to preparing the desktop, before 
>>> being asked to specify your privacy settings.
>>>
>>> We tested this method on the latest Windows 11 preview build 26200 and 
>>> can confirm that it works. It's a much more streamlined process compared 
>>> to the old oobe\bypassnro method, which required the PC to restart and 
>>> to slowly progress through the Windows 11 setup experience before 
>>> landing on the desktop.
>>>
>>> This new method doesn't require a restart and skips straight to the end 
>>> of the setup experience, landing just at the point where Windows asks 
>>> you to configure privacy settings. It's a win all around!
>>>
>>> While this new workaround works for now, something tells me that 
>>> Microsoft is likely going to crack down on these bypasses more often 
>>> going forward. So, it's unknown how long this new bypass will work, so 
>>> use it while you can!
>>
>> The oobe\bypassnro method is the only one that worked for me. That was a couple
>> of weeks ago. 
>> All the others, fake emails etc failed to work.
>>
>> The easy solution is to install the professional version of Windows.
>> At least until they screw with that as well.
>>
>>
>>
> 
> Which they will.  These workarounds is just backing yourself into a
> corner.  They'll go further and further to lock you down, force you to
> use their services and cajole you into computing as per THEIR vision.
> No point trying to stay afloat a sinking ship.  Abandon Windows now.
> 

Computing still works. SuperPI 1.5xs is still as fast as it ever was :-)
6:53 for 32 million digits of PI. 16MB of L3. 4635 Mhz
6:30 for 32 million digits of PI. 64MB of L3. 5050 Mhz

One of the two machines has an MSA. Must be the slow one :-)

I used to compare the OSes on that benchmark, but the machine
I used to use for that died (blown southbridge), so I can no
longer compare them. I used to compare them from WinXP to Win10.
Maybe Windows 7 was a few seconds faster. But there was not a
progression of "our latest OS is our best OS".

Most of the Microsoft "tricks" and "ploys" are pointless, but
it makes them happy I guess. I don't find myself buying
"XBox GamePass?" just because a Notification popped up in my face.
I don't have an XBox, and it's hard to say how a single
notification would turn me into a "rental gamer". My last copy of
Microsoft Office here, was bought in 1999, when I was
still working. And I won't need an AI to help me write a ransom note.

"Clippy"
https://uncyclopedia.com/w/images/b/b3/Mainscreen1.jpg

   Paul

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.comp.os.windows-11

csiph-web