Boot Safe Mode Windows 10

[Rosy Demorest]

SafeMode starts Windows in a basic state, and uses a limited set of files and drivers. If a problem does not happen in Safe Mode, it means that the default settings and basic device drivers do not cause the problem. Observing Windows in Safe Mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your computer.

In Safe Mode, Windows has reduced functionality. The task of isolating problems is easier since many nonessential components are disabled, such as sound, third-party drivers and services, nonessential Windows services, and more. Corrupt software, drivers, or the installation of poorly configured software prevents Windows from successfully booting into normal mode.

I have a desktop Windows 10 x64 machine that's been working fine for months/years. It was automatically updated from Win7 last year. A couple days ago I replaced the 2x4GB DDR3 memory with 2x8GB DDR3. This seemed to work though for some reason it works at 800MHz instead of the 1600MHz that the memory supports. The BIOS shows mem freq 1600 as expected. But this is the smaller issue. The PC worked booted fine.When everything seemed to working as expected, I was still bothered by the slow startup and login times. Now with 16GB I had expected these times to improve.I installed Windows SDK performance recording tool and set it to record the boot sequence and restarted the PC. Windows failed to boot twice (UNEXPECTED KERNEL MODE TRAP) and went into the auto diagnostic repair mode. Restore just spins until I lose patience. I did manage to boot in safe mode and disable the recording. It did not help.Running sfc/scannow "did not find any integrity violations".

I also managed to uninstall the Windows SDK/Perf Rec (by restarting the MSI service) - to no avail.

I ran the Windows memory test, but when it's done it reboots, the reboot fails, and I never did see the results.

I replaced the new RAM with the original ones, but this did not make any difference (BIOS setting are as they were originally).

Did you install the new sticks of ram into the same slots on the motherboard that you removed the old ones from ? There should be a manual for your motherboard from the manufacturer showing you the order that ram should be installed.

Please configure Windows to generate complete memory dumps, then restart the system and reproduce the crash. When done, compress the memory dump, upload it to a safe location and pm me a download link. Also enclose logs collected by ESET Log Collector (it generates a zip archive).

Before I can do what you ask, which would require me to reinstall it (again) and figure out the mem-dump process, please take a look here, where I originally posted and where I was pointed to ESET as the/a cause. There's a zip file there with the dumps I did a couple of days ago. Please LMK if they're sufficiently informative.

I know you can remotely shutdown a Windows machine with the "shutdown" command line. But I think it's impossible to remotely get a machine into safe mode (with networking). Does anyone know of a way to do this?

If you have the option to interactively connect to Windows on the machine, though, you can use MSCONFIG to set the /SAFEBOOT switch in boot.ini, then reboot the machine. Do Start -> Run and type in MSCONFIG, then on the boot.ini tab check /SAFEBOOT under Boot Options and choose which safe mode you want to boot into (in this scenario, NETWORK).

This is exactly what HP's integrated lights-out option is for. Editing the boot.ini file won't be much help, since you won't be able to log into the machine, as the RDP service won't run. In case that's an HP server though you can connect directly to it's console via https portal, and also have access to virtual "power button".

Not an answer to the question, but hopefully useful to anyone who's hit issues when trying this. I found that despite rebooting in safe mode with networking, various services including Remote Desktop Services and Server (i.e. providing SMB access to boot.ini) failed to start, giving error code 1084 when started via MMC > Services.

Note: You can just run the 3 lines below; the function above is just there as a convenience wrapper. I've not tested the above cmdlet; though I have used this method without the wrapper so can say that all individual parts work.

That answer above about edit the boot.ini , is nice and all -- EXCEPT....you can't change the boot.ini file...if you follow "Mark's" directions step by step - you hit a brick wall because the boot.ini is read only.

If you hastily chose to modify the BOOT.ini to restart in safe mode with networking, and then restart, you will find that you cannot remotely log in at all. You WILL likely be able to view the boot file \\machinename\C$\boot.ini, but won't be able to modify it because it is read only. You will also not be able to "right-click and uncheck 'read-only' " because you won't be able to navigate to the C$ directory at all. I now have to physically login to this virtual workstation in order to change the boot.ini back. I will never make that mistake again!

In earlier versions of Windows, boot.ini was a system file that contained information about the Windows operating systems installed on a computer. This information was displayed during the startup process when you turned on your computer. It was most useful in multiboot configurations, or for advanced users or administrators who needed to customize how Windows started.

In this version of Windows, the boot.ini file has been replaced with Boot Configuration Data (BCD). This file is more versatile than boot.ini, and it can apply to computer platforms that use means other than basic input/output system (BIOS) to start the computer.

If you need to make changes to BCD, such as removing entries from the list of displayed operating systems, use the command-line tool Bcdedit, an advanced tool intended for administrators and IT professionals. For technical information about Bcdedit, go to the Microsoft website for IT professionals.

If your computer is a multiboot configuration, you can still change which Windows operating system opens by default, and how long to display the list of operating systems, by using System in Control Panel.

If you should make this mistake, you will likely be able to navigate to the boot.ini file via File Explorer, so \hostname\C$\boot.ini, and there is a chance you will also be able to remove "/safeboot:network" and save.

I'm trying to boot into windows safe mode so that I can run the DDU utility and install the Bootcamp adrenalin drivers (for gaming). When I boot and select the windows partition, I hold 'shift' which brings up the boot options, I select 4 (safe mode), and the login screen flickers, then a black screen, and no response.

I rebooted to a black screen using a 5K monitor over USB-C / Thunderbolt. So, I hooked up a 4K screen over HDMI which did the trick. Windows doesn't play nice with 5K screens over USB-C / Thunderbolt.

Restart. After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.After your PC restarts, you'll see a list of options. Select 4 or F4to start your PC in Safe Mode. Or if you'll need to use the Internet,select 5 or F5 for Safe Mode with Networking.

I had a similar problem where I needed to boot into safe mode or access other Windows recovery options, but couldn't because my Mac had the touch bar and for some reason my trackpad and keyboard would not work when booting into Windows, at all. After learning that Windows should automatically boot into recovery mode if there have been 4-5 hard reboots (assuming Bootcamp is your main startup disk), I tried hard resetting (holding the power button down until it shuts down, then pushing the power button to turn it on) several times.

On top of that, considering my trackpad and keyboard would not work when booting into Windows, I instead hard rebooted while holding down the Option button, which brought up the Mac and Bootcamp (Windows) partitions, where my trackpad and keyboard worked. Then, I held down the shift button while I clicked on the Bootcamp (Windows) partition "arrow" button. That booted Windows into recovery mode, which gave me the options I needed and I was able to fix what I needed to.

I just finished going through this, and fixed it. It was a pain because you can't run the tool on a Mac, so you must run the tool on a spare PC. I was on vacation, and didn't have one until I got home. My Windows 10 boot up was stuck at the blue logo.

Safe mode is an alternate way of starting up your computer so it's only using the essential programs needed to run. Normally, when you boot up your computer, it loads a lot of drivers, which are programs that allow your operating system (OS) to communicate with other devices and software. However, when you start up in safe mode, only the minimum number of drivers needed to run the computer are loaded (usually just the mouse, keyboard, and display drivers).

Let's say one day you go to use your computer and find that your OS just won't start, or maybe it keeps crashing on you. This could be due to any number of reasons, including a virus, malware, corrupt files, or something else entirely. Safe mode allows you to boot up your OS in a very basic state so you can potentially identify and fix the problem.

Once you think you've solved your problem, you'll need to get out of safe mode to test and see if it worked. To do this, simply restart your computer. When it boots up again, it should start Windows in its normal operating mode.

This website uses cookies to measure and analyze our traffic. For more information about the cookies we use, see our Terms of Use. If you want to change your decision later on, select the 'Cookie Policy' link in the footer.

The Problem:

I'm attempting to setup an alert for if one of my forwarder machines boots in Safe Mode. The data that's retrieved from Windows Event Viewer and Splunk Web Interface regarding booting-ups is:

3a8082e126