Microsoft Intune – How to modify Windows 10 registry settings

See this article: Merged view of HKEY_CLASSES_ROOT.

The system uses the following rules to merge information from the two sources:

• The merged view includes all subkeys of the HKEY_CURRENT_USER\Software\Classes key.
• The merged view includes all immediate subkeys of the HKEY_LOCAL_MACHINE\Software\Classes key that do not duplicate the subkeys of HKEY_CURRENT_USER\Software\Classes.
• At the end of this topic is a list of subkeys that are found in both HKEY_LOCAL_MACHINE\Software\Classes and HKEY_CURRENT_USER\Software\Classes. The immediate subkeys of these keys from the HKEY_LOCAL_MACHINE tree are included in the merged view only if they are not duplicates of immediate subkeys from the HKEY_CURRENT_USER tree. The merged view does not include the HKEY_LOCAL_MACHINE contents of duplicate subkeys.

As it turns out, it has to do with the following:

1) The Powershell ISE was running on 32-bit machine and it was trying to remotely scan a 64-bit Windows OS.

2) WSUS running on a 64-bit Windows OS is a 64-bit app.

3) 32-bit Powershell ISE and 32-regedit cannot remotely "see" the following WSUS entries: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results

You can only "see" as far as:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

The WindowsUpdate subkey is invisible to 32-bit app.

To solve the problem, always running Powershell on a 64-bit Windows OS and you can remotely "see" both 32-bit and 64-bit Windows OS.