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

Groups > alt.comp.os.windows-10 > #182218 > unrolled thread

How to boot into Windows 10 Safe Mode

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

Contents

  How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-12 05:51 -0800
    Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-12 06:03 -0800
    Re: How to boot into Windows 10 Safe Mode "Allan Higdon" <allanh@vivaldi.net> - 2025-02-12 08:06 -0600
      Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-12 06:16 -0800
        Re: How to boot into Windows 10 Safe Mode "Allan Higdon" <allanh@vivaldi.net> - 2025-02-12 08:55 -0600
        Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-16 14:02 +0000
          Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-16 06:26 -0800
            Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-16 15:36 +0000
              Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-16 19:15 +0000
                Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-16 13:51 -0800
                  Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-16 18:48 -0600
                    Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-17 05:08 -0800
                      Re: How to boot into Windows 10 Safe Mode Paul <nospam@needed.invalid> - 2025-02-19 01:39 -0500
                    Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-17 15:42 +0000
                Re: How to boot into Windows 10 Safe Mode Char Jackson <none@none.invalid> - 2025-02-16 20:48 -0600
                  Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-17 15:42 +0000
                    Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-17 12:11 -0600
                      Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-17 18:57 +0000
                        Re: How to boot into Windows 10 Safe Mode Char Jackson <none@none.invalid> - 2025-02-18 01:36 -0600
                          Re: How to boot into Windows 10 Safe Mode "Bill Bradshaw" <bradshaw@gci.net> - 2025-02-18 11:14 -0900
                    Re: How to boot into Windows 10 Safe Mode Char Jackson <none@none.invalid> - 2025-02-18 00:29 -0600
                      Re: How to boot into Windows 10 Safe Mode Mr Xi Ji Ping <ping@china.cn> - 2025-02-19 03:16 +0000
                      Re: How to boot into Windows 10 Safe Mode Paul <nospam@needed.invalid> - 2025-02-19 04:02 -0500
      Re: How to boot into Windows 10 Safe Mode "Alan K." <alan@invalid.com> - 2025-02-12 16:43 -0500
    Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-12 12:44 -0600
      Re: How to boot into Windows 10 Safe Mode "Allan Higdon" <allanh@vivaldi.net> - 2025-02-12 15:25 -0600
    Re: How to boot into Windows 10 Safe Mode Paul <nospam@needed.invalid> - 2025-02-12 19:16 -0500
      Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-13 05:18 -0800
    Re: How to boot into Windows 10 Safe Mode ant@zimage.comANT (Ant) - 2025-02-13 03:28 +0000
      Re: How to boot into Windows 10 Safe Mode Uncle Sam <uncle.sam@usa.com> - 2025-02-13 03:58 +0000
        Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-13 05:27 -0800
      Re: How to boot into Windows 10 Safe Mode Paul <nospam@needed.invalid> - 2025-02-13 03:01 -0500
    Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-15 08:48 -0600
      Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-15 08:56 -0600
        Re: How to boot into Windows 10 Safe Mode "Allan Higdon" <allanh@vivaldi.net> - 2025-02-16 09:34 -0600
          Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-16 12:27 -0600
            Re: How to boot into Windows 10 Safe Mode "Allan Higdon" <allanh@vivaldi.net> - 2025-02-16 15:29 -0600
              Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-16 18:45 -0600
                Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-17 16:06 +0000
                  Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-17 10:28 -0600
                    Re: How to boot into Windows 10 Safe Mode Frank Slootweg <this@ddress.is.invalid> - 2025-02-17 16:51 +0000
          Re: How to boot into Windows 10 Safe Mode Paul <nospam@needed.invalid> - 2025-02-16 20:01 -0500
      Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-15 09:40 -0600
        Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-16 06:32 -0800
          Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-16 12:30 -0600
            Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-16 13:56 -0800
              Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-16 18:46 -0600
                Re: How to boot into Windows 10 Safe Mode "John C." <r9jmg0@yahoo.com> - 2025-02-17 05:33 -0800
                  Re: How to boot into Windows 10 Safe Mode VanguardLH <V@nguard.LH> - 2025-02-17 10:15 -0600

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

#182218 — How to boot into Windows 10 Safe Mode

I decided that it would be a good idea to know how to do this, so I
looked it up and... my God... what an absolute clusterfuck.

Gone are the simple days of pressing F8 while starting your computer.
This is a history (according to CoPilot) of the process:

Windows 95/98/ME:

    Press F8: Restart your computer and repeatedly press the F8 key
right before the Windows logo appears.

    Select Safe Mode: Choose Safe Mode from the boot menu.

Windows 2000:

    Press F8: Similar to Windows 95/98/ME, restart your computer and
press F8 before the Windows logo appears.

    Select Safe Mode: Pick Safe Mode from the boot options.

Windows XP:

    Press F8: Restart and press F8 key before the Windows logo shows up.

    Select Safe Mode: Navigate to and select Safe Mode from the Advanced
Options menu.

Windows Vista and Windows 7:

    Press F8: Restart your computer, and before the Windows logo
appears, press F8.

    Select Safe Mode: Choose Safe Mode from the Advanced Boot Options menu.

Windows 8 and 8.1:

    Shift + Restart:

        Open the Charm Bar with Win + C.

        Click on Settings > Power while holding the Shift key, and
select Restart.

        Navigate to Troubleshoot > Advanced options > Startup Settings.

        Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
with Networking.

Windows 10:

    Shift + Restart:

        On the sign-in screen, press and hold the Shift key while
selecting Power > Restart.

        Navigate to Troubleshoot > Advanced options > Startup Settings.

        Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
with Networking.

    Settings:

        Go to Settings > Update & Security > Recovery.

        Under Advanced startup, click Restart now.

        Follow the same steps as above.

    System Configuration:

        Press Win + R, type msconfig, and press Enter.

        Go to the Boot tab and check Safe boot.

        Click Apply and then OK.

        Restart your computer.

Windows 11:

    Shift + Restart:

        On the sign-in screen, press and hold the Shift key while
selecting Power > Restart.

        Navigate to Troubleshoot > Advanced options > Startup Settings.

        Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
with Networking.

    Settings:

        Go to Settings > System > Recovery.

        Under Advanced startup, click Restart now.

        Follow the same steps as above.
______________________________________________________________________________

Hmmm....

-- 
John C.

[toc] | [next] | [standalone]

#182220

I wrote:
> I decided that it would be a good idea to know how to do this, so I
> looked it up and... my God... what an absolute clusterfuck.
> 
> Gone are the simple days of pressing F8 while starting your computer.
> This is a history (according to CoPilot) of the process:
> 
> Windows 95/98/ME:
> 
>     Press F8: Restart your computer and repeatedly press the F8 key
> right before the Windows logo appears.
> 
>     Select Safe Mode: Choose Safe Mode from the boot menu.
> 
> Windows 2000:
> 
>     Press F8: Similar to Windows 95/98/ME, restart your computer and
> press F8 before the Windows logo appears.
> 
>     Select Safe Mode: Pick Safe Mode from the boot options.
> 
> Windows XP:
> 
>     Press F8: Restart and press F8 key before the Windows logo shows up.
> 
>     Select Safe Mode: Navigate to and select Safe Mode from the Advanced
> Options menu.
> 
> Windows Vista and Windows 7:
> 
>     Press F8: Restart your computer, and before the Windows logo
> appears, press F8.
> 
>     Select Safe Mode: Choose Safe Mode from the Advanced Boot Options menu.
> 
> Windows 8 and 8.1:
> 
>     Shift + Restart:
> 
>         Open the Charm Bar with Win + C.
> 
>         Click on Settings > Power while holding the Shift key, and
> select Restart.
> 
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
> 
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
> 
> Windows 10:
> 
>     Shift + Restart:
> 
>         On the sign-in screen, press and hold the Shift key while
> selecting Power > Restart.
> 
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
> 
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
> 
>     Settings:
> 
>         Go to Settings > Update & Security > Recovery.
> 
>         Under Advanced startup, click Restart now.
> 
>         Follow the same steps as above.
> 
>     System Configuration:
> 
>         Press Win + R, type msconfig, and press Enter.
> 
>         Go to the Boot tab and check Safe boot.
> 
>         Click Apply and then OK.
> 
>         Restart your computer.
> 
> Windows 11:
> 
>     Shift + Restart:
> 
>         On the sign-in screen, press and hold the Shift key while
> selecting Power > Restart.
> 
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
> 
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
> 
>     Settings:
> 
>         Go to Settings > System > Recovery.
> 
>         Under Advanced startup, click Restart now.
> 
>         Follow the same steps as above.
> ______________________________________________________________________________
> 
> Hmmm....

And by the way, I want to add that it's idiocy like this that's slowly
choking off the world of computing for the general public. Many of my
friends and relatives no longer use their computers and several have
even gotten rid of them. "I just use my cell phone for what I need" is a
refrain I commonly hear.

Microsoft has completely lost touch with the fact that there's only so
much complexity that their end users will tolerate.

I myself, routinely have been spending well over an hour every morning
simply dealing with Windows 10 issues and attempting to make sense of
the OS. I'm rapidly nearing the end of that road.

IMO, the best way to use computers these days is to have two of them:
-an air-gapped one running, say, Windows 7, main data storage (screw th
"cloud") and all the programs a person likes. This one is for actually
getting things done.

-one with only absolutely necessary programs, as little data stored on
it as possible and running an updated current version of Windows OR an
Apple computer. This one would be for connecting to the internet and
getting your email.

Fuck Microsoft. They're a pack of assholes.

-- 
John C.

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

#182221

On Wed, 12 Feb 2025 07:51:24 -0600, John C. <r9jmg0@yahoo.com> wrote:

> I decided that it would be a good idea to know how to do this, so I
> looked it up and... my God... what an absolute clusterfuck.
>
> Gone are the simple days of pressing F8 while starting your computer.
> This is a history (according to CoPilot) of the process:
>
> Windows 95/98/ME:
>
>     Press F8: Restart your computer and repeatedly press the F8 key
> right before the Windows logo appears.
>
>     Select Safe Mode: Choose Safe Mode from the boot menu.
>
> Windows 2000:
>
>     Press F8: Similar to Windows 95/98/ME, restart your computer and
> press F8 before the Windows logo appears.
>
>     Select Safe Mode: Pick Safe Mode from the boot options.
>
> Windows XP:
>
>     Press F8: Restart and press F8 key before the Windows logo shows up.
>
>     Select Safe Mode: Navigate to and select Safe Mode from the Advanced
> Options menu.
>
> Windows Vista and Windows 7:
>
>     Press F8: Restart your computer, and before the Windows logo
> appears, press F8.
>
>     Select Safe Mode: Choose Safe Mode from the Advanced Boot Options menu.
>
> Windows 8 and 8.1:
>
>     Shift + Restart:
>
>         Open the Charm Bar with Win + C.
>
>         Click on Settings > Power while holding the Shift key, and
> select Restart.
>
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
>
> Windows 10:
>
>     Shift + Restart:
>
>         On the sign-in screen, press and hold the Shift key while
> selecting Power > Restart.
>
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
>
>     Settings:
>
>         Go to Settings > Update & Security > Recovery.
>
>         Under Advanced startup, click Restart now.
>
>         Follow the same steps as above.
>
>     System Configuration:
>
>         Press Win + R, type msconfig, and press Enter.
>
>         Go to the Boot tab and check Safe boot.
>
>         Click Apply and then OK.
>
>         Restart your computer.
>
> Windows 11:
>
>     Shift + Restart:
>
>         On the sign-in screen, press and hold the Shift key while
> selecting Power > Restart.
>
>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>
>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> with Networking.
>
>     Settings:
>
>         Go to Settings > System > Recovery.
>
>         Under Advanced startup, click Restart now.
>
>         Follow the same steps as above.
> ______________________________________________________________________________
>
> Hmmm....
>

This how I do it.
To enable Safe Mode, I use a batch file with these 2 lines.

bcdedit /set {default} safeboot minimal
shutdown /r /t 0

To disable Safe Mode and return to normal boot, I use a batch file with these 2 lines.

bcdedit /deletevalue {default} safeboot
shutdown /r /t 0

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

#182222

On 25/02/12 06:06 AM, Allan Higdon wrote:
> On Wed, 12 Feb 2025 07:51:24 -0600, John C. <r9jmg0@yahoo.com> wrote:
> 
>> I decided that it would be a good idea to know how to do this, so I
>> looked it up and... my God... what an absolute clusterfuck.
>>
>> Gone are the simple days of pressing F8 while starting your computer.
>> This is a history (according to CoPilot) of the process:
>>
>> Windows 95/98/ME:
>>
>>     Press F8: Restart your computer and repeatedly press the F8 key
>> right before the Windows logo appears.
>>
>>     Select Safe Mode: Choose Safe Mode from the boot menu.
>>
>> Windows 2000:
>>
>>     Press F8: Similar to Windows 95/98/ME, restart your computer and
>> press F8 before the Windows logo appears.
>>
>>     Select Safe Mode: Pick Safe Mode from the boot options.
>>
>> Windows XP:
>>
>>     Press F8: Restart and press F8 key before the Windows logo shows up.
>>
>>     Select Safe Mode: Navigate to and select Safe Mode from the Advanced
>> Options menu.
>>
>> Windows Vista and Windows 7:
>>
>>     Press F8: Restart your computer, and before the Windows logo
>> appears, press F8.
>>
>>     Select Safe Mode: Choose Safe Mode from the Advanced Boot Options
>> menu.
>>
>> Windows 8 and 8.1:
>>
>>     Shift + Restart:
>>
>>         Open the Charm Bar with Win + C.
>>
>>         Click on Settings > Power while holding the Shift key, and
>> select Restart.
>>
>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>
>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>> with Networking.
>>
>> Windows 10:
>>
>>     Shift + Restart:
>>
>>         On the sign-in screen, press and hold the Shift key while
>> selecting Power > Restart.
>>
>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>
>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>> with Networking.
>>
>>     Settings:
>>
>>         Go to Settings > Update & Security > Recovery.
>>
>>         Under Advanced startup, click Restart now.
>>
>>         Follow the same steps as above.
>>
>>     System Configuration:
>>
>>         Press Win + R, type msconfig, and press Enter.
>>
>>         Go to the Boot tab and check Safe boot.
>>
>>         Click Apply and then OK.
>>
>>         Restart your computer.
>>
>> Windows 11:
>>
>>     Shift + Restart:
>>
>>         On the sign-in screen, press and hold the Shift key while
>> selecting Power > Restart.
>>
>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>
>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>> with Networking.
>>
>>     Settings:
>>
>>         Go to Settings > System > Recovery.
>>
>>         Under Advanced startup, click Restart now.
>>
>>         Follow the same steps as above.
>> ______________________________________________________________________________
>>
>> Hmmm....
>>
> 
> This how I do it.
> To enable Safe Mode, I use a batch file with these 2 lines.
> 
> bcdedit /set {default} safeboot minimal
> shutdown /r /t 0
> 
> To disable Safe Mode and return to normal boot, I use a batch file with
> these 2 lines.
> 
> bcdedit /deletevalue {default} safeboot
> shutdown /r /t 0

Thanks for replying, Allan, but what about trying to get into Safe Mode
from a cold boot?

-- 
John C.

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

#182223

On Wed, 12 Feb 2025 08:16:38 -0600, John C. <r9jmg0@yahoo.com> wrote:

> On 25/02/12 06:06 AM, Allan Higdon wrote:
>> On Wed, 12 Feb 2025 07:51:24 -0600, John C. <r9jmg0@yahoo.com> wrote:
>>
>>> I decided that it would be a good idea to know how to do this, so I
>>> looked it up and... my God... what an absolute clusterfuck.
>>>
>>> Gone are the simple days of pressing F8 while starting your computer.
>>> This is a history (according to CoPilot) of the process:
>>>
>>> Windows 95/98/ME:
>>>
>>>     Press F8: Restart your computer and repeatedly press the F8 key
>>> right before the Windows logo appears.
>>>
>>>     Select Safe Mode: Choose Safe Mode from the boot menu.
>>>
>>> Windows 2000:
>>>
>>>     Press F8: Similar to Windows 95/98/ME, restart your computer and
>>> press F8 before the Windows logo appears.
>>>
>>>     Select Safe Mode: Pick Safe Mode from the boot options.
>>>
>>> Windows XP:
>>>
>>>     Press F8: Restart and press F8 key before the Windows logo shows up.
>>>
>>>     Select Safe Mode: Navigate to and select Safe Mode from the Advanced
>>> Options menu.
>>>
>>> Windows Vista and Windows 7:
>>>
>>>     Press F8: Restart your computer, and before the Windows logo
>>> appears, press F8.
>>>
>>>     Select Safe Mode: Choose Safe Mode from the Advanced Boot Options
>>> menu.
>>>
>>> Windows 8 and 8.1:
>>>
>>>     Shift + Restart:
>>>
>>>         Open the Charm Bar with Win + C.
>>>
>>>         Click on Settings > Power while holding the Shift key, and
>>> select Restart.
>>>
>>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>
>>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>> with Networking.
>>>
>>> Windows 10:
>>>
>>>     Shift + Restart:
>>>
>>>         On the sign-in screen, press and hold the Shift key while
>>> selecting Power > Restart.
>>>
>>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>
>>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>> with Networking.
>>>
>>>     Settings:
>>>
>>>         Go to Settings > Update & Security > Recovery.
>>>
>>>         Under Advanced startup, click Restart now.
>>>
>>>         Follow the same steps as above.
>>>
>>>     System Configuration:
>>>
>>>         Press Win + R, type msconfig, and press Enter.
>>>
>>>         Go to the Boot tab and check Safe boot.
>>>
>>>         Click Apply and then OK.
>>>
>>>         Restart your computer.
>>>
>>> Windows 11:
>>>
>>>     Shift + Restart:
>>>
>>>         On the sign-in screen, press and hold the Shift key while
>>> selecting Power > Restart.
>>>
>>>         Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>
>>>         Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>> with Networking.
>>>
>>>     Settings:
>>>
>>>         Go to Settings > System > Recovery.
>>>
>>>         Under Advanced startup, click Restart now.
>>>
>>>         Follow the same steps as above.
>>> ______________________________________________________________________________
>>>
>>> Hmmm....
>>>
>>
>> This how I do it.
>> To enable Safe Mode, I use a batch file with these 2 lines.
>>
>> bcdedit /set {default} safeboot minimal
>> shutdown /r /t 0
>>
>> To disable Safe Mode and return to normal boot, I use a batch file with
>> these 2 lines.
>>
>> bcdedit /deletevalue {default} safeboot
>> shutdown /r /t 0
>
> Thanks for replying, Allan, but what about trying to get into Safe Mode
> from a cold boot?
>

According to
https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b

Select "Automatic Repair"

"If Windows fails to start correctly multiple times, it will automatically enter Windows RE. This can happen if there are issues with the boot process or if the system detects a problem that prevents Windows from starting."

The "Startup Settings" option allows booting into Safe Mode.

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

#182328

John C. <r9jmg0@yahoo.com> wrote:
> On 25/02/12 06:06 AM, Allan Higdon wrote:
[...]
> > This how I do it.
> > To enable Safe Mode, I use a batch file with these 2 lines.
> > 
> > bcdedit /set {default} safeboot minimal
> > shutdown /r /t 0
> > 
> > To disable Safe Mode and return to normal boot, I use a batch file with
> > these 2 lines.
> > 
> > bcdedit /deletevalue {default} safeboot
> > shutdown /r /t 0
> 
> Thanks for replying, Allan, but what about trying to get into Safe Mode
> from a cold boot?

  Without any preparation, you can do:
  
  Cold boot while pressing the get-into-BIOS key (in my case, for HP
computers, the 'esc' key). This will give a BIOS Startup Menu which has
several choices, probably including 'F11 System Recovery' (or similar
wording), selecting that, will bring you in the UEFI part of your
computer, which gives the same as 'Navigate to Troubleshoot' in:

<you>
> >> Windows 10:
> >>
> >> Shift + Restart:
> >>
> >> On the sign-in screen, press and hold the Shift key while
> >> selecting Power > Restart.
> >>
> >> Navigate to Troubleshoot > Advanced options > Startup Settings.
> >>
> >> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> >> with Networking.
</you>

  I.e. in 'old'(er) computers it was simple because they only had the
BIOS, but they had limited functionality. In 'new'(er) computers, it's
more complicated, because the UEFI (and its (sort-of) legacy BIOS) has
much, much more functionality.

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

#182330

On 25/02/16 06:02 AM, Frank Slootweg wrote:
> John C. <r9jmg0@yahoo.com> wrote:
>> On 25/02/12 06:06 AM, Allan Higdon wrote:
> [...]
>>> This how I do it.
>>> To enable Safe Mode, I use a batch file with these 2 lines.
>>>
>>> bcdedit /set {default} safeboot minimal
>>> shutdown /r /t 0
>>>
>>> To disable Safe Mode and return to normal boot, I use a batch file with
>>> these 2 lines.
>>>
>>> bcdedit /deletevalue {default} safeboot
>>> shutdown /r /t 0
>>
>> Thanks for replying, Allan, but what about trying to get into Safe Mode
>> from a cold boot?
> 
>   Without any preparation, you can do:
>   
>   Cold boot while pressing the get-into-BIOS key (in my case, for HP
> computers, the 'esc' key). This will give a BIOS Startup Menu which has
> several choices, probably including 'F11 System Recovery' (or similar
> wording), selecting that, will bring you in the UEFI part of your
> computer, which gives the same as 'Navigate to Troubleshoot' in:
> 
> <you>
>>>> Windows 10:
>>>>
>>>> Shift + Restart:
>>>>
>>>> On the sign-in screen, press and hold the Shift key while
>>>> selecting Power > Restart.
>>>>
>>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>>
>>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>>> with Networking.
> </you>
> 
>   I.e. in 'old'(er) computers it was simple because they only had the
> BIOS, but they had limited functionality. In 'new'(er) computers, it's
> more complicated, because the UEFI (and its (sort-of) legacy BIOS) has
> much, much more functionality.

Thanks for this info, Frank. However, my desktop dates back to *ahem*
*cough* about 2010. No UEFI.

-- 
John C.

Take back Microsoft from India.

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

#182336

John C. <r9jmg0@yahoo.com> wrote:
> On 25/02/16 06:02 AM, Frank Slootweg wrote:
[...]
> Thanks for this info, Frank. However, my desktop dates back to *ahem*
> *cough* about 2010. No UEFI.

  Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
and by 2007 already had its third spec (version 2.0). UEFI can be quite
'invisible if you don't know it's there and don't know how to enter it.

  An easy way to tell one or the other is just try the recipe you
posted:

> > <you>
> >>>> Windows 10:
> >>>>
> >>>> Shift + Restart:
> >>>>
> >>>> On the sign-in screen, press and hold the Shift key while
> >>>> selecting Power > Restart.
> >>>>
> >>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
> >>>>
> >>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> >>>> with Networking.
> > </you>

  If where it says 'Navigate to Troubleshoot' you get a screen labeled
'Choose an option' which includes the mentioned 'Troubleshoot' option,
you *do* have UEFI.

  Alternatively, you can use Computer Management -> Storage -> Disk
Management. If that lists an 'EFI' partition, you have UEFI.

  Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
the top bar.

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

#182347

Earlier today, I wrote:
> John C. <r9jmg0@yahoo.com> wrote:
> > On 25/02/16 06:02 AM, Frank Slootweg wrote:
> [...]
> > Thanks for this info, Frank. However, my desktop dates back to *ahem*
> > *cough* about 2010. No UEFI.
> 
>   Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
> and by 2007 already had its third spec (version 2.0). UEFI can be quite
> 'invisible if you don't know it's there and don't know how to enter it.
> 
>   An easy way to tell one or the other is just try the recipe you
> posted:
> 
> > > <you>
> > >>>> Windows 10:
> > >>>>
> > >>>> Shift + Restart:
> > >>>>
> > >>>> On the sign-in screen, press and hold the Shift key while
> > >>>> selecting Power > Restart.
> > >>>>
> > >>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
> > >>>>
> > >>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
> > >>>> with Networking.
> > > </you>
> 
>   If where it says 'Navigate to Troubleshoot' you get a screen labeled
> 'Choose an option' which includes the mentioned 'Troubleshoot' option,
> you *do* have UEFI.
> 
>   Alternatively, you can use Computer Management -> Storage -> Disk
> Management. If that lists an 'EFI' partition, you have UEFI.
> 
>   Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
> the top bar.

  Yet another method mentioned by VanguardLH elsewhere in this thread:

  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
(without options/arguments). That will say 'efi' (ignore case), in
several places, if you have an UEFI system.

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

#182351

On 25/02/16 11:15 AM, Frank Slootweg wrote:
> Earlier today, I wrote:
>> John C. <r9jmg0@yahoo.com> wrote:
>>> On 25/02/16 06:02 AM, Frank Slootweg wrote:
>> [...]
>>> Thanks for this info, Frank. However, my desktop dates back to *ahem*
>>> *cough* about 2010. No UEFI.
>>
>>   Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
>> and by 2007 already had its third spec (version 2.0). UEFI can be quite
>> 'invisible if you don't know it's there and don't know how to enter it.
>>
>>   An easy way to tell one or the other is just try the recipe you
>> posted:
>>
>>>> <you>
>>>>>>> Windows 10:
>>>>>>>
>>>>>>> Shift + Restart:
>>>>>>>
>>>>>>> On the sign-in screen, press and hold the Shift key while
>>>>>>> selecting Power > Restart.
>>>>>>>
>>>>>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>>>>>
>>>>>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>>>>>> with Networking.
>>>> </you>
>>
>>   If where it says 'Navigate to Troubleshoot' you get a screen labeled
>> 'Choose an option' which includes the mentioned 'Troubleshoot' option,
>> you *do* have UEFI.
>>
>>   Alternatively, you can use Computer Management -> Storage -> Disk
>> Management. If that lists an 'EFI' partition, you have UEFI.
>>
>>   Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
>> the top bar.
> 
>   Yet another method mentioned by VanguardLH elsewhere in this thread:
> 
>   In a 'Run as administrator' Command Prompt window, run 'bcdedit'
> (without options/arguments). That will say 'efi' (ignore case), in
> several places, if you have an UEFI system.

Thanks for the info, Frank. I tried Disk Management and there's no
lsting of an efi partition.

Ran bcdedit at a command prompt, and no mention of efi.

System was purchased on June 25, 2011.

-- 
John C.

Take back Microsoft from India.

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

#182363

"John C." <r9jmg0@yahoo.com> wrote:

> On 25/02/16 11:15 AM, Frank Slootweg wrote:
>> Earlier today, I wrote:
>>> John C. <r9jmg0@yahoo.com> wrote:
>>>> On 25/02/16 06:02 AM, Frank Slootweg wrote:
>>> [...]
>>>> Thanks for this info, Frank. However, my desktop dates back to *ahem*
>>>> *cough* about 2010. No UEFI.
>>>
>>>   Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
>>> and by 2007 already had its third spec (version 2.0). UEFI can be quite
>>> 'invisible if you don't know it's there and don't know how to enter it.
>>>
>>>   An easy way to tell one or the other is just try the recipe you
>>> posted:
>>>
>>>>> <you>
>>>>>>>> Windows 10:
>>>>>>>>
>>>>>>>> Shift + Restart:
>>>>>>>>
>>>>>>>> On the sign-in screen, press and hold the Shift key while
>>>>>>>> selecting Power > Restart.
>>>>>>>>
>>>>>>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>>>>>>
>>>>>>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>>>>>>> with Networking.
>>>>> </you>
>>>
>>>   If where it says 'Navigate to Troubleshoot' you get a screen labeled
>>> 'Choose an option' which includes the mentioned 'Troubleshoot' option,
>>> you *do* have UEFI.
>>>
>>>   Alternatively, you can use Computer Management -> Storage -> Disk
>>> Management. If that lists an 'EFI' partition, you have UEFI.
>>>
>>>   Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
>>> the top bar.
>> 
>>   Yet another method mentioned by VanguardLH elsewhere in this thread:
>> 
>>   In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>> (without options/arguments). That will say 'efi' (ignore case), in
>> several places, if you have an UEFI system.
> 
> Thanks for the info, Frank. I tried Disk Management and there's no
> lsting of an efi partition.
> 
> Ran bcdedit at a command prompt, and no mention of efi.
> 
> System was purchased on June 25, 2011.

Just because UEFI got adopted by mobo makers doesn't mean sellers
weren't still selling their old MBR stock of mobos.  That was a
transition period.

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

#182374

On 25/02/16 04:48 PM, VanguardLH wrote:
> "John C." <r9jmg0@yahoo.com> wrote:
> 
>> On 25/02/16 11:15 AM, Frank Slootweg wrote:
>>> Earlier today, I wrote:
>>>> John C. <r9jmg0@yahoo.com> wrote:
>>>>> On 25/02/16 06:02 AM, Frank Slootweg wrote:
>>>> [...]
>>>>> Thanks for this info, Frank. However, my desktop dates back to *ahem*
>>>>> *cough* about 2010. No UEFI.
>>>>
>>>>   Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
>>>> and by 2007 already had its third spec (version 2.0). UEFI can be quite
>>>> 'invisible if you don't know it's there and don't know how to enter it.
>>>>
>>>>   An easy way to tell one or the other is just try the recipe you
>>>> posted:
>>>>
>>>>>> <you>
>>>>>>>>> Windows 10:
>>>>>>>>>
>>>>>>>>> Shift + Restart:
>>>>>>>>>
>>>>>>>>> On the sign-in screen, press and hold the Shift key while
>>>>>>>>> selecting Power > Restart.
>>>>>>>>>
>>>>>>>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>>>>>>>
>>>>>>>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>>>>>>>> with Networking.
>>>>>> </you>
>>>>
>>>>   If where it says 'Navigate to Troubleshoot' you get a screen labeled
>>>> 'Choose an option' which includes the mentioned 'Troubleshoot' option,
>>>> you *do* have UEFI.
>>>>
>>>>   Alternatively, you can use Computer Management -> Storage -> Disk
>>>> Management. If that lists an 'EFI' partition, you have UEFI.
>>>>
>>>>   Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
>>>> the top bar.
>>>
>>>   Yet another method mentioned by VanguardLH elsewhere in this thread:
>>>
>>>   In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>>> (without options/arguments). That will say 'efi' (ignore case), in
>>> several places, if you have an UEFI system.
>>
>> Thanks for the info, Frank. I tried Disk Management and there's no
>> lsting of an efi partition.
>>
>> Ran bcdedit at a command prompt, and no mention of efi.
>>
>> System was purchased on June 25, 2011.
> 
> Just because UEFI got adopted by mobo makers doesn't mean sellers
> weren't still selling their old MBR stock of mobos.  That was a
> transition period.

Yeah, that's what I figured too. And the system was purchased at a
Costco store. It was given to me by a relative. Still a good computer
though IMO.

-- 
John C.

Take back Microsoft from India.

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

#182418

On Mon, 2/17/2025 8:08 AM, John C. wrote:
> On 25/02/16 04:48 PM, VanguardLH wrote:
>> "John C." <r9jmg0@yahoo.com> wrote:
>>
>>> On 25/02/16 11:15 AM, Frank Slootweg wrote:
>>>> Earlier today, I wrote:
>>>>> John C. <r9jmg0@yahoo.com> wrote:
>>>>>> On 25/02/16 06:02 AM, Frank Slootweg wrote:
>>>>> [...]
>>>>>> Thanks for this info, Frank. However, my desktop dates back to *ahem*
>>>>>> *cough* about 2010. No UEFI.
>>>>>
>>>>>   Are you sure that your desktop doesn't have UEFI? UEFI started in 2005
>>>>> and by 2007 already had its third spec (version 2.0). UEFI can be quite
>>>>> 'invisible if you don't know it's there and don't know how to enter it.
>>>>>
>>>>>   An easy way to tell one or the other is just try the recipe you
>>>>> posted:
>>>>>
>>>>>>> <you>
>>>>>>>>>> Windows 10:
>>>>>>>>>>
>>>>>>>>>> Shift + Restart:
>>>>>>>>>>
>>>>>>>>>> On the sign-in screen, press and hold the Shift key while
>>>>>>>>>> selecting Power > Restart.
>>>>>>>>>>
>>>>>>>>>> Navigate to Troubleshoot > Advanced options > Startup Settings.
>>>>>>>>>>
>>>>>>>>>> Click Restart and then choose 4 for Safe Mode or 5 for Safe Mode
>>>>>>>>>> with Networking.
>>>>>>> </you>
>>>>>
>>>>>   If where it says 'Navigate to Troubleshoot' you get a screen labeled
>>>>> 'Choose an option' which includes the mentioned 'Troubleshoot' option,
>>>>> you *do* have UEFI.
>>>>>
>>>>>   Alternatively, you can use Computer Management -> Storage -> Disk
>>>>> Management. If that lists an 'EFI' partition, you have UEFI.
>>>>>
>>>>>   Even simpler if you have Macrium Reflect, that will say '[EUFI]' on
>>>>> the top bar.
>>>>
>>>>   Yet another method mentioned by VanguardLH elsewhere in this thread:
>>>>
>>>>   In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>>>> (without options/arguments). That will say 'efi' (ignore case), in
>>>> several places, if you have an UEFI system.
>>>
>>> Thanks for the info, Frank. I tried Disk Management and there's no
>>> lsting of an efi partition.
>>>
>>> Ran bcdedit at a command prompt, and no mention of efi.
>>>
>>> System was purchased on June 25, 2011.
>>
>> Just because UEFI got adopted by mobo makers doesn't mean sellers
>> weren't still selling their old MBR stock of mobos.  That was a
>> transition period.
> 
> Yeah, that's what I figured too. And the system was purchased at a
> Costco store. It was given to me by a relative. Still a good computer
> though IMO.
> 

https://www.cpuid.com/softwares/cpu-z.html

     ZIP - English

If you run CPU-Z portable version, in the Mainboard tab, it does
not tell you whether the BIOS is one type or another.

However, the "About" tab on the top-right, has "Save Report (.TXT)"
and that has a lot more detail in it. For my DailyDriver, it says
for example:

   WALLACE.txt     <=== machine-name

BIOS

UEFI               Yes                      <=== not a lot of detail...
BIOS Vendor        American Megatrends Inc.
BIOS MSG           63-0100-000001-00101111-122418-Chipset
BIOS Date          12/24/18
Mainboard Vendor   000001
AMD AGESA          ComboAM4v2PI 1.2.0.Ca    <=== PCH stokes CPU at startup, with a bitstream

Then, elsewhere in the file, it claims a certain EEPROM size for the BIOS.
A legacy BIOS could be 128KB in size, so relatively cheap to build. The
DMI is the "decorative fluff" and any information here has no effect
on system operation, and the contents could be completely imaginary.

DMI

SMBIOS Version    2.8

DMI BIOS
   vendor         American Megatrends International LLC.
   version        1.I0
   date           07/13/2024
   ROM size       16384 KB    <===

One of the reasons a UEFI BIOS is so big, is 4MB of it (4096KB)
is set aside for "boot path memory". Every time you change-up disks
in the machine, the boot path is stored for some reason. Yet, caching
the boot path, doesn't particularly seem to "accelerate" anything.

This feature of UEFI is referred to as NVRAM (non volatile RAM)
even though it is really a flash memory. The 256 byte CMOS memory in the PCH
is also referred to as NVRAM, but it is the real NVRAM (battery powered
static RAM cells).

The BIOS must also "manage" this area. One BIOS design forgot the
need to "flush" the 4MB region when it gets to a certain fullness,
and the motherboard actually "jams up" when it runs out of boot path
storage space. There aren't many boards where that happened, but
it was a bit of a QA wakeup call for the people creating the
UEFI BIOS design.

A 128KB legacy BIOS motherboard, won't have 4096KB of NVRAM (NOR Flash)
to store such variables, so the BIOS chip from that perspective
has to be pretty big, to stand a chance of doing that.

It is quite normal for the BIOS to have "self-flashing capability".
That's been present since at least year 2000. In fact, some BIOS flashing
procedures, use the flash routine store in the BIOS, to flash the BIOS :-)
(Don't worry, the BIOS is shadowed in system RAM...)

Not all boards have replacement BIOS images, like an OEM board
could get by with just the initial BIOS images stored. However,
the Secure Boot bugs have required a certain amount of fixing,
so at least in the last two or three years, there's been an
uptick in the availability of replacement BIOS images. You have
to be fairly careful when decompressing one of those images,
to "re-inflate it to the correct size". Working with the BIOS
file from the manufacturer web site, is not easy, but given my
DMI is declaring one monster of a BIOS chip, I would want a
second opinion by using 7ZIP on the file.

Name: 7C56v1I1.zip
Size: 18216711 bytes (17 MiB)
SHA256: D7216262F760291AAE2FC275E6E0EAC974CFEF67467F09B7D5CF7B6F37356B74

It is kind of a monster :-) "Must be a UEFI", a fairly mild confirmation.
A regular BIOS simply does not need to be anywhere near that big.

When that file is unpacked, the size is 33554432. If that is a power-of-two
number, then that's how ROMs are sold, is power-of-two for NOR flash EEPROMS.

factor 33554432
33554432: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

It's actually 32MB! A hell of a lot bigger than a 128KB legacy BIOS.

   Paul

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

#182383

VanguardLH <V@nguard.lh> wrote:
[...]
> Just because UEFI got adopted by mobo makers doesn't mean sellers
> weren't still selling their old MBR stock of mobos.  That was a
> transition period.

  Yes, but 4 to 6 years [1] is quite a long time for such a transition
period.

[1] 2005/2007 to John's purchase in 2011.

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

#182367

On 16 Feb 2025 19:15:23 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:

>  Yet another method mentioned by VanguardLH elsewhere in this thread:
>
>  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>(without options/arguments). That will say 'efi' (ignore case), in
>several places, if you have an UEFI system.

Or not. My home-built PC uses UEFI but the output of bcdedit doesn't
mention "efi" anywhere.

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

#182382

Char Jackson <none@none.invalid> wrote:
> On 16 Feb 2025 19:15:23 GMT, Frank Slootweg <this@ddress.is.invalid>
> wrote:
> 
> >  Yet another method mentioned by VanguardLH elsewhere in this thread:
> >
> >  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
> >(without options/arguments). That will say 'efi' (ignore case), in
> >several places, if you have an UEFI system.
> 
> Or not. My home-built PC uses UEFI but the output of bcdedit doesn't
> mention "efi" anywhere.

  Hmmm!? On my (HP) system, the Windows Boot Manager and Windows Boot
Loader 'path' names end in '.efi'.

  What about Disk Management, does that list an 'EFI' partition?

  N.B. I have only HP systems, so I'd be interested if (some of) these
things are HP-specific.

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

#182392

Frank Slootweg <this@ddress.is.invalid> wrote:

> Char Jackson <none@none.invalid> wrote:
>> On 16 Feb 2025 19:15:23 GMT, Frank Slootweg <this@ddress.is.invalid>
>> wrote:
>> 
>>>  Yet another method mentioned by VanguardLH elsewhere in this thread:
>>>
>>>  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>>>(without options/arguments). That will say 'efi' (ignore case), in
>>>several places, if you have an UEFI system.
>> 
>> Or not. My home-built PC uses UEFI but the output of bcdedit doesn't
>> mention "efi" anywhere.
> 
>   Hmmm!? On my (HP) system, the Windows Boot Manager and Windows Boot
> Loader 'path' names end in '.efi'.
> 
>   What about Disk Management, does that list an 'EFI' partition?
> 
>   N.B. I have only HP systems, so I'd be interested if (some of) these
> things are HP-specific.

Those are image files, the same as when .dat or .wmi are listed for the
boot loader files.  However, .efi files are boot loaders that the BCD
table points to that UEFI can start loading.  They contain instructions
for loading and starting an OS.  EFI files can be digitally signed for
integrity checking by UEFI Secure Boot (if you enabled that in the
UEFI/BIOS).

WIM files are file-based disk image formats.  For example, WindowsPE
ships or builds as a .wim file.

https://www.techtarget.com/searchenterprisedesktop/definition/Windows-Imaging-Format-WIM

While the .dat filetype usually means a data file, it has also been used
to specify an image file for an OS image.

EFI files follow the PE-COFF (Portable Executable - Common Object Format
File) standard image format.

https://learn.microsoft.com/en-us/windows/win32/debug/pe-format

I know some of the other boot image formats utilize WinPE's boot loader,
like the boot entry for Macrium Reflect (if you add it to the boot
list).

Since the OP says bcdedit doesn't list any .efi boot destinations, he
doesn't have UEFI.  WMI and DAT are used with MBR, and physical
enumeration in boot.ini before that.  He might have some BCD entries
specifying .wim files, or .dat files.

I remember the old boot.ini text files you could edit in Notepad that
located the boot loader by in the boot sector by drive and partition
(drives started with an offset of 0 while partitions started with an
offset of 1).  I haven't seen that target type in bcdedit, but my boot
list is rather simplistic and short.

An easy way to determine if UEFI is involved is to run Device Manager
(devmgmt.msc), and look under <computer> -> System Devices to look for
"Microsoft-compliant UEFI system".

Another easy way is to run msinfo32.exe, and look for "BIOS Mode: UEFI".
If Legacy, it's MBR.

With bcdedit, look for the "Windows Boot Loader" section(s) at the path
setting.  If it points to \Windows\system32\winload.exe, it's legacy
(MBR).  If it points to \Windows\system32\winload.efi, it's UEFI.  Under
the "Windows Boot Manager" section, if path points to
\EFI\Microsoft\Boot\bootmgfw.efi, its UEFI.  Char says he sees no .efi
strings in the output of bcdedit.  

In Disk Management (diskmgmt.msc), look at the recovery partition on the
boot disk to see if it says "Healthy (EFI System Partition)".  The
section in the partitioning information may be too narrow to see much
past "Healthy", so hover the mouse cursor over the partition to see the
full comment.

It is possible the mobo has UEFI, but is configured to run in legacy
boot mode through the CSM (Compatibility Support Module) that provides
legacy BIOS compatibility to support MBR drives, especially if GPT was
unnecessary (the drives were under 2TB with 4, or less, partitions), or
to provide compatibility with older operating systems.  The UEFI specs
does contain an MBR section, too, with its partition table and partition
entries.  Intel was supposed to phase out CSM by around 2020, but the
OP's (Allan's) computer is much older.

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

#182394

VanguardLH <V@nguard.lh> wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
> 
> > Char Jackson <none@none.invalid> wrote:
> >> On 16 Feb 2025 19:15:23 GMT, Frank Slootweg <this@ddress.is.invalid>
> >> wrote:
> >> 
> >>>  Yet another method mentioned by VanguardLH elsewhere in this thread:
> >>>
> >>>  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
> >>>(without options/arguments). That will say 'efi' (ignore case), in
> >>>several places, if you have an UEFI system.
> >> 
> >> Or not. My home-built PC uses UEFI but the output of bcdedit doesn't
> >> mention "efi" anywhere.
> > 
> >   Hmmm!? On my (HP) system, the Windows Boot Manager and Windows Boot
> > Loader 'path' names end in '.efi'.
> > 
> >   What about Disk Management, does that list an 'EFI' partition?
> > 
> >   N.B. I have only HP systems, so I'd be interested if (some of) these
> > things are HP-specific.

[...]

> Since the OP says bcdedit doesn't list any .efi boot destinations, he
> doesn't have UEFI.  WMI and DAT are used with MBR, and physical
> enumeration in boot.ini before that.  He might have some BCD entries
> specifying .wim files, or .dat files.

  Sigh! It's not the OP (who is John C.), but Char Jackson, and Char
says (see quote above) "My home-built PC uses UEFI", so he *does* have
UEFI. You're not suggesting that Char doesn't know what he's talking
about, are you!?

[...]

[Several repeats of info I already mentioned.]

[...]

>	    Intel was supposed to phase out CSM by around 2020, but the
> OP's (Allan's) computer is much older.

  Also Allan (Higdon) is not the OP, John C. is.

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

#182401

On 17 Feb 2025 18:57:43 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:

>VanguardLH <V@nguard.lh> wrote:
>> Frank Slootweg <this@ddress.is.invalid> wrote:
>> 
>> > Char Jackson <none@none.invalid> wrote:
>> >> On 16 Feb 2025 19:15:23 GMT, Frank Slootweg <this@ddress.is.invalid>
>> >> wrote:
>> >> 
>> >>>  Yet another method mentioned by VanguardLH elsewhere in this thread:
>> >>>
>> >>>  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>> >>>(without options/arguments). That will say 'efi' (ignore case), in
>> >>>several places, if you have an UEFI system.
>> >> 
>> >> Or not. My home-built PC uses UEFI but the output of bcdedit doesn't
>> >> mention "efi" anywhere.
>> > 
>> >   Hmmm!? On my (HP) system, the Windows Boot Manager and Windows Boot
>> > Loader 'path' names end in '.efi'.
>> > 
>> >   What about Disk Management, does that list an 'EFI' partition?
>> > 
>> >   N.B. I have only HP systems, so I'd be interested if (some of) these
>> > things are HP-specific.
>
>[...]
>
>> Since the OP says bcdedit doesn't list any .efi boot destinations, he
>> doesn't have UEFI.  WMI and DAT are used with MBR, and physical
>> enumeration in boot.ini before that.  He might have some BCD entries
>> specifying .wim files, or .dat files.
>
>  Sigh! It's not the OP (who is John C.), but Char Jackson, and Char
>says (see quote above) "My home-built PC uses UEFI", so he *does* have
>UEFI. You're not suggesting that Char doesn't know what he's talking
>about, are you!?

He's probably right, actually. I apparently don't know what I'm talking
about in this case. It happens!

Msinfo.exe shows "bios mode - legacy", which I don't remember setting,
and during cold boot, if I enter what we used to call BIOS, the screen
says UEFI, but that could just be a Gigabyte thing. 

I'm not sure how disk size and format play into it, but in addition to
the system drive, I have 5 data disks in this system, all formatted GPT,
with capacities of 12TB, 14TB, 14TB, 18TB, and 18TB.

Apologies for leading you astray. Please carry on. :)

[snipping the rest]

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

#182412

Char Jackson wrote:
> On 17 Feb 2025 18:57:43 GMT, Frank Slootweg <this@ddress.is.invalid>
> wrote:
>
>> VanguardLH <V@nguard.lh> wrote:
>>> Frank Slootweg <this@ddress.is.invalid> wrote:
>>>
>>>> Char Jackson <none@none.invalid> wrote:
>>>>> On 16 Feb 2025 19:15:23 GMT, Frank Slootweg
>>>>> <this@ddress.is.invalid> wrote:
>>>>>
>>>>>>  Yet another method mentioned by VanguardLH elsewhere in this
>>>>>> thread:
>>>>>>
>>>>>>  In a 'Run as administrator' Command Prompt window, run 'bcdedit'
>>>>>> (without options/arguments). That will say 'efi' (ignore case),
>>>>>> in several places, if you have an UEFI system.
>>>>>
>>>>> Or not. My home-built PC uses UEFI but the output of bcdedit
>>>>> doesn't mention "efi" anywhere.
>>>>
>>>>   Hmmm!? On my (HP) system, the Windows Boot Manager and Windows
>>>> Boot Loader 'path' names end in '.efi'.
>>>>
>>>>   What about Disk Management, does that list an 'EFI' partition?
>>>>
>>>>   N.B. I have only HP systems, so I'd be interested if (some of)
>>>> these things are HP-specific.
>>
>> [...]
>>
>>> Since the OP says bcdedit doesn't list any .efi boot destinations,
>>> he doesn't have UEFI.  WMI and DAT are used with MBR, and physical
>>> enumeration in boot.ini before that.  He might have some BCD entries
>>> specifying .wim files, or .dat files.
>>
>>  Sigh! It's not the OP (who is John C.), but Char Jackson, and Char
>> says (see quote above) "My home-built PC uses UEFI", so he *does*
>> have UEFI. You're not suggesting that Char doesn't know what he's
>> talking about, are you!?
>
> He's probably right, actually. I apparently don't know what I'm
> talking about in this case. It happens!
>
> Msinfo.exe shows "bios mode - legacy", which I don't remember setting,
> and during cold boot, if I enter what we used to call BIOS, the screen
> says UEFI, but that could just be a Gigabyte thing.
>
> I'm not sure how disk size and format play into it, but in addition to
> the system drive, I have 5 data disks in this system, all formatted
> GPT, with capacities of 12TB, 14TB, 14TB, 18TB, and 18TB.
>
> Apologies for leading you astray. Please carry on. :)
>
> [snipping the rest]

I have msinfo32 on my windows 10 64 bit that shows a lot of info.  To set 
boot safe boot options use msconfig.  Actually I am not sure if you are 
still on the subject line.

<Bill>

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

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

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

csiph-web