Yes. It does create a new explorer process that goes away a little while after closing the window. But, even with a dozen Chrome tabs open and an Win10x64 VM running with 8GB of RAM on my Surface Book, which has 16GB of RAM, I have not found that to be a problem. I don't recall this being an issue on prior OS/hardware combinations either. When watching the process in SysInternals\ProcExp, CPU usage drops quickly when the window closes. After the timeout interval, the process then closes also. A new explorer process is launched even without the start command. And, the new explorer process is not a child of TCC, but of svchost.