[Bug] - Script File Associations v3.4 — .ps1m should be .psm1

[EXPKevinGreer]

Baseline Info (please complete the following information):

• OS: Windows
• Version: 3.8

Describe the bug
The policy Win - OIB - SC - Device Security - D - Script File Associations - v3.4 contains an
association for .ps1m. This is not a valid PowerShell extension — the PowerShell module
extension is .psm1.

The entry therefore has no effect, and .psm1 files are not covered by the policy. Every tenant
deploying this baseline has the same gap.

To Reproduce

Via the policy configuration:

1. Open Win - OIB - SC - Device Security - D - Script File Associations - v3.4
2. View the default associations configuration XML
3. Observe the entry:

   <Association Identifier=".ps1m" ProgId="Applications\notepad.exe" ApplicationName="Notepad" />

4. Note there is no entry for .psm1

Expected behaviour
.psm1 files should be associated with Notepad, consistent with the other PowerShell and script
extensions covered by the policy. The .ps1m entry should be corrected to .psm1:

<Association Identifier=".psm1" ProgId="Applications\notepad.exe" ApplicationName="Notepad" />

Screenshots
Not applicable — the relevant XML line is included above.

Additional context
perhaps consider also .reg and .scr?