WMI registry issues that can't be resolved by resetting the WMI registry - Windows 10

This issue is occurring in a Windows 10 environment.

I've had an issue arise in our environment that our application deployment and inventory tool is showing inaccurate data for around 10 percent of the workstations in our environment. The support for this tool has identified the issue as relating to the WMI registry, and punted at that point claiming it outside of their scope. The issue was confirmed with the test of running the command and getting the error response in an elevated PowerShell window below:

PS C:\WINDOWS\system32> Get-WmiObject -Class Win32_Product

Get-WmiObject : Generic failure

At line:1 char:1

• Get-WmiObject -Class Win32_Product

• 
      + CategoryInfo          : InvalidOperation: (:) [Get-WmiObject], ManagementException 
  
      + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand 
  
  

At this point, I searched on WMI registry issues, and found the typical documented processes for checking the WMI registry, and resetting if necessary.

I've also tried other basic troubleshooting steps to fix system issues, like running sfc /scannow

I have found that running the command of winmgmt /verifyrepository results in a return of WMI repository is consistent, so it doesn't appear to be corrupt. However, under direction of Microsoft support, I completed a reset of the WMI registry with the below process:

1. Disable and stop the WMI service:

sc config winmgmt start= disabled

net stop winmgmt

1. Navigate to the WBEM folder:

cd %windir%\system32\wbem

1. Rename the repository folder:

   rename repository repository.old

1. Re-enable the WMI service:

   sc config winmgmt start= auto

1. Recompile all default WMI .mof and .mfl files:

cd %windir%\system32\wbem

for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

1. Reboot the system.

This process appears to have completed successfully, however, the problem has persisted, and I still get the same error in PowerShell as documented above.

At this point, Microsoft support guided me in doing a repair install of Windows 10 on the effected laptop. The repair install completed successfully, but the issue persists.

This issue occurs no matter who is signed into the laptop, so it isn't tied to a profile.

This is normally the point where the answer would be to give up on the Windows install and just wipe/reinstall Windows. However, that is not an acceptable answer when dealing with 10 percent of our workstations. Also, given the frequency of this occurring, I expect it to continue occurring until we find the root cause of this, and reimaging laptops anytime this problem occurs is not an acceptable solution.

I'm a bit surprised that the repair install didn't resolve the issue. We know the issue isn't in a user profile, and the repair install should have put a new set of system files on the laptop. What is left that wouldn't have been reset?

My thoughts at this point are that perhaps the All Users profile holds onto it's settings in the reset, and it lies in there - would that make sense? Is there a process to reset the All Users profile?

Or does anyone have any other ideas or suggestions on this issue?

***moved from Windows / Windows 10 / Performance and system failures***