This problem has been around since last August and we're still seeing the issue, even with the latest RU6 MP2 PP1 builds. We have tried all of the recommendations above, as well as others suggested by Symantec's support organization, and still the problem persists.
In fact, while the problem used to only affect 64-bit clients, beginning with RU6 MP2 we started seeing it on 32-bit Windows XP systems, too. (But at least on 32-bit Windows XP systems you can manually re-enable the firewall after the first reboot and everything's fine.)
For us, the last reliable client builds were RU6a (11.0.6005), so that's what we're continuing to use until Symantec can resolve the problem once and for all.