T wrote:
Hi All,

Go To Assist has a function that allows me to boot into safe
mode. It does not use msconfig.

Is there a way to boot into safe mode without msconfig. Something
from the command line perhaps?

These things "seem" to change a lot in 10. (I use to just use f8
at boot.)

-T

F8 boot menu for Windows 10 (done from emergency boot CD).
Can be done from running OS as well, by removing the /store clause.

dir /AH C:\boot\BCD # verify it is there, it could be in system reserved

bcdedit /store C:\boot\BCD /set {bootmgr} displaybootmenu True

Looks like this. You could also tighten up the delay from
30 seconds to 5 seconds, so this menu can be left on customer
systems.

https://i.postimg.cc/0NVZWSnj/f8-in-boot-menu.gif

Note - results are unpredictable on multiboot Windows setups,
and anything which meddles with the individual OSes might not
present the menu you were expecting.

Note2 - if you use the Macrium boot repair option from the CD,
it will remove custom lines such as the one above.

*******

This is a second section from my notes. I think normally
the bootmenupolicy is "Standard" rather than "Legacy".
There are three items in the "safebootalternateshell"
family for altering the booting into safe mode directly
behavior. Whatever I was doing at the time, I must have
found some other way to do it, when the web page I was
using wasn't delivering the results I wanted.

Didn't work....
bcdedit /set {default} safebootalternateshell yes

bcdedit /set {default} bootmenupolicy legacy

# From the rescue DVD... C: is System Reserved, D: is OS partition.

bcdedit /store C:\boot\BCD /enum

bcdedit /store C:\boot\BCD /set {default} bootmenupolicy legacy

A far as I'm concerned personally, the "displaybootmenu" plus
shortening the delay, is something you can leave behind for
customers to marvel at. Then some day, on the phone you can say
to them, "try pressing F8 when you see that black screen with
the one line that says Windows 10".

Note that you can also customize the title string for each
OS in that menu, to make them easier for humans to comprehend.
I have a dual Windows boot here, where it says something
stupid like "Wxx on Volume 4" and if you insert another
disk it might become "Wxx on Volume 5", and while I like
comedy and all, I can't tell what the **** I'm booting with
a labeling scheme like that. You can assign static labels
if you want, which might suit the situation better.

And a SafeModeWithoutNetworking would be a "trap" for any
remote control situations. If I were you, I'd experiment
with the various modes in your own lab first, to figure out
which ones are duds from a practical perspective.

Paul