Trouble with DWORD:ffffffff being converted to '-1'

[NoDowt]

When using the below for the registry info.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\AES 128/128]
"Enabled"=dword:ffffffff

We end up get getting the following powershell
# Reg2CI (c) 2022 by Roger Zander try { if(-NOT (Test-Path -LiteralPath "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\AES 128/128")){ return $false }; if((Get-ItemPropertyValue -LiteralPath 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\AES 128/128' -Name 'Enabled' -ea SilentlyContinue) -eq -1) { } else { return $false }; } catch { return $false } return $true

The hex 0xFFFFFFFF dword value is being converted to '-1' decimal, rather than '4294967295' as shown in regedit, or when doing a get-ItemPropertyValue on the same key already set as 0xFFFFFFFF.

Interestingly, the ConfigMgr GUI does the same thing when trying to setup a CI via browsing the registry & also when it is evaluating the registry item if you set the value to 4294967295 (we see it remediating from '-1' to 4294967295 every time it is evaluated).