Windows Startup Settings (including safe mode)

With Windows Startup Settings you can start Windows in different advanced troubleshooting modes to help you find and fix problems on your PC.

Get to Windows Startup Settings in PC settings

Swipe in from the right edge of the screen, tap Settings, and then tap Change PC settings.
(If you’re using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, click Settings, and then click Change PC settings.)

Under PC settings, tap or click Update and recovery, and then tap or click Recovery.

Under Advanced startup, tap or click Restart now.

Once your PC restarts, on the Choose an option screen, tap or click Troubleshoot. If you don’t see the Startup Settings option, tap or click Advanced options.

Tap or click Startup Settings and then Restart.

On the Startup Settings screen, choose the startup setting you want.

Sign in to your PC with a user account that has administrator rights.

Get to Windows Startup Settings in the Windows Recovery Environment

If you can’t start your PC, follow these instructions to get to the Windows Recovery Environment. You’ll need to connect a keyboard to complete the steps.

Do one of the following, depending on whether you have installation media (such as a DVD or USB flash drive):

If you have installation media for Windows 8.1, start your computer from the installation media. Insert the DVD or USB flash drive and restart your computer. If you see a message asking you to “Press any key to boot from DVD,” do so. If you don’t see the message, you might need to change the boot order in your computer’s BIOS settings so that it first starts from the DVD or USB. When you see the Install Windows page, tap or click Repair your computer to start the Windows Recovery Environment.

If you don’t have installation media, use the power button to restart your computer three times. This will start the Windows Recovery Environment.

In the Windows Recovery Environment, on the Choose an option screen, tap or click Troubleshoot.

Tap or click Startup Settings. If you don’t see Startup Settings, tap or click Advanced options, and then tap or click Startup Settings.

Tap or click Restart, and then wait while your computer restarts.

On the Startup Settings screen, choose an option.

Sign in to your computer with a user account that has administrator rights.

Some options, such as safe mode, start Windows in a limited state where only essential programs are started. Other options start Windows with advanced features (typically used by system admins and IT pros). For more info, go to the Microsoft TechNet website for IT pros.

Note: If you’re using BitLocker, you’ll need to suspend it before you can get to Windows Startup Settings. If you’re using Windows RT 8.1, you may be asked to enter your Device Encryption recovery key to get to the Startup settings.

Starts Windows in an advanced troubleshooting mode intended for IT pros and system admins.

Creates a file, ntbtlog.txt, that lists all the drivers that are installed during startup and that might be useful for advanced troubleshooting.

Starts Windows using your current video driver and using low resolution and refresh rate settings. You can use this mode to reset your display settings.

Safe mode starts Windows with a minimal set of drivers and services to help troubleshoot issues. If a problem doesn’t reappear when you start your PC in safe mode, you can eliminate the default settings and basic device drivers and services as possible causes. There are three different safe mode options:

Enable Safe Mode. Starts Windows with a minimal set of drivers and services.

Enable Safe Mode with Networking. Starts Windows in safe mode and includes the network drivers and services needed to access the Internet or other computers on your network.

Enable Safe Mode with Command Prompt. Starts Windows in safe mode with a Command Prompt window instead of the usual Windows interface. This option is intended for IT pros and system admins.

If the problem doesn’t occur when you restart your PC in safe mode, it’s unlikely that the basic settings, files, and drivers in Windows are the cause of the problem. Try starting all of the apps on your desktop that you commonly use one by one (including the apps in your Startup folder) to see if a specific app might be causing the problem. If one of the apps is causing the problem, uninstall it or contact the software publisher. If the problem appears while in safe mode, or you still can’t find the problem, you can try refreshing or resetting your PC. For more info, see How to refresh, reset, or restore your PC.

Why isn’t my Windows 7 x64 laptop hibernating properly?

Usually when I put my Windows 7 x64 Acer TravelMate 5520 laptop into hibernation nowadays, it starts back up in this screen:

Text in picture:

Windows did not shut down successfully. If this was due to the system not responding, or if the system was shut down to protect data, you might be able to recover by choosing one of the Safe Mode configurations from the menu below:

(Use the arrow keys to highlight your choice.)

Safe Mode with Networking

Safe Mode with Command Prompt

Start Windows Normally

Seconds until the highlighted choice will be selected automatically: 21

Description: Start windows with its regular settings

And then it fails to resume from hibernation. Hibernation used to work perfectly all the time, now it often does this. Sometimes it doesn’t do it, but usually it does.

I tried turning on and off hibernate through cmd.exe, but it doesn’t seem to consistently fix the problem. I tried restarting when it happens and then it may or may not work after that. Anyone have any idea why this is happening? Searching online didn’t find anything.

Hibernation used to work perfectly. I don’t want to stop using hibernation. Standby actually doesn’t work either on my computer. For some reason when I start up from standby the sound gets messed up and sometimes these horizontal white lines appear on the screen, and then I have to restart.

Troubleshoot Start menu errors

Start failures can be organized into these categories:

• Deployment/Install issues — Easiest to identify but difficult to recover. This failure is consistent and usually permanent. Reset, restore from backup, or rollback to recover.
• Performance issues — More common with older hardware, low-powered machines. Symptoms include: High CPU utilization, disk contention, memory resources. This makes Start very slow to respond. Behavior is intermittent depending on available resources.
• Crashes — Also easy to identify. Crashes in Shell Experience Host or related can be found in System or Application event logs. This can be a code defect or related to missing or altered permissions to files or registry keys by a program or incorrect security tightening configurations. Determining permissions issues can be time consuming but a SysInternals tool called Procmon will show Access Denied. The other option is to get a dump of the process when it crashes and depending on comfort level, review the dump in the debugger, or have support review the data.
• Hangs — in Shell Experience host or related. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. If a background application or service hangs, Start will not have resources to respond in time. Clean boot may help identify if the issue is related to additional software. Procmon is also useful in this scenario.
• Other issues — Customization, domain policies, deployment issues.

Basic troubleshooting

When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. For issues where the Start menu or subcomponent isn’t working, you can do some quick tests to narrow down where the issue may reside.

Check the OS and update version

• Is the system running the latest Feature and Cumulative Monthly update?
• Did the issue start immediately after an update? Ways to check:
  • PowerShell:[System.Environment]::OSVersion.Version
  • WinVer from CMD.exe

Check if Start is installed

If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.

If Start was working and just fails intermittently, it’s likely that Start is installed correctly, but the issue occurs downstream. The way to check for this problem is to look for output from these two PS commands:

get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost

get-AppXPackage -Name Microsoft.Windows.Cortana

Failure messages will appear if they aren’t installed

If Start is not installed, then the fastest resolution is to revert to a known good configuration. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. No method is supported to install Start Appx files. The results are often problematic and unreliable.

Check if Start is running

If either component is failing to start on boot, reviewing the event logs for errors or crashes during boot may pin point the problem. Booting with MSCONFIG and using a selective or diagnostic startup option will eliminate and/or identify possible interference from additional applications.

• get-process -name shellexperiencehost
• get-process -name searchui

If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate third-party or additional drivers and applications.

Check whether the system a clean install or upgrade

• Is this system an upgrade or clean install?
  • Run test-path «$env:windir\panther\miglog.xml»
  • If that file does not exist, the system is a clean install.
• Upgrade issues can be found by running test-path «$env:windir\panther\miglog.xml»

Check if Start is registered or activated

• Export the following Event log to CSV and do a keyword search in a text editor or spreadsheet:
  • Microsoft-Windows-TWinUI/Operational for Microsoft.Windows.ShellExperienceHost or Microsoft.Windows.Cortana
    • «Package was not found»
    • «Invalid value for registry»
    • «Element not found»
    • «Package could not be registered»

If these events are found, Start is not activated correctly. Each event will have more detail in the description and should be investigated further. Event messages can vary.

Other things to consider

When did the problem start?

• Top issues for Start menu failure are triggered
  • After an update
  • After installation of an application
  • After joining a domain or applying a domain policy
• Many of those issues are found to be
  • Permission changes on Registry keys or folders
  • Start or related component crashes or hangs
  • Customization failure

To narrow down the problem further, it’s good to note:

What is the install background?

• Was this a deployment, install from media, other
• Using customizations?
  • DISM
  • Group Policy or MDM
  • copyprofile
  • Sysprep
  • Other

• Group policy settings that restrict access or permissions to folders or registry keys can cause issues with Start performance.
• Some Group Policies intended for Windows 7 or older have been known to cause issues with Start
• Untested Start Menu customizations can cause unexpected behavior by typically not complete Start failures.

Не загружается windows 10 — startup.nsh

Такая вот проблема.
Установка Windows 10 на новый ноутбук MSI.

Вставил флешку, выбрал приоритет загрузки с usb флешки.
Все ок, загрузка пошла. Далее система показала какие то 6 дисков.
Один диск был разбит на несколько мелких частей. На ту часть диска, которая была вся свободна (450 гб)
Показалась ошибка (возможно это важно?!) — «преобразуйте диск в MBR».
И пошла установка. Все вроде ок, windows встал и запускается.

Но только при включении всегда следующее:
press ESC in 1 second to skip startup.nsh, any other key to continue.
Shell>_
Вложение:

И приходится вводит exit, нажимать enter и только после этого, происходит нормальная загрузка Windows 10.

Внес изменения в файл startup.nsh — из всех вариантов помогло добавить фразу — bootx64.efi
Результат есть, сообщение все равно показывается, и идет отчет 5,4,3,2,1 и потом автоматически загружается.
Не много раздражает и хочется, чтобы все работало как должно.

Кто сталкивался, может сможете подсказать, что делать?
Любые идеи принимаются.

п.с. после установки windows появились вот такие диски.

Press esc in 1 seconds to skip startup.nsh
press esc in 1 seconds to skip startup.nsh не работает клавиатура и мышь. Помогитееее, Люди.

Press ESC in 2 Seconds to skip startup.nsh,any other key to continue
Пытался переустановить виндовс,после переустановки стала выбивать данная ошибка, что делать?

Windows XP — StartUP Problem
Извините что пишу англискими буквами, у меня нет Русски кеыбоард. Постараюс обяснит мою проблему.

Windows Installer Startup
Доброго времени суток! Каждый раз при загрузке windows появляется установщик windows с надписью.

Решение

поосторожнее — этим Вы удалите диск восстановления системы от разработчика, но если он Вам не нужен (и что-то мне подсказывает, что в том образе восстановления полно утилит от MSI, которые показыват мультики — о том, какой хороший ноутбук, то есть — мусор) то лучше всего сделать так, как советует kumehtar.
Мой вариант:
1. Скачайте все драйверы для Вашего ноутбука с сайта производителя.
2. Разберитесь с UEFI BIOS ноутбука — включите там только режим UEFI.
3. Из смонтированного образа с 10-кой скопируйте всё, что там есть на заранее отформатированную флешку в FAT32 — всё это можно сделать самой виндой, без всяких там «супер»-утилит.
4. Загрузитесь с этой флешки.
5. Если всё-таки решились очистить весь диск и по-нормальному его разбить на разделы, в окне создания разделов: Жмeте нa клaвиaтype Shift + F10. B кoмaнднoй cтpoкe ввoдите кoмaнды (после каждой команды нажимать Enter на клаве):
Koнвepтиpoвaть в GPT:

diskpart
list dlsk (ecли диcк нe oдин)
sel disk 0 (выбор диска)
clean
convert gpt
exit (выxoд из diskpart)
exit (выxoд из cmd)

Внизу жмете кнопочку «Обновить».
6. Создаете разделы, которые Вам хочется и устанавливаете на тот, который создали под диск С:\, винду.
Если это не поможет, отключите в UEFI BIOS ноутбука Secure Boot (после установки винды, его можно обратно включить, если захочется).