You can see the VirtualBox.exeinstance running in the task manager, but if you try and kill it refuses to go away. Since then, when trying to start a VirtualBox guest (doesn't matter what guest), nothing happens. A couple of days ago, our Corporate IT decided they were going to silently install a newer version Symantec Endpoint Protection. We were running VirtualBox 4.3.16 on a Windows 7 Enterprise SP1 圆4 host.

I would very much appreciate the effort from everyone ) I have the Services.msc opened, i watch the services beeing stopped, refreshing to see on what state is the service (stopping, stopped)īut until i see the services stopped, i am like 'please work.

Of course the SEP client will work again when i will receive the GO from my customer that i can reboot the servers.īut considering the fact that they are Production servers, you just can't have them rebooted whenever you want :|Īnd seeing this situation i am in at the moment and have been in the pas, i became 'paranoia' in using the 'smc -stop' function to stop a SEP :)Įverytime i use it, it gives me the creeps, because i have the Tsk Mngr opened, i watch the processes :) I have disabled the Tamper Protection before running smc -stop, because of what i read around many articles, stating that is good to have it disabled, becuase if would not interfere with anyone who tries to tamper SEP, so i did this.īut my main concern is that at this moment i have 2 production servers who have their SEP clients almost 'broken', because durring the 'smc -stop' process, the ccSvcHst.exe just frozen on STOPPING status :|

I was wondering if there is a way to find out why the process ccSvcHst.exe jamms when i do a 'smc -stop' on a SEP client.

Stop symantec endpoint protection cmd