Skip to content

IIS Site V-278953: Fix fatal registry key path error - #1559

Open
FrederickGeek8 wants to merge 2 commits into
microsoft:devfrom
FrederickGeek8:fix-iissite-key
Open

IIS Site V-278953: Fix fatal registry key path error#1559
FrederickGeek8 wants to merge 2 commits into
microsoft:devfrom
FrederickGeek8:fix-iissite-key

Conversation

@FrederickGeek8

@FrederickGeek8 FrederickGeek8 commented Jul 23, 2026

Copy link
Copy Markdown

Pull Request (PR) description:
This PR fixes a syntax error in the IIS Site 2.15 STIG introduced into Processed/IISSite-10.0-2.15.xml in 48674a30d084f4eda8f0a97c45d31ae81e448e4c (although the error was introduced to the manual rule log in an earlier commit).

It's perhaps worth noting that the syntax error appears in the STIG text itself.

I updated the Manual Rule specification, regenerated the XML using ConvertTo-PowerStigXml, and testing the new build in a testing VM I have set up. I no longer encounter the crash with the proper syntax.

This Pull Request (PR) fixes the following issues:
When running PowerSTIG v4.30.0 with IIS Site ruleset enabled, PowerSTIG crashes with the following error:

PowerShell DSC resource MSFT_RegistryResource  failed to execute Test-TargetResource functionality with error message:
The registry drive HKLM is invalid. Please update the Key parameter to include a valid registry drive.
Parameter name: Key
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

This is due to a registry key path starting like HKLM\ instead of HKLM:\. This PR fixes that syntax in the Manual Rule specification and regenerates the IIS-Site XML.

This PR will also close #1535 by finishing the work started in 4.30.0.

Task list:

  • Change details added to Unreleased section of CHANGELOG.md (Not required for Convert modules)?
  • Added/updated documentation, comment-based help and descriptions where appropriate?
  • Examples appropriately updated?
  • New/changed code adheres to Style Guidelines?
  • Unit and (optional) Integration tests created/updated where possible?

There is an error in the STIG descriptive text that was transcribed into
V-278953's manual rule. Without this fix, this IIS 10.0 Site PowerSTIG
cannot be run because the syntax for the registry key path is incorrect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IIS Site V-278953 is a No-Op

1 participant