it is funny you should say this. Just recently, i started updating my clients to 12.1.5337.5000. (Win 7 x64 Enterprise)
I usuallyt deploy to a First rollout group and then to the rest of the company. this time it was a little different.
quick backgroup, we are in the process of updating some server to 2012r2 and we just recently moved all our VMs from one hyper host cluster on 2008r2 to a newer hyper host cluster on 2012r2.
i rebuilt/created a new deployment box and imported all my Microsoft Deployment Toolkit builds from an olfer version of MDT to the most recent release. With that, i also updated all my system deployment information, software patches, etc... Sep 12.1.5337.5000 was on of those softwares. we have 10 new employees start so i blasted 10 new machines all with the new av client.
now to the point, 2 of the new machines have experience the hanging at the shutdown screen after an attempted reboot. the most recent case was a call center rep that restarted at 5:00pm on 1/15/15 and i had to kick the box manually this morning at 1/16/15.
moreover, i just deployed the client to 13 addtional machines as part of a First rollout group deployment last night. we have auto protect, download protection, sonar, early launch anti-malware, ie protect, outlook protect, intrusion prevention, app control to block most usb devices (excpt HID) enabled. this is a desktop specific policy that we built. i have installed this on a few servers as well (as part of a first rollout group as well) i have not rebooted any servers after the client update, so i have not data for that to share.
in the system logs, i see the following message for the SEP:Agent:Behavior
User is attempting to terminate Symantec Management Client....
event source: SMC; category: 0; severity: Info
i had not opened a case. i can if you all think it will help.
keep me posted as this is probably set to affect all of my clients.