Re: Can not check Registry Path

[Daniel D.]

Is this something to do with 32 vs. 64bit views? https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/view-system-registry-with-64-bit-windows 

On Tue, Nov 22, 2022 at 9:52 AM JNAP NA <rootf...@gmail.com> wrote:

Hi
I have a problem that's driving me crazy, so I have 4 files and 4 registry checks for that files.

The first 3 checks are looking to keys inside the HKLM\Software\Wow6432Node, and they are working fine. The last one, it's looking into HKLM\Software\Microsoft\.... and it never finds anything. 

What already did/tried, run as administrator and that made no difference. 

Then I created several values in other keys (eg: HKLM\Software, HKLM\Software\Policies) only to check if it's a general problem, but no, in those cases I can get the key and the value... 

The only time I can't get anyhting it's when I'm trying to get keys\values inside the HKLM\Software\Microsoft... 

It looks like that it can't read/access the values inside the HKLM\Software\Microsoft root key or any  of the subfolders\keys.

I'm missing something? 

What's happening here? 

Here's a sample of the registry exported, part of the configuration and part of the log.

//REG FILE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v2.1\2.1.30]
"Version"="2.1.30.60071"

//CONFIGURATION

    <installedcheck path="SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v2.1\2.1.30"
                            fieldname="Version"
                            fieldvalue=" 2.1.30.60071 "
                            defaultvalue="False"
                            fieldtype="REG_SZ"
                            comparison="match"
                            rootkey="HKEY_LOCAL_MACHINE"
                            wowoption="NONE"
                            type="check_registry_value"
                            description="Check HKLM Version"/>
        </component>

//LOG FILE

2022-11-22 14:34:10    --- Loaded 4 supported component(s)
2022-11-22 14:34:11    Checking whether registry value 'SOFTWARE\WOW6432Node\Microsoft\VisualStudio\12.0\VC\Runtimes\x64\Version' exists
2022-11-22 14:34:11    Registry value: v12.0.40660.00
2022-11-22 14:34:11    -- Microsoft Visual C++ Redist 2013 (Microsoft Visual C++ Redist 2013): INSTALLED
2022-11-22 14:34:11    Checking whether registry value 'SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x64\Version' exists
2022-11-22 14:34:11    Registry value: v14.32.31332.00
2022-11-22 14:34:11    -- Microsoft Visual C++ Redist 2015-2019 (Microsoft Visual C++ Redist 2015-2019): INSTALLED
2022-11-22 14:34:11    Checking whether registry value 'SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v2.1\2.1.30\Version' exists
2022-11-22 14:34:11    *** No registry key found: SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v2.1\2.1.30\Version, default value: false
2022-11-22 14:34:11    -- Microsoft ASP.NET Core 2.1.30 (Microsoft ASP.NET Core 2.1.30): NOT INSTALLED
2022-11-22 14:34:11    Checking whether registry value 'SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x64\hostfxr\Version' exists
2022-11-22 14:34:11    Registry value: 6.0.10
2022-11-22 14:34:11    -- Microsoft .NET Core Runtime - 2.2.6 (Microsoft .NET Core Runtime - 2.2.6): NOT INSTALLED
2022-11-22 14:34:11    All required components installed: yes
2022-11-22 14:34:11    All optional components installed: no
2022-11-22 14:34:11    All checked components installed: no
2022-11-22 14:34:11    IsProcessElevated: yes

Thanks
JP 

--
You received this message because you are subscribed to the Google Groups "dotnetinstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dotnetinstall...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dotnetinstaller/5043e6c2-0d1b-4222-a9e9-0dc2f48182e2n%40googlegroups.com.

--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - t:@dblockdotorg - ig:@artdblockdotorg - github/dblock

[JNAP NA]

Yep

After posting I remembered that maybe that was the cause.. So after setting the wowoption property to WOW64_64, everything worked.

Thanks anyway

JP

To view this discussion on the web visit https://groups.google.com/d/msgid/dotnetinstaller/CALCE7pkHBgQMYyZQN43SWiu-Tm_Dy1QVafPdG_dLwzDoUsM3Cw%40mail.gmail.com.