Scripting Question

Registry Value Equals CIR not working

07/10/2020 415 views

I've been unable to get the following CIR working and to pick up systems with the defined reg value.

RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, Userinit, C:\Windows\system32\KUsrInit.exe{{comma}})

I've also tried it as 

RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, Userinit, C:\Windows\system32\KUsrInit.exe,)

Ever since Windows 8, Any major hardware or OS changes will cause this specific registry entry to get merged with the windows default setting, causing File Explorer to launch every time a user logs in to a computer.  My goal is to create a MI that will automatically correct this setting after a Windows 10 build upgrade or hardware change.

Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


Use RegistryValueReturn and then create a smart label to identify the machines with the incorrect value.

Answered 07/13/2020 by: chucksteel
Red Belt

  • That was my backup plan but would require a smart label as well as an additional CIR entry on systems which I was hoping to avoid if possible as they create some clutter in the appliance.

    I may have to fall back to that after all, ty.

    [Edit] ended up going the route you suggested as it's a bit more transparent for someone else if they needed to review what was going on, I'm pretty certain that my original issue was related to 64-bit redirection though as I had to alter the CIR before it worked correctly.

    RegistryValueReturn(HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, Userinit, TEXT)
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ