Ah, now that makes sense. We never upgraded to 4.62 so never saw that it had broken. We will probably skip straight from 4.61 to 4.63 (or whatever version ends up reporting Windows Server 2012 correctly via @ProductType).

Thanks for the support,
Steve.