Skip to main content

Report the Windows Update Build Revision (UBR) with Custom Fields

What the UBR shows

The Windows Update Build Revision (UBR) is the revision portion appended to the operating-system build number on Windows 10 and Windows 11. FileWave can collect the registry value with a Custom Field so administrators can group and report devices by full build revision.

Use UBR as a version indicator, not complete update-health proof.
A matching revision helps compare devices, but it does not replace Windows Update status, failed-installation review, or validation against the approved build for your environment.

Why collect it

Keeping devices updated is crucial for maintaining security, stability, and optimal performance. By monitoring UBR numbers, IT administrators can:

  1. Identify devices that are not up-to-date with the latest updates.
  2. Plan and execute update deployments effectively.
  3. Verify the success of update installations.
  4. Maintain compliance with internal and external policies or regulations.

This is useful in any managed Windows environment that needs to compare device build revisions during patch validation or troubleshooting.

Create or import the Custom Fields

The first Custom Field returns the numeric UBR value from HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion:

$ubr_version =(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").UBR
echo "$ubr_version"
exit 0

The second Custom Field combines the Windows version and UBR into one reportable string:

$os_version = (Get-WmiObject -Class win32_OperatingSystem).Version
$sub_build_version = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").UBR
echo "$os_version.$sub_build_version"
exit 0

Import the prepared definitions or create equivalent fields manually:

  1. Download Windows UBR.customfields.zip and extract Windows UBR.customfields.
  2. Review both embedded PowerShell scripts before import.
  3. In FileWave Central, open Assistants > Custom Fields > Edit Custom Fields.
  4. Choose Import and select the extracted .customfields file.
  5. Before saving the imported fields, review Assigned to all devices for both fields. The supplied definitions enable this option. Clear it for a limited pilot, then use Edit Custom Field Associations to assign one or both fields to the intended Windows test devices or groups.
  6. After a test device verifies and submits inventory, compare the reported values with that device's Windows version and registry UBR. Once you have confirmed the expected values, expand the assignment to the intended devices.
  7. Add the field to a Report (formerly Query) or use it as Smart Group criteria.

Related content

No comments to display