New
#10
You're welcome. I'm glad that they could help. :)
It may be a temporary glitch on your system. You might see if it still does the same after a restart.
You're welcome. I'm glad that they could help. :)
It may be a temporary glitch on your system. You might see if it still does the same after a restart.
Brink, not temporary, and no change after restart.
What was your basic user's UAC setting when you had no issues starting explorer from elevated cmd?
UAC was set to the default setting.
When you restart the computer, is it starting up into Windows as usual or a blank screen still. If still a blank screen, then you have some other issue at hand since restarting should allow it to startup normally if it was just explorer stopped.
You might see if you may be able to boot to advanced startup, and do a system restore at boot using a restore point dated before you had this issue to fix it.
https://www.tenforums.com/tutorials/2...dows-10-a.html
System Restore Windows 10
I have no problem restarting. No blank screens, nothing that like that. It's just that the explorer refuses to be restarted, which I have to do in Task Mgr by reaching it by ctl-alt-del or shift-ctl-esc.
I wonder if you can spend few more minutes for me. Be a normal, limited, user, but set your UAC to Always Alert=MAX.
then as a normal user start elevated cmd, do the taskkill and restart routine, the Option 2. PLEASE!!! My UAC is at Max.
I get the same under the same situation.
I find that when UAC is not set to default, it will cause all sorts of permission issues such as this.
By "get the same" do you mean the same results (explorer not started) as I get?
I was uninstalling Acronis and their cleanup utility asked if to close explorer, I said yes. They closed it. Then after cleanup, the log said they're starting explorer. It didn't start.
I also have a problem with installing an application which also needs to kill and restart explorer. Same problem.
So it's a feature of non-default UAC? M$ sure comes up with funny things.
This process (Option one, automatic restart of Windows Explorer) fixed an unresponsive start button in Windows 10 when a reboot was not an option because it would break a remote connection. Thank you.
Brink,
You might like to include KeithM's PS script [post #25] that stops & starts explorer and also re-opens File explorer windows.
Code:Shell = New-Object -ComObject shell.application $SavedPaths = ( $Shell.Windows() | select -expand LocationURL ) -ne '' Get-Process explorer | Stop-Process $SavedPaths | ForEach { explorer $_ }
- Note the limitation Keith states in post #33
Denis