Windows 10: Boot to Advanced Startup Options in Windows 10

I'm just not sure what would cause it to not boot to advanced startup like that, but you are able to with a USB.

One last thing to try is to turn off fast startup to see if it may be causing an issue with it.

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

 

I already turned it off. As I mentioned do you think its a problem with the shutdown command?

 

I'm not sure. How does running the command below work for you if you run it in an elevated command prompt?

shutdown /r /o /f /t 00

 

Curious and curiouser

I ran the command under the Admin Command Prompt and it worked! However, it was a one time thing. It now does a normal restart again. I even Shutdown my PC and then powered it on thinking a shutdown might be the key to get it to work. Alas it still doesn't work.

I didn't mention this but when I installed W10 using MCT it also worked only once. When I updated via WU it also worked once. This was using the restart button in PC Settings. I wonder if it's being executed in an elevated state doing it this way?

So we have a little more info. Got to be an answer.

 

I'm not sure what else to do other than clean install, test to see if it works properly without installing anything else yet, then test after you install anything to see if affected.

 

Hey Brink...

A clean instill fixed the problem which I didn't doubt it wouldn't. I think I managed to find out what was behind my problem. I use a tweak program called Windows 10 Manager. I've used it since Windows 7 and never had problems with it.

I installed it on my clean install. When I went in and changed just one option, and I don't think it really matters what option I changed, I got the Advanced Startup problem again. In addition it also screwed up Classic Start Menu. I can't get into the normal Windows Start Menu.

The option I changed in W10 Manager I undid it but still no good. W10 Manager might have changed more than this one option or the program is borked in some way. Just going into W10 Manager without changing anything doesn't screw things up.

I contacted the author to see what he has to say. He hasn't gotten back to me yet. I think some other Registry entry was changed that caused my problem.

 

At least you found the cause. If you created a restore point before this happened, then doing a system restore using that restore point should be able to undo it.

 

First of all, as you probably know, a System Restore does not restore everything. It is limited to specific things so it might not even work. More importantly I have SR turned off because I use Tweak.com Registry Backup.

What I really want to do is restore a disk image I took after I did the update which has all my programs and settings. Unfortunately this has W10 Manager on it with all the changes I've made over the years. There is no type of registry restore that will help me in this situation. The only way as I see it is to find the offending Registry entry and change it. Possibly have to add it or even delete it who knows. Using a program that takes a snapshot of your Registry before a change and then compares it to an after scenario, in this case making a change with W10 Manager, might be useful. Or a program that monitors changes and records them on the fly.

The author of W10 Manager just emailed me and he will look into it. From what he said in his email I don't even think he is aware of what the Advanced Startup Options are. I gave him a link to your tutorial on it.

 

I hope that they will be able to find the offending change W10 Manager made, and will be able to reverse it for you.

 

I ran a before and after Registry snapshot program. I found at least one entry that Windows 10 Manager added that causes my problem. Here's the added entry that causes the issue:

HKLM\SOFTWARE\Policies\Microsoft\Windows\System\AllowBlockingAppsAtShutdown = 0x00000001

AllowBlockingAppsAtShutdown doesn't normaly exist. Do you have any info on this entry Brink?

 

streetwolf,

The AllowBlockingAppsAtShutdown DWORD is for the "Turn off automatic termination of applications that block or cancel shutdown" group policy located at Computer Configuration\Administrative Templates\System\Shutdown Options in Local Group Policy (gpedit.msc).





If you like, delete the AllowBlockingAppsAtShutdown DWORD, restart the computer, and test to see if you still have the issue.

 

I already did that through adding it to the Registry myself. I suspect that going through GPEDIT would create the same Reg entry. I wonder if the entry was present in my previous version of Windows 10. If so than there is something different about W10 TH2.

I looked at all the Windows 10 Manager settings and can't seem to find the culprit. It is possible it is on the menu. I haven't changed anything on it btw.

 

AllowBlockingAppsAtShutdown should not be there by default. It's only added when you enable the policy in gpedit.msc or manually in Registry Editor.

That setting in W10 Manager enables the same policy.

 

Which setting in Windows 10 Manager? Is it on the screenshot? Is it one of the sliders?

 

The top check box at the bottom in your screenshot. Unchecking that box enabled the policy.