Skip to content

Missing Windows Auto Update

If Windows machines are missing Auto Update information in vScope, the most likely cause is that the machine is not inventoried with the WMI or WinRM probe, or the data is unavailable due to permission or registry settings. Here’s a guide to troubleshoot this issue.


How vScope Collects Auto Update Information

Auto Update information is different from patch data. Patch data represents updates already installed on the system, while Auto Update information pertains to how the auto-update feature is configured.

vScope collects Auto Update settings from specific registry paths:

  • \Policies\Microsoft\Windows\WindowsUpdate\AU\
  • \CurrentVersion\WindowsUpdate\Auto Update\

Within these paths, AUOptions values determine the auto-update configuration.


Steps to Verify Auto Update Data Availability

  1. Confirm WMI/WinRM Probe Usage
    Ensure the Windows machine is being inventoried with either the WMI or WinRM probe. vScope needs these probes to access registry information about auto-update settings.

  2. Verify Registry Access
    Make sure that the credential used by vScope has permission to read the Windows registry paths listed above.


Checking the Auto Update Settings Directly on the Machine

To check the registry for the AUOptions value:

  1. Open Registry Editor (regedit) on the target machine.
  2. Navigate to one of the following paths:
    • HKEY_LOCAL_MACHINE\Policies\Microsoft\Windows\WindowsUpdate\AU
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
  3. Look for the AUOptions entry in either location. The AUOptions value should be present with a configuration value.

If AUOptions is missing from these registry paths, vScope cannot retrieve auto-update information for that machine.


Example Registry View

Registry Path with AUOptions Entry:

Screenshot of Windows registry

AUOptions Value Set in Registry:

Windows Auto update settings in Registry Editor


Further Troubleshooting

If Auto Update information still does not appear in vScope:

  • Confirm that WMI or WinRM access is fully operational.
  • Double-check that the AUOptions entry is populated with a valid configuration setting.

By following these steps, you can ensure that vScope can collect auto-update configurations from your Windows machines.