When updating just now to build 52, I used the Task Manager to keep track of the ShrAlias copies running. I purposely left it running in TCC before I issued the command "option /u". When I got to the point in the installation process where I was asked about automatically closing it and then restarting, the installer shut it down.
Later when I clicked on the option to run Take Command now, at the point when the registration prompt came up, two copies of ShrAlias started running, as shown in the following screen capture.
After clicking "Continue", TCMD started and ran TCC in one tab. It showed the following:
TCC 17.00.52 x64 Windows 7 [Version 6.1.7601]
TCC Build 52 Windows 7 Build 7601 Service Pack 1
Running C:\tcmd\ver17\TCSTART.btm
No need to load SHRALIAS. It is already running.
TCSTART saw that ShrAlias was already running and did not try to load it again. Unloading it went as follows:
TCC(17.00.52): C:\Users\Jay\DOCUME~1\mydrop~1>shralias /u
SHRALIAS unloaded
TCC(17.00.52): C:\Users\Jay\DOCUME~1\mydrop~1>shralias /u
SHRALIAS unloaded
TCC(17.00.52): C:\Users\Jay\DOCUME~1\mydrop~1>shralias /u
SHRALIAS not loaded
That got rid of the two copies. Starting a second TCC tab produced the following, as expected:
TCC 17.00.52 x64 Windows 7 [Version 6.1.7601]
TCC Build 52 Windows 7 Build 7601 Service Pack 1
Running C:\tcmd\ver17\TCSTART.btm
Loading SHRALIAS
SHRALIAS loaded
set /r c:\tcmd\ver17\env.cfg
alias /r c:\tcmd\ver17\diralias.cfg
alias /r c:\tcmd\ver17\alias.cfg
function /r c:\tcmd\ver17\function.cfg