none
Multiple Windows Update Errors (maybe a certificate issue?) RRS feed

  • Question

  • This is a fresh install, where fresh means it was reinstalled over an existing install and nothing was kept from the previous install, of Windows 8.1. Windows update appears to be checking forever but nothing is ever updated. 

    I've seen a good number of errors in WindowsUpdate.log and tried to address those through the various fixes seen throughout these forums. Many thanks to those that have contributed over the years!

    The same image has been used without issue to reimage other machines but I downloaded another one from our volume license subscription as a just in case but it made no difference. At the very bottom is what I suspect the culprit is but I'm not deeply familiar with the backend of the Windows Update process. 

    Any assistance is appreciated!!!!

    Here is what I've tried so far and what the end result was.

    • Windows Update Troubleshooter: Found and fixed errors. I ran this multiple times through out the various attempts to get WU working.
    • sfc /scannow: Found no corrupted files
    • DISM /Online /Cleanup-image /Restorehealth: Said it found issues and repaired them.

    I'm currently running through the steps below and currently at the "Reset or reinstall Windows" section which boggles my mind since this is a fresh install.

    https://support.microsoft.com/en-gb/help/10164/fix-windows-update-errors

    I've also tried everything noted here, 
    https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components

    I checked this and it seems the version on the machine is later than what's listed at this URL,
    https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-version

    Oh and I also tried this, 
    https://djseppie.wordpress.com/2010/07/19/windows-update-error-0x8024000c/

    I did notice this in the log and trying to fetch that URL manually via curl and Firefox does return a certificate error. Could this be the root cause of the problem? 

    2019-02-20 19:04:10:549 ****2c Misc WARNING: Send failed with hr = 80072ee2.
    2019-02-20 19:06:16:827 840 92c Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2019-02-20 19:06:16:827 840 92c Misc WARNING: Send request failed, hr:0x80072ee2
    2019-02-20 19:06:16:827 840 92c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://fe2.update.microsoft.com/v10/3/windowsupdate/selfupdate/wuident.cab>. error 0x80072ee2
    2019-02-20 19:06:16:827 840 92c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
    2019-02-20 19:06:16:827 840 92c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
    2019-02-20 19:06:16:827 840 92c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2

    Curl output:
    $ curl -D - -so /dev/null 'https://fe2.update.microsoft.com/v10/3/windowsupdate/selfupdate/wuident.cab' -v
    *   Trying 13.83.148.218...
    * TCP_NODELAY set
    * Connected to fe2.update.microsoft.com (13.83.148.218) port 443 (#0)
    * ALPN, offering h2
    * ALPN, offering http/1.1
    * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
    * successfully set certificate verify locations:
    *   CAfile: /etc/ssl/cert.pem
      CApath: none
    * TLSv1.2 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
    * TLSv1.2 (IN), TLS handshake, Server hello (2):
    { [90 bytes data]
    * TLSv1.2 (IN), TLS handshake, Certificate (11):
    { [3351 bytes data]
    * TLSv1.2 (OUT), TLS alert, Server hello (2):
    } [2 bytes data]
    * SSL certificate problem: unable to get local issuer certificate
    * stopped the pause stream!
    * Closing connection 0

    Firefox error:
    Someone could be trying to impersonate the site and you should not continue. Websites prove their identity via certificates. Firefox does not trust fe2.update.microsoft.com because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates. Error code: SEC_ERROR_UNKNOWN_ISSUER

    The WindowsUpdate.log file can be found here: https://www.dropbox.com/s/tadbmbr3mkapzmk/WindowsUpdate.log?dl=0


    Friday, February 22, 2019 6:18 PM

Answers

  • Thank you for responding. After spending 3 days on this I decided to just format and start over. It's a fresh install so I'm at a loss as to why this is occurring. Either way I appreciate you taking the time to respond.
    Monday, February 25, 2019 8:01 PM

All replies

  • Hi,

     

    According to your description, please try the following suggestions to check if the issue solved:

     

    >>>Solution 1

    Check if you are using a proxy server. If you do, double check the settings in the Internet Explorer and make sure that the proxy does not require a username or password to connect. If it does, the easiest way is to disable the proxy server during the duration of the windows update, although you can also create a workaround by setting your firewall to allow the connection to the Windows Update directly without going through the proxy.

     

    >>>Solution 2

    If your computer has been infested with spyware in the past – or it is at the moment – then the spyware might have modified your Internet Explorer settings to use a proxy server. Open the cmd.exe program and type issue the following command:

               netsh winhttp import proxy source=ie

     

    >>>Solution 3

    Some dll files might have become unregistered – due to various factors – which could trigger the windows update error 80072ee2. In this case, open cmd.exe, and register the following dlls: oleaut32.dll, jscript.dll, vbscript.dll, msxml.dll, softpub.dll, wintrust.dll, initpki.dll, cryptdlg.dll. You can register a dll by typing regsvr32 {name of the dl}.

     

    >>>Solution 4

    This is the rarest occurrence that may cause the windows update error 80072ee2, but your computer’s MTU setting might be incorrect. In this case, you simply have to set the MTU value to 1492 and try the windows update again.

     

    Hope these are helpful.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 25, 2019 7:25 AM
    Moderator
  • Thank you for responding. After spending 3 days on this I decided to just format and start over. It's a fresh install so I'm at a loss as to why this is occurring. Either way I appreciate you taking the time to respond.
    Monday, February 25, 2019 8:01 PM