Windows 7 Shell replacement slow logoff

Finally, my uncoditional love for command line interfaces persuaded me to replace the default windows shell host (explorer.exe) with a command prompt ( Console | Download Console software for free at SourceForge.net) by changing the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Shell string value to path\console.exe file... (don't worry, I backed up, plus, I can't let the re-installation dvd just sit there collecting dust)

I like the way things are going, however, I do have one problem I can't quite understand: occasionally (especially after changing stuff like environment variables and virtual memory settings) logging off takes a long time (5-10) minutes. Logon, system shutdown, sleeping, hibernating, and locking all function normal. After some research on the issue, I noticed the problem is usually related to major changes in user account settings...

The only change I did make to user settings is I disabled user account control for my account, because I set Console.exe to run as administrator from the compatibility settings, and it would not start up with UAC turned on.

 

buried deep in the application and service logs under Microsoft > Windows > Diagnostic-Performance you may find a clue as to what is specifically causing the slow down, but I would suspect that one or (probably) more applications is holding the ntuser registry key open--windows will force these applications to shut down eventually, but generally allows them to stay open and close themselves after sending them the shutdown command

 

You should have tried powershell instead.

 

what in the wide world of sports makes you think that 'powershell' is in any way related to the alternate gui/shell replacement the OP mentioned?

 

he replaced explorer with cmd. and cmd got itself replaced by powershell. so he should have replaced explorer with powershell is most likely the idea of it.

but if that fixes the slow logoff, no clue..

 

Well I did try powershell, but I am more used to cmd and I don't need powershell to do what I do... Anyways, I can call it from cmd should I ever need it.

The problem is not affected by using the shutdown command instead of ctrl+alt+del or a dialog box, which says it will forcefully turn off running programs if called with a delay or the /f parameter... Which it does. Does it not shut down all the programs? Unlike the shutdowns when I used explorer, it just says "windows will shutdown in less than a minute" and then closes everything and goes to log off, and it does not ask me to close them myself.

The logs you mentioned only talk about drivers slowing down standby (sleep and hibernation), which perform pretty good and haven't changed at all!

 

did you post in the CONSOLE forum at soundforge?

 

I assume you meant sourceforge...

No, and I highly doubt it is the problem here... The first time this happened was actually in the last few hours before I made the replacement, but I turned a blind eye... I did actually use powershell for the first day before I found console and this was still bothering me. And now that I think about it, the problem seems to go away when I haven't made changes to virtual memory settings, environment variables and other such system settings after 2 or 3 reboots.

 

how about just letting explorer exists and putting cmd into autostart?

 

ok, is it established/admitted that the gui shell/command shell change has nothing to do with the slowdown???

if so, time to change the name of the topic.