Nested Issue -- RegEdit missing WinLogon->Shell Key for Startup

[StevenDorsey]

For the context of my situation, see this forum's thread below:
 

He reset his pc, but one of the symptoms was having the startup key changed in the following location:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell

My Shell location did not exist altogether, and I was thinking creating it would make my laptop start booting up normally again. I don't know how it happened. I was installing fallout 3 and fallout 3 mods yesterday, tried disabling the windows defender notification thing that starts up, and watching youtube videos nothing else. So, I don't know what I could have done to cause hte black screen and cmd window to pop up in the system32 location.

However, just the sound of that now seems to me like the bootup process is reaching that point when its supposed to launch things, and maybe the absence of the Shell key in RegEdit was preventing it from opening Explorer.exe, which was probably necessary for everything else to run.

The reason for this thread though, I've created a Key in Winlogon where it should be, but it only has the default keyword with nothing set now. So:

1. What type of Keyword(s) do I need to create here, do I just use the default?
2. What do/does they/it need to be named?
3. What value(s) does/do it/they need to have?

 

-----------------------------------------------------------------------

Edit: I went into MSConfig.exe, and it looks like my Boot Type was set to Selective Boot, but with every tickbox checked, so I set it back to Normal. Seems like it should have been booting the same way that way regardless though. Do you think that could have had a hand in it?

-----------------------------------------------------------------------

Final Edit: I just figured out that "Shell" is supposed to be a Keyword that exists in the Winlogon Key Folder, not another Key Folder under Winlogon. That being said, my Winlogon\Shell is already set to 'explorer.exe', so I might need to Refresh my Windows 10 OS, because I don't see anything else that could be causing this.

[23ek1jelkejd10dsslk14]

34 minutes ago, StevenDorsey said:

Final Edit: I just figured out that "Shell" is supposed to be a Keyword that exists in the Winlogon Key Folder, not another Key Folder under Winlogon. That being said, my Winlogon\Shell is already set to 'explorer.exe', so I might need to Refresh my Windows 10 OS, because I don't see anything else that could be causing this.

Well from sounds of it, it looks like the best what you can do right now,

I checked my regedit and it's as you say - no Shell sub-key, just a value in Winlogon set to a explorer.exe

[StevenDorsey]

1 hour ago, MIKEsome said:

Well from sounds of it, it looks like the best what you can do right now,

I checked my regedit and it's as you say - no Shell sub-key, just a value in Winlogon set to a explorer.exe

Yeah. 'sfc /scannow' didn't detect any integrity violations. MBam 3 detected a change with that registry key, and deleted a modification, but that doesn't mean the keyword is back to the way it was, or that it's there at all anymore.