Registry script is changing 5 of 6 keys

Anton_Howard Read the article (https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2013-3900), which does a .reg import. If I do that, the EnableCertPaddingCheck is a REG_SZ, not DWORD. I modified the script for that below. Could you test that?

Set keys
$CertPaddingCheckPaths = @("HKLM:\Software\Microsoft\Cryptography\Wintrust\Config", "HKLM:\Software\Wow6432Node\Microsoft\Cryptography\Wintrust\Config")
$SecuritySignaturePaths = @("HKLM:\System\CurrentControlSet\Services\LanManWorkstation\Parameters", "HKLM:\System\CurrentControlSet\Services\LanManServer\Parameters")
$EnableCertPaddingCheckKey = "EnableCertPaddingCheck"
$RequireSecuritySignatureKey = "RequireSecuritySignature"
$KeyValue = "1"

#CertPadding
foreach ($CertPaddingCheckPath in $CertPaddingCheckPaths) {
    # Create the registry key if it doesn't exist
    if (!(Test-Path $CertPaddingCheckPath)) {
        New-Item -Path $CertPaddingCheckPath -Force -ItemType Directory | Out-Null
        Write-Host Created $CertPaddingCheckPath
    }
    # Create or update the registry value
    Set-ItemProperty -Path $CertPaddingCheckPath -Name $EnableCertPaddingCheckKey -Value $KeyValue -Type String
}

#SecuritySignature
foreach ($SecuritySignaturePath in $SecuritySignaturePaths) {
    # Create the registry key if it doesn't exist
    if (!(Test-Path $SecuritySignaturePath)) {
        New-Item -Path $SecuritySignaturePath -Force -ItemType Directory | Out-Null
        Write-Host Created $SecuritySignaturePath
    }
    # Create or update the registry value
    Set-ItemProperty -Path $SecuritySignaturePath -Name $RequireSecuritySignatureKey -Value $KeyValue -Type DWORD
}

Write-Host "Registry keys and values have been created or updated successfully."

Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.

If the post was helpful in other ways, please consider giving it a Like.