Error 80072f8f updating windows

The occurrence of the error prevents your computer from checking for available updates automatically.The most possible moment when you may encounter this error is when accessing Windows Update.If you want to use a self-signed cert in IIS7 for your WSUS clients then you’ll want to take a look at this one: ======== IIS7 allows you to create it’s own self-signed certificate instead of using a standalone certificate authority or domain certificate. In this case , after creating the certificate it’s necessary to tell the client machines that the self-signed certificate is trusted in the domain. PFX file and change the file type to personal information exchange *.pfx, p12. Type the password to complete the process, leaving just Included all extended properties checked. Choose the option to place all certificates in the following store : Trusted root certification authorities. Once the policy updates, the clients should trust the certificate and begin working again. If the update applies successfully, you’ll need to look for another proxy server or VPN provider if you want to get future Windows updates while surfing anonymously.But even if you’re certain that you don’t use any proxy settings, I urge you to double-check, as there is a lot of malware capable of redirecting your traffic through a proxy server.

error 80072f8f updating windows-1error 80072f8f updating windows-73error 80072f8f updating windows-71

It indicates that there’s something wrong with the SSL (Secure Sockets Layer) connection between WU and the Microsoft Server.

In order to allow the certificate to be trusted, you need to import the self-signed certificate to the domain trusted root certificate authority to allow the clients to use and trust the new cert. Creating the self-signed certificate on IIS7: right click and import.

var microsoft = microsoft

Leave a Reply