Windows 10: Boot into Safe Mode on Windows 10

Hey John,

When you upload a file, you just need to be sure to attach it afterwards. Uploading it alone will not have the file/image show in the post. *Smile

https://www.tenforums.com/tutorials/1...en-forums.html

If you like, you can use the same method below in Windows 10 as well to add Safe Mode to the boot options screen.

http://www.eightforums.com/tutorials...ndows-8-a.html

 

I have the exact same problem as CasioJones in post #10 of this thread wherein I boot to the OS and the result is a black screen. I have found that it is possible if rebooting that after login the desktop appears but displays no program icons including the recycle bin and displays as a rapidly flickering image for a minute or so before I get the black screen. The single other difference for me is that my install was not an upgrade from a previous version of Windows but rather a stand alone install from a downloaded ISO file from Microsoft.

I too can use ctrl+alt+del to access the several options to run task manager, switch user, etc, and they all work but the desktop refuses to display. The lack of icons gives me the notion that Windows explorer is not running. I recall a bug in Windows 7 that followed this scenario in which the solution was a registry hack, might this be a regressive bug in Windows 10?

I realize that I can use my install media to attempt access to Safe Mode and if that indeed works I am a bit uncertain as to what direction to take to try to figure out exactly what is wrong here. So I am looking for some direction here on what I might try to solve the issue. I'm all ears!

Thanks.

 

Hello Railtech, and welcome to Ten Forums.

Are you able to run explorer from Task Manger to get your desktop back?

 

I have not tried that yet. Right now I am away from the machine and cannot test. Might be that way for awhile but I will certainly give that a try. Thanks and I am open for anything else you might think of.

EDIT: Do you think it might be a user profile corruption issue?

 

Sounds good now, but the Cloud-Upgrade model MS is using means no recovery disk at install. Needless to say my upgrade did not go well and I had no safe-mode recovery option or W10 media. If that's an inherent limitation of the system fine, but if it was deliberate it was another huge error.

I'm restored and operational, after a lot of extra work, but needless to say MS has long forgotten what being a user feels like. I'm just glad I had the skills to recover. What do non-IT folks do?

 

Hello John, and welcome to Ten Forums. *Smile

You will always be able to have installation or recovery media for Windows 10.

https://www.tenforums.com/tutorials/9...-download.html

https://www.tenforums.com/tutorials/4...dows-10-a.html

 

Should any of you run into black screen after reboot and be without Win 10 DVD - Try to boot a ubuntu based LiveCD and and after you have got to the ubuntu based desktop, reboot and remove LiveCd and boot into windows - that fixed it for me*Smile

JBJ
MS Programmers should go back to the drawing board!

 

I used option 3 and went to an elevated command prompt and put this in
bcdedit /set {current} safeboot network

Then I used F8 to boot to safemode but the problem was I was in a continues loop, everytime I restarted it went right back to safemode. I had to use msconfig to untick safeboot and then i booted up normally

bcdedit /set {current} safeboot network <-----How do i remove this ?

 

Hello Ken, and welcome to Ten Forums. *Smile

You would want to use the command in step 3 of OPTION THREE in the tutorial to remove this entry.

 

You're most welcome Ken. *Smile

 

I was testing this out. When I am using the cmd prompt within Windows 10, I can follow these instructions to a tee. There is a loader entry marked {current} if I just type in BCDEDIT. However, I created a Recover Drive and used it to boot up and entered the command prompt. Now, if I type in BCDEDIT /SET {CURRENT} SAFEBOOT NETWORK, it just errors out (error occurred while attempting to reference the specified entry). And it is true that if I type BCDEDIT, the only loader entry is referring to the Recover Drive (E: in this case) instead of C: . So is it not possible to set the Win 10 PC to a safeboot mode from the cmd prompt offered from the recover drive using BCDEDIT?

 

Hello Starry, *Smile

Are you able to boot into Safe Mode using OPTION ONE instead?

 

If I go into the Advanced Options while Windows is up, then yes I can get to Startup Settings. But if I boot up on the Recover Drive (Flash Drive), then Startup Settings is not an option. I can get into Command Prompt, but perhaps it was never meant to allow me to access the Bootup Loader for the main PC when I am not booting up on it. I can get at the entries on the C drive ... it calls it the X drive, but it all the same files. So I could certainly change things. It's just that in that context, the current loader entry isn't loaded.

 

What I have done in the past is set up the PCs to allow selection of a Safe Mode every time the PC boots and that works pretty well. On Windows 8, I had it set up as separate multi-boot entries in the boot menu. But Win 8.1 stopped allowing that and I found some other way to do it. I was just hoping that things had changed on Windows 10 and I would be able to get into safe mode on a PC that won't boot normally.

 

Usually, you'll see X:\Sources> in a command prompt at boot.

Odd. Typing bcdedit in a command prompt at boot should also show you the boot details like below.

Usually at boot, you would have {default} as the identifier instead of {current} though.