Frankly, this is a question that is basically more just out of curiosity than a real problem because it's got an easy workaround, but I'd still like to know why the workaround is (sometimes!) needed. The situation is quite simple: the following command: C:\Windows\System32\notepad.exe (which is really in an alias named NP but it's the same if run directly from the command line) causes the TCC session from which I start Notepad to "hang" until Notepad is closed. This doesn't happen all that often, but once it starts to happen it's completely consistent: every time I start Notepad from any TCC session that particular TCC session completely hangs (i.e. the command prompt doesn't happen and no commands can be issued/executed) until I close that instance of Notepad; and this is the case for every TCC session from which I start Notepad until Windows is rebooted. And, yes, I know that if I execute the simple "enhancement" to the command "Start C:\Windows\System32\notepad.exe" that doesn't happen (frankly I and pretty much everyone else I figure would be shocked if it did), but it's a rather deep-down preference of mine to not do things that shouldn't have to be done, and this shouldn't have to be done. - Dan P. S. I've actually got an alias "FixNP=Alias NP=Start C:\Windows\System32\Notepad" to fix the Notepad issue if and when it occurs.