PSHELL?

[vefatica]

It's better, but there are things I don't understand.

"PSHELL /S dir" works, and after that, "PSHELL /C" doesn't complain. After both of those, another "PSHELL /S dir" doesn't work.

Is the "persistent PowerShell interpreter" supposed to be restarted as needed? Is it started by default when TCC is started?

 

[vefatica]

In a new instance I could not repeat what I observed in my previous post. Then, in another instance, I could.

What does "PSHELL /C" do? It doesn't seem to free any resources and NSILP_PowerShell.x86.dll stays loaded along with about 15 other DLLs that were loaded when it was loaded.

 

[rconn]

Is the "persistent PowerShell interpreter" supposed to be restarted as needed? Is it started by default when TCC is started?

The PowerShell interpreter is started the first time it's needed, and isn't closed unless you do a PSHELL /C. It is not started by default when TCC is started.

 

[rconn]

What does "PSHELL /C" do? It doesn't seem to free any resources and NSILP_PowerShell.x86.dll stays loaded along with about 15 other DLLs that were loaded when it was loaded.

PSHELL /C closes the local instance of the interpreter. It does not unload the dll.

 

[vefatica]

PSHELL /C closes the local instance of the interpreter. It does not unload the dll.

Does closing it (or not closing it) have any practical effect? It doesn't seem to.

 

[rconn]

Does closing it (or not closing it) have any practical effect? It doesn't seem to.

Yes, it clears the internal PowerShell variables in the interpreter. 99% of the time, you wouldn't want to do that.

 

[AnrDaemon]

I suggest changing the /C switch descriptions from "close" to "clear".
Something like "/C(lear) Clears the persistent PowerShell interpreter state, effectively initializing it anew"