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

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

Installing Windows 11 Without a Microsoft Account

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

Contents

  Installing Windows 11 Without a Microsoft Account Boris <nospam@invalid.com> - 2025-01-16 01:06 +0000
    Re: Installing Windows 11 Without a Microsoft Account "J. Weaver Jr." <jwjr@poREMOVETHISbox.com> - 2025-01-15 20:44 -0500
      Re: Installing Windows 11 Without a Microsoft Account ant@zimage.comANT (Ant) - 2025-01-16 02:02 +0000
        Re: Installing Windows 11 Without a Microsoft Account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-15 22:16 -0700
          Re: Installing Windows 11 Without a Microsoft Account Boris <nospam@invalid.com> - 2025-01-16 06:08 +0000
            Re: Installing Windows 11 Without a Microsoft Account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-16 11:05 -0700
    Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-15 23:04 -0500
      Re: Installing Windows 11 Without a Microsoft Account Java Jive <java@evij.com.invalid> - 2025-01-16 10:36 +0000
        Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-16 13:08 -0500
          Re: Installing Windows 11 Without a Microsoft Account Java Jive <java@evij.com.invalid> - 2025-01-17 13:16 +0000
            Re: Installing Windows 11 Without a Microsoft Account Frank Slootweg <this@ddress.is.invalid> - 2025-01-17 16:13 +0000
              Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-17 11:56 -0500
    Re: Installing Windows 11 Without a Microsoft Account Newyana2 <newyana@invalid.nospam> - 2025-01-15 23:08 -0500
      Re: Installing Windows 11 Without a Microsoft Account Newyana2 <newyana@invalid.nospam> - 2025-01-15 23:13 -0500
        Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-16 09:19 -0500
          Re: Installing Windows 11 Without a Microsoft Account Newyana2 <newyana@invalid.nospam> - 2025-01-16 11:13 -0500
            Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-16 13:14 -0500
              Re: Installing Windows 11 Without a Microsoft Account Java Jive <java@evij.com.invalid> - 2025-01-17 13:49 +0000
                Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-17 12:07 -0500
    Re: Installing Windows 11 Without a Microsoft Account Boris <nospam@invalid.com> - 2025-01-16 04:20 +0000
      Re: Installing Windows 11 Without a Microsoft Account Paul <nospam@needed.invalid> - 2025-01-16 09:50 -0500
    Re: Installing Windows 11 Without a Microsoft Account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-15 21:45 -0700
      Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-16 12:52 +0000
        Re: Installing Windows 11 Without a Microsoft Account [resend] Marion <marion@facts.com> - 2025-01-17 05:01 +0000
        Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-19 14:52 -0500
          Re: Installing Windows 11 Without a Microsoft Account [resend] Paul <nospam@needed.invalid> - 2025-01-19 15:24 -0500
            Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-19 21:39 +0000
            Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-19 16:59 -0500
              Re: Installing Windows 11 Without a Microsoft Account [resend] Paul <nospam@needed.invalid> - 2025-01-19 17:16 -0500
                Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-19 19:54 -0500
          Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-19 21:44 +0000
            Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-19 17:05 -0500
              Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-19 22:13 +0000
              Re: Installing Windows 11 Without a Microsoft Account [resend] "Carlos E.R." <robin_listas@es.invalid> - 2025-01-20 13:44 +0100
                Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-20 13:31 +0000
                Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-20 08:59 -0500
            Re: Installing Windows 11 Without a Microsoft Account [resend] Frank Slootweg <this@ddress.is.invalid> - 2025-01-20 11:34 +0000
              Re: Installing Windows 11 Without a Microsoft Account [resend] Andy Burns <usenet@andyburns.uk> - 2025-01-20 12:07 +0000
                Re: Installing Windows 11 Without a Microsoft Account [resend] Newyana2 <newyana@invalid.nospam> - 2025-01-20 09:20 -0500
                Re: Installing Windows 11 Without a Microsoft Account [resend] ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-20 13:16 -0700
              Re: Installing Windows 11 Without a Microsoft Account [resend] ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-20 12:29 -0700
            Re: Installing Windows 11 Without a Microsoft Account [resend] Daniel70 <daniel47@eternal-september.org> - 2025-01-30 20:23 +1100
        Re: Installing Windows 11 Without a Microsoft Account [resend] Frank Slootweg <this@ddress.is.invalid> - 2025-01-20 15:15 +0000
      Re: Installing Windows 11 Without a Microsoft Account "Carlos E.R." <robin_listas@es.invalid> - 2025-01-17 15:17 +0100
        Re: Installing Windows 11 Without a Microsoft Account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-18 10:22 -0700
          Re: Installing Windows 11 Without a Microsoft Account "Carlos E.R." <robin_listas@es.invalid> - 2025-01-18 21:05 +0100
            Re: Installing Windows 11 Without a Microsoft Account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-19 12:32 -0700
    Re: Installing Windows 11 Without a Microsoft Account Andy Burns <usenet@andyburns.uk> - 2025-01-16 09:11 +0000
    Re: Installing Windows 11 Without a Microsoft Account Joerg Walther <joerg.walther@magenta.de> - 2025-01-16 17:26 +0100

Page 1 of 3  [1] 2 3  Next page →

#16323 — Installing Windows 11 Without a Microsoft Account

Windows 11 Home, OEM installed on a Dell XPS 8950

When originally set up in September 2023, I was able to circumvent the 
Microsoft email account requirement by entering "no@thanks.com", when asked 
for a Microsoft account.  It worked.  I've never had a Microsoft account and 
don't want one.

Today I had to use Dell's Support Assist OS Recovery software to reinstall 
Windows 11.  (The machine would not boot after an update.)  I set it to save 
my personal data.

Of course, I'm back at being asked for a Microsoft account email, which I 
don't have.  I guess I could create an account, but I seem to remember that 
if Microsoft sets up the machine, the user's default folder will be assigned 
a cumbersome alpha-numeric-special character name, which can't be renamed.  
Am I remembering correctly?

I'm searching for a remedy.  Does anyone know what the latest work-around is?

TIA

[toc] | [next] | [standalone]

#16324

On 1/15/2025 8:06 PM, Boris wrote:
> Of course, I'm back at being asked for a Microsoft account email, which I
> don't have.  I guess I could create an account, but I seem to remember that
> if Microsoft sets up the machine, the user's default folder will be assigned
> a cumbersome alpha-numeric-special character name, which can't be renamed.
> Am I remembering correctly?
> 
> I'm searching for a remedy.  Does anyone know what the latest work-around is?

What we did: set up with a Microsoft account, create a new user with 
Administrator privs, log out, log in as the new Admin, delete the 
Microsoft account user.

You get to redo part of the initial setup, and you'll still get the 
occasional nag to "Sign in to connect your favorite Microsoft apps to 
your device", but that's it.  -JW

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

#16326

J. Weaver Jr. <jwjr@poremovethisbox.com> wrote:
> On 1/15/2025 8:06 PM, Boris wrote:
> > Of course, I'm back at being asked for a Microsoft account email, which I
> > don't have.  I guess I could create an account, but I seem to remember that
> > if Microsoft sets up the machine, the user's default folder will be assigned
> > a cumbersome alpha-numeric-special character name, which can't be renamed.
> > Am I remembering correctly?
> > 
> > I'm searching for a remedy.  Does anyone know what the latest work-around is?

> What we did: set up with a Microsoft account, create a new user with 
> Administrator privs, log out, log in as the new Admin, delete the 
> Microsoft account user.

> You get to redo part of the initial setup, and you'll still get the 
> occasional nag to "Sign in to connect your favorite Microsoft apps to 
> your device", but that's it.  -JW

At least you save your activation key with MS account too which could be handy if you ever need to reinstall from scratch.
-- 
"For the Lord is good and his love endures forever; his faithfulness continues through all generations." --Psalm 100:5. Slammy Jan. & still not fully recovered from New Yr.'s Day eve(ning) Norovirus. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
 / /\ /\ \                      Please nuke ANT if replying by e-mail.
| |o   o| |
   \ _ /
    ( )

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

#16332

Ant wrote on 1/15/25 7:02 PM:
> J. Weaver Jr. <jwjr@poremovethisbox.com> wrote:
>> On 1/15/2025 8:06 PM, Boris wrote:
>>> Of course, I'm back at being asked for a Microsoft account email, which I
>>> don't have.  I guess I could create an account, but I seem to remember that
>>> if Microsoft sets up the machine, the user's default folder will be assigned
>>> a cumbersome alpha-numeric-special character name, which can't be renamed.
>>> Am I remembering correctly?
>>>
>>> I'm searching for a remedy.  Does anyone know what the latest work-around is?
> 
>> What we did: set up with a Microsoft account, create a new user with
>> Administrator privs, log out, log in as the new Admin, delete the
>> Microsoft account user.
> 
>> You get to redo part of the initial setup, and you'll still get the
>> occasional nag to "Sign in to connect your favorite Microsoft apps to
>> your device", but that's it.  -JW
> 
> At least you save your activation key with MS account too which could be handy if you ever need to reinstall from scratch.
> 

Not entirely true.
  No such thing as an activation key
  When setting up the initial account(Microsoft Account[aka MSA], 
Activation is digitally linked to the device and also to the MSA on 
MSFT's backend servers.
  When a Local Account is recreated that same device remains diigitally 
linked to the same backend MSFT server(i.e. Activation is always linked 
to the device)
Removing the MSA account does not remove the backend linkage to the device.
Windows 8/10/11 can all be reinstalled/clean installed 'from scratch' 
since the device is digitally linked. A Microsoft account is not 
necessary to reinstall/clean install Windows.

The benefit of the MSA comes into play if the device has a major hardware 
change(CPU, Motherboard),
  - The MSA linkage to the backend server provides an additional feature 
option in Windows Troubleshooting(that does not exist when an MSA-device 
combo is not linked to the backend server). That MSA only available 
Troubleshooter feature provides an easy option to reactivate the device 
after a cpu/mobo change without extra steps *and without a product key entry'

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

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

#16334

=?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote in
news:vma4mv$3ch82$1@dont-email.me: 

> Ant wrote on 1/15/25 7:02 PM:
>> J. Weaver Jr. <jwjr@poremovethisbox.com> wrote:
>>> On 1/15/2025 8:06 PM, Boris wrote:
>>>> Of course, I'm back at being asked for a Microsoft account email,
>>>> which I don't have.  I guess I could create an account, but I seem to
>>>> remember that if Microsoft sets up the machine, the user's default
>>>> folder will be assigned a cumbersome alpha-numeric-special character
>>>> name, which can't be renamed. Am I remembering correctly?
>>>>
>>>> I'm searching for a remedy.  Does anyone know what the latest
>>>> work-around is? 
>> 
>>> What we did: set up with a Microsoft account, create a new user with
>>> Administrator privs, log out, log in as the new Admin, delete the
>>> Microsoft account user.
>> 
>>> You get to redo part of the initial setup, and you'll still get the
>>> occasional nag to "Sign in to connect your favorite Microsoft apps to
>>> your device", but that's it.  -JW
>> 
>> At least you save your activation key with MS account too which could
>> be handy if you ever need to reinstall from scratch. 
>> 
> 
> Not entirely true.
>   No such thing as an activation key
>   When setting up the initial account(Microsoft Account[aka MSA], 
> Activation is digitally linked to the device and also to the MSA on 
> MSFT's backend servers.
>   When a Local Account is recreated that same device remains diigitally 
> linked to the same backend MSFT server(i.e. Activation is always linked 
> to the device)
> Removing the MSA account does not remove the backend linkage to the
> device. Windows 8/10/11 can all be reinstalled/clean installed 'from
> scratch' since the device is digitally linked. A Microsoft account is
> not necessary to reinstall/clean install Windows.

I'm confused. You say that Windows 8/10/11 can all be reinsalled/clean
installed "from scratch' because they are digitally linked, but a MSA is
not necessary to reinstall/clean install Windows.  That sounds
contradictory.  What am I misunderstanding? 


> 
> The benefit of the MSA comes into play if the device has a major
> hardware change(CPU, Motherboard),

I'm not one to swap out a CPU or motherboard, but I see that could be
useful if one rebuilds/upgrades hardware.  Is there any advantage, to a
user like me, to otherwise have a MSA? 

>   - The MSA linkage to the backend server provides an additional feature
> option in Windows Troubleshooting(that does not exist when an MSA-device
> combo is not linked to the backend server). That MSA only available 
> Troubleshooter feature provides an easy option to reactivate the device 
> after a cpu/mobo change without extra steps *and without a product key
> entry' 
> 

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

#16347

Boris wrote on 1/15/25 11:08 PM:
> =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote in
> news:vma4mv$3ch82$1@dont-email.me:
> 
>> Ant wrote on 1/15/25 7:02 PM:
>>> J. Weaver Jr. <jwjr@poremovethisbox.com> wrote:
>>>> On 1/15/2025 8:06 PM, Boris wrote:
>>>>> Of course, I'm back at being asked for a Microsoft account email,
>>>>> which I don't have.  I guess I could create an account, but I seem to
>>>>> remember that if Microsoft sets up the machine, the user's default
>>>>> folder will be assigned a cumbersome alpha-numeric-special character
>>>>> name, which can't be renamed. Am I remembering correctly?
>>>>>
>>>>> I'm searching for a remedy.  Does anyone know what the latest
>>>>> work-around is?
>>>
>>>> What we did: set up with a Microsoft account, create a new user with
>>>> Administrator privs, log out, log in as the new Admin, delete the
>>>> Microsoft account user.
>>>
>>>> You get to redo part of the initial setup, and you'll still get the
>>>> occasional nag to "Sign in to connect your favorite Microsoft apps to
>>>> your device", but that's it.  -JW
>>>
>>> At least you save your activation key with MS account too which could
>>> be handy if you ever need to reinstall from scratch.
>>>
>>
>> Not entirely true.
>>    No such thing as an activation key
>>    When setting up the initial account(Microsoft Account[aka MSA],
>> Activation is digitally linked to the device and also to the MSA on
>> MSFT's backend servers.
>>    When a Local Account is recreated that same device remains diigitally
>> linked to the same backend MSFT server(i.e. Activation is always linked
>> to the device)
>> Removing the MSA account does not remove the backend linkage to the
>> device. Windows 8/10/11 can all be reinstalled/clean installed 'from
>> scratch' since the device is digitally linked. A Microsoft account is
>> not necessary to reinstall/clean install Windows.
> 
> I'm confused. You say that Windows 8/10/11 can all be reinsalled/clean
> installed "from scratch' because they are digitally linked, but a MSA is
> not necessary to reinstall/clean install Windows.  That sounds
> contradictory.  What am I misunderstanding?
> 
> 
>>
>> The benefit of the MSA comes into play if the device has a major
>> hardware change(CPU, Motherboard),
> 
> I'm not one to swap out a CPU or motherboard, but I see that could be
> useful if one rebuilds/upgrades hardware.  Is there any advantage, to a
> user like me, to otherwise have a MSA?
> 
>>    - The MSA linkage to the backend server provides an additional feature
>> option in Windows Troubleshooting(that does not exist when an MSA-device
>> combo is not linked to the backend server). That MSA only available
>> Troubleshooter feature provides an easy option to reactivate the device
>> after a cpu/mobo change without extra steps *and without a product key
>> entry'
>>
> 


1. Windows with an MSA logon - device footprint is digitally linked and 
also linked to the MSA. The MSA linkage provides one single additional 
Troubleshooting option.
  - the additional troubleshooting option enables the user to activate 
Windows after and only after a major hardware change(CPU or motherboard)
or
2. Windows without an MSA logon but with a Local Account logon - device 
footprint is digital linked but without that additional Troubleshooting 
option

The device footprint's digital link is stored on the MSFT server for 
both(1 and/or 2).
  => the device footprint digital link is the only thing necessary to 
activate Windows and its license for use after a reinstall or clean install.
  -i.e. if the cpu or mobo is changed/replaced, that extra MSA only 
troubleshooting option provides a simple selectable feature to inform of 
the major hardware change and activate Windows after a reinstall/clean 
install and updates the device footprint linkage and licensing.  If no 
major hardware change, the existing device footprint(MSA or Local 
account) digital linkage is the only requirement necessary to 
reinstall/clean install Windows.


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

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

#16327

On Wed, 1/15/2025 8:06 PM, Boris wrote:
> Windows 11 Home, OEM installed on a Dell XPS 8950
> 
> When originally set up in September 2023, I was able to circumvent the 
> Microsoft email account requirement by entering "no@thanks.com", when asked 
> for a Microsoft account.  It worked.  I've never had a Microsoft account and 
> don't want one.
> 
> Today I had to use Dell's Support Assist OS Recovery software to reinstall 
> Windows 11.  (The machine would not boot after an update.)  I set it to save 
> my personal data.
> 
> Of course, I'm back at being asked for a Microsoft account email, which I 
> don't have.  I guess I could create an account, but I seem to remember that 
> if Microsoft sets up the machine, the user's default folder will be assigned 
> a cumbersome alpha-numeric-special character name, which can't be renamed.  
> Am I remembering correctly?
> 
> I'm searching for a remedy.  Does anyone know what the latest work-around is?
> 
> TIA
> 

To answer your immediate question. "Shift-F10" (or Shift-Fn-F10 on some laptops)
plus the "BypassNRO" command into the Command prompt window that pops to the front.
I keep getting these key sequences confused (as F10 is used for a few other things too).

https://www.elevenforum.com/t/bypass-microsoft-account-during-setup.22260/

    # See the "F10" reference here.

    https://www.elevenforum.com/t/clean-install-windows-11.99/

https://superuser.com/questions/1769167/how-to-pass-shift-f10-for-installing-windows-11-instead-of-opening-up-microsof

The file they are executing is here.

   C:\Windows\System32\oobe\BypassNRO.cmd   124 bytes

The contents of the file, are here. It causes a reboot and
a rerun of the OOBE setup.  The setup is restart-able.
This is sitting on my W11 C: drive right now. That's how
I can look it up when needed.

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

*******

Things I might try:

1) Do a full backup (in case a step goes badly).
   You can do an offline backup with a Macrium Rescue stick or DVD.
   if the backup software complains the C: needs a CHKDSK, you can
   use any WinPE media (Macrium or the Win11 installer DVD and the
   Troubleshooting and Command Prompt window) to execute a CHKDSK /f  C:

2) While booted from the Installer DVD, select Troubleshooting and
   then Command Prompt. This reverts the in-flight update file.
   When install media boots, it is the X: partition, and the C:
   partition should be your OS (on single-boot systems).

   DISM /image:c:\ /cleanup-image /revertpendingactions

   That can roll back an update that does not complete properly.
   I don't see why it would or could fix the boot, but you never
   know how clever the software is.

3) On Macrium Reflect Free rescue media, is a Boot Repair option in
   one of the menus. Attempt to repair the C: partition and the ESP
   it uses for booting. The tool will seek confirmation of which
   partition is which.

   While Windows itself has some repair routines it will run (three different
   sequences for three power failures), it's not particularly gifted at fixing stuff.
   Macrium is preferred for the first boot repair attempt, followed by the
   Windows one. Turning off power on SSDs is not the best thing for them,
   and that's why we have a backup from (1).

4) A Repair Install could be used, if you could get the OS started.
   A Clean Install does not preserve user files or programs, in the
   conventional sense. Installing a second C: drive (dual boot),
   does prevent damage to user files on the first C: drive. But the
   program installations won't be there. What Dell is doing, must be
   slightly different.

   On a 24H2, you can try the Shift-F10, as described above, after
   your Dell flavored installation progresses to OOBE registration dialog. .

Once the machine has had w10/W11 installed and the license key
registered with Microsoft, it does not need the license key
registered in the future. A license key could come in handy
if you are generating a Refurbisher Kit with Microsoft, as
an example of an out-of-band key exchange. But for the most part,
the license  key is handled electronically without your help.
when it asks for a key during installation, you answer "I don't have
a key" most of the time. If you were upgrading from Home to Pro
with an Upgrade Key, then yes, you enter the Upgrade key (at some
point). After an installation is finished, the logic will contact
Microsoft and finish the activation (by sending a hardware hash
to Microsoft, and the hash should match the previous one). If you
change motherboards, and install an OS, that would "disturb" the
hash and then your license key (written on that piece of paper),
just might come in handy.

   slmgr /dlv      # Dialog will say "licensed" if the job was done properly.

  Paul

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

#16336

On 2025-01-16 04:04, Paul wrote:
>
> To answer your immediate question. "Shift-F10" (or Shift-Fn-F10 on some laptops)
> plus the "BypassNRO" command into the Command prompt window that pops to the front.
> I keep getting these key sequences confused (as F10 is used for a few other things too).
> 
> https://www.elevenforum.com/t/bypass-microsoft-account-during-setup.22260/
> 
>      # See the "F10" reference here.
> 
>      https://www.elevenforum.com/t/clean-install-windows-11.99/
> 
> https://superuser.com/questions/1769167/how-to-pass-shift-f10-for-installing-windows-11-instead-of-opening-up-microsof
> 
> The file they are executing is here.
> 
>     C:\Windows\System32\oobe\BypassNRO.cmd   124 bytes
> 
> The contents of the file, are here. It causes a reboot and
> a rerun of the OOBE setup.  The setup is restart-able.
> This is sitting on my W11 C: drive right now. That's how
> I can look it up when needed.
> 
> @echo off
> reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
> shutdown /r /t 0

Would it work to install that key before upgrading from W10 to W11 while 
preserving your programs and files?

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#16348

On Thu, 1/16/2025 5:36 AM, Java Jive wrote:
> On 2025-01-16 04:04, Paul wrote:
>>
>> To answer your immediate question. "Shift-F10" (or Shift-Fn-F10 on some laptops)
>> plus the "BypassNRO" command into the Command prompt window that pops to the front.
>> I keep getting these key sequences confused (as F10 is used for a few other things too).
>>
>> https://www.elevenforum.com/t/bypass-microsoft-account-during-setup.22260/
>>
>>      # See the "F10" reference here.
>>
>>      https://www.elevenforum.com/t/clean-install-windows-11.99/
>>
>> https://superuser.com/questions/1769167/how-to-pass-shift-f10-for-installing-windows-11-instead-of-opening-up-microsof
>>
>> The file they are executing is here.
>>
>>     C:\Windows\System32\oobe\BypassNRO.cmd   124 bytes
>>
>> The contents of the file, are here. It causes a reboot and
>> a rerun of the OOBE setup.  The setup is restart-able.
>> This is sitting on my W11 C: drive right now. That's how
>> I can look it up when needed.
>>
>> @echo off
>> reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
>> shutdown /r /t 0
> 
> Would it work to install that key before upgrading from W10 to W11 while preserving your programs and files?
> 

Windows is moved to Windows.old, and the Registry is likely the
real Registry during the Migration phase. You could stop the process
somewhere in the middle and set that key.

But that's the problem I was having, is coming up with a way of setting
that key, when Regedit and a GUI isn't available. Kaspersky has a registry
editor on the rescue disc, but I don't know which version of Kav CD
is compatible with GPT systems. Kaspersky also made a claim that the
Registry Editor they use, is FOSS (Open Source), but I was never able
to locate where the item was developed. The Kaspersky Rescue Disc is
based on Gentoo as an OS, and the Registry Editor is running on top
of Gentoo in that case.

Otherwise, you're in for clumsy "hive loading" exercises. Notice
that the key in question is in "CurrentVersion", which means if you
do this exercise manually, it is up to you, the Wizard, to select the
correct actual version, to edit. That would be all part of the fun.

   Paul

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

#16360

On 2025-01-16 18:08, Paul wrote:
>
> On Thu, 1/16/2025 5:36 AM, Java Jive wrote:
>>
>> On 2025-01-16 04:04, Paul wrote:
>>>
>>> @echo off
>>> reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
>>> shutdown /r /t 0
>>
>> Would it work to install that key before upgrading from W10 to W11 while preserving your programs and files?
> 
> Windows is moved to Windows.old, and the Registry is likely the
> real Registry during the Migration phase. You could stop the process
> somewhere in the middle and set that key.
> 
> But that's the problem I was having, is coming up with a way of setting
> that key, when Regedit and a GUI isn't available. Kaspersky has a registry
> editor on the rescue disc, but I don't know which version of Kav CD
> is compatible with GPT systems. Kaspersky also made a claim that the
> Registry Editor they use, is FOSS (Open Source), but I was never able
> to locate where the item was developed. The Kaspersky Rescue Disc is
> based on Gentoo as an OS, and the Registry Editor is running on top
> of Gentoo in that case.
> 
> Otherwise, you're in for clumsy "hive loading" exercises. Notice
> that the key in question is in "CurrentVersion", which means if you
> do this exercise manually, it is up to you, the Wizard, to select the
> correct actual version, to edit. That would be all part of the fun.

By the above I presume that you mean that the registry used during the 
upgrade  -  the "real registry"  -  is an out-of-the-box Win 11 core or 
rump registry running during the PE phase?  I think that's what you must 
mean as, if so, then all the above makes perfect sense, whereas 
otherwise I'd be confused, because, when upgrading in place from Win 10 
to Win 11, most of the old 10 registry must be carried over into or as 
the new 11 one, otherwise you'd lose all the settings for all the 
non-Windows software.  I've noticed that even some Windows settings seem 
to make it through in-place upgrades, though sadly not enough to save 
most of the customisations so painstakingly done on the old version of 
Windows, thus maddeningly forcing one to redo them all over again :-(

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#16364

Java Jive <java@evij.com.invalid> wrote:
[...]

> By the above I presume that you mean that the registry used during the 
> upgrade  -  the "real registry"  -  is an out-of-the-box Win 11 core or 
> rump registry running during the PE phase?  I think that's what you must 
> mean as, if so, then all the above makes perfect sense, whereas 
> otherwise I'd be confused, because, when upgrading in place from Win 10 
> to Win 11, most of the old 10 registry must be carried over into or as 
> the new 11 one, otherwise you'd lose all the settings for all the 
> non-Windows software.  I've noticed that even some Windows settings seem 
> to make it through in-place upgrades, though sadly not enough to save 
> most of the customisations so painstakingly done on the old version of 
> Windows, thus maddeningly forcing one to redo them all over again :-(

  As far as I call tell, Paul was talking about a fresh install (of
Windows 11), not about an upgrade from Windows 10 to 11, i.e. your
question.

  The 'OOBE' (Out Of Box Experience) aspect obviously does not apply to
an upgrade, because the thing is already Out Of Box for a long, long
time.

  That said, I can not imagine that a Microsoft account is forced during
a 10->11 upgrade. At least it wasn't during the 8.1->10 upgrade of my
wife's system, while (AFAIK) for a 10 fresh install, a Microsoft Account
was also (somewhat) forced.

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

#16365

On Fri, 1/17/2025 11:13 AM, Frank Slootweg wrote:
> Java Jive <java@evij.com.invalid> wrote:
> [...]
> 
>> By the above I presume that you mean that the registry used during the 
>> upgrade  -  the "real registry"  -  is an out-of-the-box Win 11 core or 
>> rump registry running during the PE phase?  I think that's what you must 
>> mean as, if so, then all the above makes perfect sense, whereas 
>> otherwise I'd be confused, because, when upgrading in place from Win 10 
>> to Win 11, most of the old 10 registry must be carried over into or as 
>> the new 11 one, otherwise you'd lose all the settings for all the 
>> non-Windows software.  I've noticed that even some Windows settings seem 
>> to make it through in-place upgrades, though sadly not enough to save 
>> most of the customisations so painstakingly done on the old version of 
>> Windows, thus maddeningly forcing one to redo them all over again :-(
> 
>   As far as I call tell, Paul was talking about a fresh install (of
> Windows 11), not about an upgrade from Windows 10 to 11, i.e. your
> question.
> 
>   The 'OOBE' (Out Of Box Experience) aspect obviously does not apply to
> an upgrade, because the thing is already Out Of Box for a long, long
> time.
> 
>   That said, I can not imagine that a Microsoft account is forced during
> a 10->11 upgrade. At least it wasn't during the 8.1->10 upgrade of my
> wife's system, while (AFAIK) for a 10 fresh install, a Microsoft Account
> was also (somewhat) forced.
> 

Well, this is largely a theoretical exercise we're talking about
here. I was only thinking out loud, how I was trying to do it here,
as a test case. And I was mainly doing the exercise, in the
interest of seeing if there was an "easy" way to get that done,
if the shift-F10 did not work. I gave up on my install effort and
dumped the VM I was working in.

Using Rufus as materials, remains the best way for users to migrate
their stuff. The Shift-F10, I used that previously and it took a
number of tries before I got the details right. But at least the
materials survive retries, so you can just keep bashing at it :-)

   Paul

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

#16328

On 1/15/2025 8:06 PM, Boris wrote:
> Windows 11 Home, OEM installed on a Dell XPS 8950
> 
> When originally set up in September 2023, I was able to circumvent the
> Microsoft email account requirement by entering "no@thanks.com", when asked
> for a Microsoft account.  It worked.  I've never had a Microsoft account and
> don't want one.
> 
> Today I had to use Dell's Support Assist OS Recovery software to reinstall
> Windows 11.  (The machine would not boot after an update.)  I set it to save
> my personal data.
> 
> Of course, I'm back at being asked for a Microsoft account email, which I
> don't have.  I guess I could create an account, but I seem to remember that
> if Microsoft sets up the machine, the user's default folder will be assigned
> a cumbersome alpha-numeric-special character name, which can't be renamed.
> Am I remembering correctly?
> 
> I'm searching for a remedy.  Does anyone know what the latest work-around is?
> 

   I installed it last week with no problems. I unplugged the ethernet
and told it I have no Internet. I was updating from 10, so I'm not
completely certain about a fresh install. But in my case it didn't
require an MS account.

    It may be that a Rufus-written ISO also bypasses it. It does provide
several options.

    It's possible that the Dell rstore is cooperating with MS, in which
case maybe you could just overwrite that?

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

#16329

On 1/15/2025 11:08 PM, Newyana2 wrote:

As I thought, see here:

https://www.howtogeek.com/836157/how-to-use-windows-11-with-a-local-account/

   Scroll down to the Rufus option. But there is one catch with
that: You'll need to figure out what hardware you have and
get drivers. Dell is a pain that way. They like to get the drivers
and put them into their own package. You may need something
like CPUID to fund out exactly what the motherboard, graphics,
etc are. Maybe save a copy of your restore partition to be on
the safe side.

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

#16341

On Wed, 1/15/2025 11:13 PM, Newyana2 wrote:
> On 1/15/2025 11:08 PM, Newyana2 wrote:
> 
> As I thought, see here:
> 
> https://www.howtogeek.com/836157/how-to-use-windows-11-with-a-local-account/
> 
>   Scroll down to the Rufus option. But there is one catch with
> that: You'll need to figure out what hardware you have and
> get drivers. Dell is a pain that way. They like to get the drivers
> and put them into their own package. You may need something
> like CPUID to fund out exactly what the motherboard, graphics,
> etc are. Maybe save a copy of your restore partition to be on
> the safe side.

During WinPE, the screen is driven by the Microsoft Basic Display Adapter
driver. The resolution is 1024x768. On some monitors, you might see
a distortion because the aspect ratio is not very close. Once the
OS is installed, on the second reboot you might see "searching for display driver"
as it goes to the Internet and gets the correct graphics driver to
replace MBDA.

The SATA driver could be MSAHCI.

There are a couple Intel RAID drivers.

There will be other drivers which are missing,
but even a thing like a PERC, if you were running
the Server Edition it might have a PERC for you.
when installing WinXP, you might remember the names of
RAID controllers streaming by on the screen, as
Windows "tried on different pairs of shoes" :-)

Microsoft should have a USB driver, like a USBport.inf .
It could be an XHCI driver. There is an EHCI and an OHCI
driver as well.

Where the media will wobble a bit, is NIC drivers. Intel
has been on a bit of a spree, and it is possible there could
be NICs or Wifi which are not on your DVD. On brand new motherboards,
this is why I keep my USB3 ASIX GbE NIC adapter handy. Plug that in
and the Microsoft DVDs have the ASIX NDIS driver for that. And boom,
you have the Internetz.

The driver situation has improved a bit since WinXP.

You don't absolutely need all the drivers, during install.
You need enough to tip the OS upright, plus a means
to download the rest.

The chipset driver for my X79 PCH are no longer in the
Microsoft catalog, but fortunately I found the Patsburg
file I needed on the Intel site (after enough Googling).
These are not "essential" drivers -- they inject the correct
text strings for the System section of Device Manager.
They're not "tipping upright" materials, and are
merely cosmetic. But when missing, annoying nonetheless.

When snarfing drivers and building a driver tree, things
like "bridges" follow standards, so for example, a single
driver can be used for the snakes and ladders of one
of the bus types. These are built-ins, and are table
stakes for any OS that thinks it can install on
arbitrary hardware. We don't usually discuss these things,
but they're essential, and by following standards,
are practically invisible today.

   Paul

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

#16345

On 1/16/2025 9:19 AM, Paul wrote:
> On Wed, 1/15/2025 11:13 PM, Newyana2 wrote:
>> On 1/15/2025 11:08 PM, Newyana2 wrote:
>>
>> As I thought, see here:
>>
>> https://www.howtogeek.com/836157/how-to-use-windows-11-with-a-local-account/
>>
>>    Scroll down to the Rufus option. But there is one catch with
>> that: You'll need to figure out what hardware you have and
>> get drivers. Dell is a pain that way. They like to get the drivers
>> and put them into their own package. You may need something
>> like CPUID to fund out exactly what the motherboard, graphics,
>> etc are. Maybe save a copy of your restore partition to be on
>> the safe side.
> 
> During WinPE, the screen is driven by the Microsoft Basic Display Adapter
> driver. The resolution is 1024x768. On some monitors, you might see
> a distortion because the aspect ratio is not very close. Once the
> OS is installed, on the second reboot you might see "searching for display driver"
> as it goes to the Internet and gets the correct graphics driver to
> replace MBDA.
> 
> The SATA driver could be MSAHCI.
> 
> There are a couple Intel RAID drivers.
> 
> There will be other drivers which are missing,
> but even a thing like a PERC, if you were running
> the Server Edition it might have a PERC for you.
> when installing WinXP, you might remember the names of
> RAID controllers streaming by on the screen, as
> Windows "tried on different pairs of shoes" :-)
> 
> Microsoft should have a USB driver, like a USBport.inf .
> It could be an XHCI driver. There is an EHCI and an OHCI
> driver as well.
> 
> Where the media will wobble a bit, is NIC drivers. Intel
> has been on a bit of a spree, and it is possible there could
> be NICs or Wifi which are not on your DVD. On brand new motherboards,
> this is why I keep my USB3 ASIX GbE NIC adapter handy. Plug that in
> and the Microsoft DVDs have the ASIX NDIS driver for that. And boom,
> you have the Internetz.
> 
> The driver situation has improved a bit since WinXP.
> 
> You don't absolutely need all the drivers, during install.
> You need enough to tip the OS upright, plus a means
> to download the rest.
> 
> The chipset driver for my X79 PCH are no longer in the
> Microsoft catalog, but fortunately I found the Patsburg
> file I needed on the Intel site (after enough Googling).
> These are not "essential" drivers -- they inject the correct
> text strings for the System section of Device Manager.
> They're not "tipping upright" materials, and are
> merely cosmetic. But when missing, annoying nonetheless.
> 
> When snarfing drivers and building a driver tree, things
> like "bridges" follow standards, so for example, a single
> driver can be used for the snakes and ladders of one
> of the bus types. These are built-ins, and are table
> stakes for any OS that thinks it can install on
> arbitrary hardware. We don't usually discuss these things,
> but they're essential, and by following standards,
> are practically invisible today.
> 

   I wasn't thinking of problems with drivers in general. I just
meant that it could be tricky finding drivers for a Dell with
generic Windows, because Dell likes to make their own driver
installers, based on PC model rather than the hardware. So,
for example, if you need an audio driver for an XPS 2000
(if that exists) then you go to Dell and download a Dell
installer that gives no indication of what audio chip you
have.

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

#16349

On Thu, 1/16/2025 11:13 AM, Newyana2 wrote:

> 
>   I wasn't thinking of problems with drivers in general. I just
> meant that it could be tricky finding drivers for a Dell with
> generic Windows, because Dell likes to make their own driver
> installers, based on PC model rather than the hardware. So,
> for example, if you need an audio driver for an XPS 2000
> (if that exists) then you go to Dell and download a Dell
> installer that gives no indication of what audio chip you
> have.

You're right, there's no question that some of the Dell
stuff is nasty. A number of people had trouble with audio
on Dell, and the way things are lashed together, is
not particularly standard. And Googling is not leading
anywhere productive. If a manufacturer finds a novel
way to implement stuff, that's not actually helping
a customer in any significant way. It's a purpose-less
tech push thing.

As for a Dell SPxxxxx.exe , you can burrow into those
with 7Zip and find an INF with the PNP numbers. You can decode
a bit of the details of what is in there. But if a sound
driver is 300MB, you would suspect every computer that Dell
ever manufactured is in that file. Leaving little ability to
determine what sound chip is in your particular laptop (based
on the driver offered).

   Paul

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

#16361

On 2025-01-16 18:14, Paul wrote:
>
> On Thu, 1/16/2025 11:13 AM, Newyana2 wrote:
>>
>>    I wasn't thinking of problems with drivers in general. I just
>> meant that it could be tricky finding drivers for a Dell with
>> generic Windows, because Dell likes to make their own driver
>> installers, based on PC model rather than the hardware. So,
>> for example, if you need an audio driver for an XPS 2000
>> (if that exists) then you go to Dell and download a Dell
>> installer that gives no indication of what audio chip you
>> have.
> 
> You're right, there's no question that some of the Dell
> stuff is nasty. A number of people had trouble with audio
> on Dell, and the way things are lashed together, is
> not particularly standard. And Googling is not leading
> anywhere productive. If a manufacturer finds a novel
> way to implement stuff, that's not actually helping
> a customer in any significant way. It's a purpose-less
> tech push thing.
> 
> As for a Dell SPxxxxx.exe , you can burrow into those
> with 7Zip and find an INF with the PNP numbers. You can decode
> a bit of the details of what is in there. But if a sound
> driver is 300MB, you would suspect every computer that Dell
> ever manufactured is in that file. Leaving little ability to
> determine what sound chip is in your particular laptop (based
> on the driver offered).

I do not remember any problems with audio on Dell hardware, but perhaps 
you both are referring to desktops, whereas I'm actually quite fond of 
Dell laptops as hardware, having mostly, but certainly not exclusively, 
good experiences with them.  I'm currently using second-hand/used 
Precision M67/800s as my main PCs, previously I used an Inspiron 15RSE 
7520 and Precision M6300s.  All have been more or less fine as laptops, 
but the older machines were a PITA to upgrade or repair compared to the 
more recent machines.  By contrast, a Precision M4300 (note the single 
digit difference in model number) was a terrible machine, a really junk 
design.

However, your point mostly seemed concerned with drivers, and I would 
agree that, like the confusing model naming and numbering, their support 
pages for downloading drivers and their naming of them are confusing 
also.  As if navigating the page itself wasn't bad enough, by default if 
you choose the 'Download all selected' option, you end up with a 
directory full of meaningless names for the self-extracting downloads. 
WTF is 'R186621.exe'?  You either have to run it to find out, or do as I 
do and sit and sweat downloading each file individually, renaming them 
as you go, so the above becomes 'R186621 TouchPad.exe' and given that it 
is in the directory '\Install\Dell\Precision M6300\Windows 7' on my 
server, I know exactly what it is.  However, the whole rigmarole is a 
PITA to do whenever you get another model of machine or upgrade the OS 
on an existing one.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#16366

On Fri, 1/17/2025 8:49 AM, Java Jive wrote:
> On 2025-01-16 18:14, Paul wrote:
>>
>> On Thu, 1/16/2025 11:13 AM, Newyana2 wrote:
>>>
>>>    I wasn't thinking of problems with drivers in general. I just
>>> meant that it could be tricky finding drivers for a Dell with
>>> generic Windows, because Dell likes to make their own driver
>>> installers, based on PC model rather than the hardware. So,
>>> for example, if you need an audio driver for an XPS 2000
>>> (if that exists) then you go to Dell and download a Dell
>>> installer that gives no indication of what audio chip you
>>> have.
>>
>> You're right, there's no question that some of the Dell
>> stuff is nasty. A number of people had trouble with audio
>> on Dell, and the way things are lashed together, is
>> not particularly standard. And Googling is not leading
>> anywhere productive. If a manufacturer finds a novel
>> way to implement stuff, that's not actually helping
>> a customer in any significant way. It's a purpose-less
>> tech push thing.
>>
>> As for a Dell SPxxxxx.exe , you can burrow into those
>> with 7Zip and find an INF with the PNP numbers. You can decode
>> a bit of the details of what is in there. But if a sound
>> driver is 300MB, you would suspect every computer that Dell
>> ever manufactured is in that file. Leaving little ability to
>> determine what sound chip is in your particular laptop (based
>> on the driver offered).
> 
> I do not remember any problems with audio on Dell hardware, but perhaps you both are referring to desktops, whereas I'm actually quite fond of Dell laptops as hardware, having mostly, but certainly not exclusively, good experiences with them.  I'm currently using second-hand/used Precision M67/800s as my main PCs, previously I used an Inspiron 15RSE 7520 and Precision M6300s.  All have been more or less fine as laptops, but the older machines were a PITA to upgrade or repair compared to the more recent machines.  By contrast, a Precision M4300 (note the single digit difference in model number) was a terrible machine, a really junk design.
> 
> However, your point mostly seemed concerned with drivers, and I would agree that, like the confusing model naming and numbering, their support pages for downloading drivers and their naming of them are confusing also.  As if navigating the page itself wasn't bad enough, by default if you choose the 'Download all selected' option, you end up with a directory full of meaningless names for the self-extracting downloads. WTF is 'R186621.exe'?  You either have to run it to find out, or do as I do and sit and sweat downloading each file individually, renaming them as you go, so the above becomes 'R186621 TouchPad.exe' and given that it is in the directory '\Install\Dell\Precision M6300\Windows 7' on my server, I know exactly what it is.  However, the whole rigmarole is a PITA to do whenever you get another model of machine or upgrade the OS on an existing one.
> 

Some of the Dells have Class D digital speakers in the laptop, and
the Class D digital speaker has a DSP inside, with firmware that
loads over SPI. Now, as a "science experiment", that's just wonderful.
What are you running, a disco ball ?

The other problem with a couple of generations of those machines,
is the sound detection can go wrong for the RealTek. Microsoft can
install a Generic driver, in place of your specific Dell driver package.
With Microsoft sticking their big elephant feet into the picture,
your sound is in for a ride. Microsoft apparently don't like the
last generation ReakTek audio, because it likely was putting too much
junk at kernel level.

I've just seen some complaints in threads.

As for my own audio, my Test Machine, the RealTek sound ha Dolby DTS
complete with a logo. The generic Microsoft driver removed that.

As long as there are "competing solutions" battling for control
inside your machine, the end-user is just along for the ride.

David's sound is still "clicking" on his Dell, and I could not
figure out how best to help. I don't really think it is broken,
but it is most likely broken by driver issues.

There was a happy time, when HDAudio detection was simple, the laptop
speaker amps were passive 2 watt things with no DSP, no firmware,
and no "speakers are available" status bit. It's a laptop,
sound is meant to suck on it. It's not a 500W Marantz 7.1 .

   Paul

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

#16330

Boris <nospam@invalid.com> wrote in news:vm9m3c$36gm7$1@dont-email.me:

> Windows 11 Home, OEM installed on a Dell XPS 8950
> 
> When originally set up in September 2023, I was able to circumvent the 
> Microsoft email account requirement by entering "no@thanks.com", when
> asked for a Microsoft account.  It worked.  I've never had a Microsoft
> account and don't want one.
> 
> Today I had to use Dell's Support Assist OS Recovery software to
> reinstall Windows 11.  (The machine would not boot after an update.)  I
> set it to save my personal data.
> 
> Of course, I'm back at being asked for a Microsoft account email, which
> I don't have.  I guess I could create an account, but I seem to remember
> that if Microsoft sets up the machine, the user's default folder will be
> assigned a cumbersome alpha-numeric-special character name, which can't
> be renamed.  Am I remembering correctly?
> 
> I'm searching for a remedy.  Does anyone know what the latest
> work-around is? 
> 
> TIA

Well, flushing ipconfig, as described here, worked:
https://www.tomshardware.com/how-to/install-windows-11-without-microsoft-
ac
count 

Now I have to do a "Retrieve files" from the backup folders that Dell
SupportAssist OS Recovery Assistant made to my external USB Western
Digital MyPassport drive.  Those folders are: Desktop, Documents,
Downloads, Music, Pictures, and Videos. 

Selected files: 136.41 GB
Destination:  400.35 GB

File is "D:\SupportAssist_Backups\2025-01-14_22.30.39\archive.zip"

Hmmm...backup destination was originally E:, not D: 
guess a drive name was deleted

It took 10 hours to move the folders out to the backup drive.  I wonder
how long it will take to retrieve them. 

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

Page 1 of 3  [1] 2 3  Next page →

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

csiph-web