Ben,
I believe what you say is incorrect. Windows 8 Professional RTM x64 does not work with WDE. After encryption has begun, on every boot you are presented with a BSOD for SYSTEM_SERVICE_EXCEPTION w/ pgpsdk.sys. I've tried this on 3 different systems (ThinkPad X201, ThinkPad X230, and ThinkCentre M91p ultra-small desktop) all with the exact same result. These are all vanilla installs of Windows 8, join to domain, install/enroll in PGP, encrypt, reboot, perpetual fail. There is no option during the install of Windows 8 regarding UEFI and the X201 is plain old boring BIOS only, so that has nothing to do with it.
I am using PGP Desktop 10.2.1 MP2 bound to UN 3.2.1 MP2 - the latest offerings from Symantec.
When you say Q2 FY13, do you mean Q4 CY12? Like October-December of this year? If not, then when?
This is becoming all to common for Symantec. New OS versions are released and it takes forever to get working versions of PGP. Being at a College, we have faculty that need to use/teach the latest software. We also have a need to secure the College's data and it is so frustrating the lack of support by Symantec for both the Windows and Mac versions of PGP. Also, UEFI has been around for many years. Why is it just being looked into now?
I hate having to go to my CIO and telling him: "Sorry, we can't roll out any Windows 8 laptops or Mountain Lion laptops because PGP still doesn't work."
I'm not ranting directly at you, but this keeps happening over and over w/ Symantec. The pause encryption bug I brought to Symantec's attention a year ago was finally fixed in 10.2.1 MP2 - a year after it was reported. It just doesn't seem like enough resources are devoted to this product.
Edit: After looking at the tech note you posted, I checked the tech note at that bottom of it: TECH190829. This is NOT the issue we are having. All these systems are booting in legacy BIOS mode via MBR disks. Encryption starts, but then perpetually BSOD's on boot after that.