If you’re not aware of these risks then please look around.There are some good introductory articles on the entrust website that talk about this issue, but please note that these articles are from 2014 and somewhat understand the urgency of the issue.Upgrading your public facing websites and services that use public certificates (e.g. For those who are running a Windows Certificate Authority (CA) to issue private certificates to servers and devices on your network, there is potentially a different problem: How do you ensure that your private CA is able to issue SHA2 certificates, and if not, how do you upgrade it so that it can?certificates you purchase from a public Certificate Authority, aka “CA”, online) is actually fairly easy; buy a new certificate from a competent supplier, install it, remove old certificate. I’m going to discuss the methods I use, which are designed for a Windows PKI infrastructure with several levels (a root CA and subordinate “issuing” CAs).And, for some time now, to install various MS properties, it's been normal for a validation request to be asked for before downloading said program.You state that you "upgraded" your computer..your computer is an OEM system, a change of the motherboard would be viewed by Microsoft as a different system and that may account for the stated message.If you installed the WGA update it may have determined that your XP was not genuine when it actually is. If that does not work then reinstall XP and don't install WMP11. When you update XP make sure you do not download the WGA notification update.
So Microsoft cannot say they are unaware of the existence of this problem.
I've done so myself and not had a problem with telephonic communication and activation.