Boot In.safe Mode

[Octaviano Collars]

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.

When I rebooted the computer, my monitor gives a "signal out of range" error because I believe the video is being detected at a higher resolution than the monitor supports. How can I force Ubuntu to start up in a lower resolution so that I can adjust display properties. I've already tried editing the /etc/default/grub and un-commenting #GRUB_GFXMODE=640x480 line. I know in Windows, you can press F8 on boot to go into a safe video mode so I'm looking for the equivalent in Ubuntu.

To start Ubuntu into safe mode (Recovery Mode) hold down the left Shift key as the computer starts to boot. If holding the Shift key doesn't display the menu press the Esc key repeatedly to display the GRUB 2 menu. From there you can choose the recovery option.

-method 1

first boot:

press the escape key to enter the startup menu then enter normally the os login manager , then restart

second boot:

press the shift key , it will redirect you to the gnu grub screen

I have a Proliant Microserver Gen8 running Windows Server 2012 R2. Our Anti-malware installed an update that causes the server to not boot correctly. In other Proliant Servers (DL380 Gen8 and 9, DL360 Gen8 and 9) I was able to get into safe mode (all through iLO) because the recovery utilites presented the option to restart in safe mode, however the Microserver does not present the same choices despite it having the same operating system.

I also have a DL160 Gen9 that had the same issue but I was able to spam F8 once the HPE screen with the green rectangle came up. I have instruced the on site tech to do the same with this Microsoerver but he is un able to get it in Safe Mode.

OK, I was able to do this eventually through the similar method I used on the Proliant DL160 Gen8. After the initial BIOS screen, there will of course be the HP Proliant screen that goes through the HP SMart Array config (F5) and the iLO 4 advanced config (F8). On the bottom are the choices F9 system Utilities F10 Intelligent Provisioning and F12 (or is it 11..I forgot already) for Network boot. The second it leaves this screen start spamming F8. It will enter the next screen with the choices stacked up, F9 RBSU, F10 Intelligent Provisioning...and so on. Keep spamming F8. It may continue onto "Attempting to boot to CD-Rom depending on your boot options. Keep spamming F8. It will eventually get to the Safe Mode choice screen.

- If you keep trying and fail to get to Safe Mode, try pulling the power once Windows starts to load. I know this is not recommended, but I think it helped it into getting into Safe mode the next reboot.

Do you have a firmware password enabled? If a firmware password is enabled, then alternate boot modes will be inaccessible unless you enter the firmware password. If a firmware password is enabled, then you should see a padlock icon with a box for entering your password when you Option Boot the Mac by holding down the Option key immediately after powering on the laptop. I know some boot options do not trigger the prompt for the firmware password such as a PRAM Reset. I'm not sure if any of the other boot options will trigger a password prompt for the firmware password. In case this is the problem here is an Apple article regarding the firmware password:

Wondering if you might want to try upgrading your system from System Preferences, (and if you do have the update option there in 10.14.6) It does mean, however, all 32 bit apps will need updating to 64 bit apps to operate in Big Sur. (Apple apps would, of course, be updated along with the Operating System)

No external devices where ever connected to my Mac since I asked my question. Only exception was my USB keyboard which was occasionally connected to rule out a non functioning internal keyboard/button.

Don't hold the Shift key down until after you power on the laptop. Holding the startup keys before power on can prevent the Mac from booting or the Mac may ignore the held key(s). If the laptop has a boot chime, then hold down the Shift key immediately after the startup chime, otherwise hold down the Shift key within a second or two of powering on the Mac.

FYI, if the firmware password is enabled, then attempting to launch the Apple Diagnostics will just boot the system into macOS on the internal drive. I know this from personal experience being stymied about why I could not boot the Apple Diagnostics. I discovered the reason when attempting to Option Boot the Mac. Perhaps this behavior is different on various Macs.

I didn't see your post for some reason when I replied earlier suggesting the firmware password. I'm glad you thought of it. I wish Apple would prompt users for the password when attempting to boot alternate methods.

I am in an VMWare environment & have a 2016 Server that seems to be having issues with some 3rd party SW that is keeping me from being able to login to the Server correctly. I would like to Boot the VM to Safe Mode. My understanding is that if I get the VM rebooting, click in the Window to get the Focus on the VM & hit F8 during the VM Post mode it will bring me to Safe mode Menu. What I actually get when I follow this procedure is Booting to Boot Manager, which does not help at all!!

I know this may be out there a bit, but when the vm is up, can you connect to it using PSTools via command line? Then possibly uninstalling the application via command line as per: -to-uninstall-a-program-on-windows-10-from-command-prompt/

After attempting setting up Raspberry Pi bluetooth to be bluetooth receiver for stereo, now whenever I start it up I can't SSH at all, I can't use the desktop at all or CTRL+ALT+Fnumber key to get to a terminal.

I see a failed message on booting so I think last tweak broke bluetooth... but how can I possibly get to a root console to fix it again? Even in Shift recovery mode, Ctrl+Alt+F1 does not let me log in as it rejects the password. This is on up-to-date Pi3.

Instead of bypassing all the system can do, this tells init the runlevel is "S", and it can then do special things to support this case. I just tested this with my semi-ancient installation of Jessie.

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 am having an incredibly frustrating problem. My RT PXI chassis has decided that something has gone wrong. I am not sure what that could be, but now it boots into safemode attempting to reboot three times. I have never been able to retrieve the error log via MAX (I get time outs), but if I go into the physical drive via ftp and poke around in the errorlog.txt, I find the most recent error:

3a8082e126