Share via

Azure VM's are not being assessed (Exception from HRESULT: 0x80072F8F)

Girish Prajwal 706 Reputation points
2020-10-15T06:43:01.367+00:00

Hi Team,

4 VM's are not being assessed for latest patches which were released by Patch Tuesday. We see errors on these servers.
Exception from HRESULT: 0x80072F8F

Troubleshooting done:

  • Uninstalled the OMS agent on the VM
  • Re-installed the OMS agent on all 4 VM's
  • Manually checked for updates, if the VMs could download. It didn't work either
  • firewall is not restricted to download any patches as the other servers which are part of same subnets have downloaded the patches

Any more suggestions.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,585 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Girish Prajwal 706 Reputation points
    2020-10-16T06:22:17.037+00:00

    Hi Winston,

    I will check on the suggestion and share the results with you.

    Regards,
    Girish Prajwal

    1 person found this answer helpful.
    0 comments
  2. whoward-msft 2,766 Reputation points
    2020-10-15T22:10:00.497+00:00

    Hi @Girish Prajwal ,

    Can you try to RDP into the VMs and disable the automatic datetime settings then restart the VMs. That error code is associated with ErrorClockWrong. Disable the automatic datetime, start and stop the Windows Update and then restart the VM. You need to reset the clock settings to get the updates correctly.

    0 comments
  3. Vikram Savant 1 Reputation point
    2020-10-23T07:06:41.967+00:00

    Hi ,

    I also facing the same issue, We have start the Windows Time service but still Vm not showing updates.

    Please share solution

    0 comments
  4. Vikram Savant 1 Reputation point
    2020-10-23T07:07:31.877+00:00

    34489-image.png

    0 comments
  5. Weily 86 Reputation points
    2020-10-23T07:19:27.15+00:00

    the 0x80072F8F error is related to an SSL certificate issue due to a time mismatch or a broken certificate chain. This was resolved by first exporting the certificate, including the certificate chain, from SCCM/WSUS server. Then the certificate was copied to and imported into target server, specifically the local computer’s trusted certificate physical store.

    0 comments