Module seems to not work in constrained language mode (files signed)

[ckuever]

Tools category

Harden Windows Security Module

Does your system meet the requirements?

• Yes, my system meets the requirements 👍

Is your Windows installation genuine?

• Yes, I am using genuine Windows installation. 💯

Please explain the bug

Hi,

re-opening #243 with information

we did everything as you also nicely described

https://github.com/HotCakeX/Harden-Windows-Security/wiki/Script-Enforcement-and-PowerShell-Constrained-Language-Mode-in-WDAC-App-Control-Policies

However even if the modules could be loaded with no issues, there are no commands available

have you ever tried your nice modules with script enforcement and in constrained language mode? Or will this simply not work?

Thank you.

[HotCakeX]

Hi,
The modules here use advanced features that aren't allowed in constrained language mode even when signed (which isn't what i had expected but that's what i experienced), maybe the PowerShell team can shed some light on it later.

That's why I personally don't recommended script enforcement unless the device isn't going to use PowerShell except for some simple built-in commands.

---

since it's not a bug, at least not one that i can fix, i'm gonna move it to discussions, i will update you as soon as i have new info on this 🙂

[ckuever]

all fine and can be closed :-) we expected that and thanks for confirmation

[HotCakeX]

No problem, i will keep you posted if i have more info about this subject.