How to Fix Win32_OperatingSystem BuildNumber don’t work on Windows 10

In the present post, we will identify the cause and afterward give the resolution to the issue of Windows Management Instrumentation (WMI) Group Policy channels, that look at Win32_OperatingSystem BuildNumber, don’t work true to form on Windows 10.

Windows Management Instrumentation (WMI) is Microsoft’s implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) benchmarks from the Distributed Management Task Force (DMTF) which is a lot of specifications from Microsoft for consolidating the administration of devices and applications in a network from Windows registering frameworks.

WMI permits scripting dialects, (for example, VBScript or Windows PowerShell) to oversee Microsoft Windows personal PCs and servers, both locally and remotely. WMI comes preinstalled in Windows 2000 and in more up to date Microsoft OSes.

WMI additionally supports such actions as the configuration of security settings, setting and changing framework properties, setting and changing permissions for approved users and user gatherings, relegating and changing drive names, planning procedures to run at specific occasions, backing up the article store, and empowering or debilitating mistake logging.

Also see: Fix Symantec Endpoint Not Working in Chrome

WMI Group Policy channel Win32_OperatingSystem BuildNumber not working

You experience this issue depends on the accompanying situation;

You need Group Policy to apply to Windows 8.1 and later versions of Windows. You need to use Win32_OperatingSystem BuildNumber to do this. Also, you make the accompanying Windows Management Instrumentation (WMI) channel:

“Select BuildNumber from Win32_OperatingSystem WHERE BuildNumber >= 9200 “

In light of known form quantities of Windows versions as appeared in the table beneath:

9200 Windows 8
9600 Windows 8.1
10240 Windows 10
10586 Windows 10, version 1511
14393 Windows 10, version 1607
15063 Windows 10, version 1703
16299 Windows 10, version 1709
17134 Windows 10, version 1803
17763 Windows 10, version 1809
18362 Windows 10, version 1903

Right now, you would expect the WMI channel to cause the Group Policy setting to apply to build number 9200 and later forms, Windows 10 forms are prohibited.

As per Microsoft, this issue happens because the information type for BuildNumber is String and not Integer. Consequently, 10*** < 9600.

To determine this issue, use a channel that takes after the accompanying model:

Select BuildNumber from Win32_OperatingSystem WHERE BuildNumber >= 10000 AND BuildNumber LIKE "%[123456789][0123456789][0123456789][0123456789][0123456789]%" OR BuildNumber >= 9200 AND BuildNumber LIKE "%[123456789][0123456789][0123456789][0123456789]%"

Note: There are a few different ways to compel the string to contrast with return the outcome that you need. You can use any method that you like. The model is completely functional.

Leave a Comment