Frequently Asked Questions

⮟ General Questions

Can I run this on Windows 7?

You can try. You'll apparently need to install Windows Management Framework 5.1 which includes a newer required version of PowerShell than what is included with Windows 7. I don't guarantee that it will work though.

Windows pops up a warning about the batch file

• This is because the batch file might not have developed a 'reputation' yet. You should be able to hit 'More Info' then 'Run Anyway'.
• To stop it from happening again for the file, you can Right Click > Properties > Look for "Unblock" at the bottom and check that, then hit OK.

Why do I need two different files?

You technically don't. Only the .ps1 file is truly necessary, because that is the actual program. The .bat file is just for convenience to make the .ps1 file easier to run, but the .ps1 file can be run manually with the instructions in the ReadMe - it's just an extra command in PowerShell.

What's the Zip file download for, and do I need the 'Extra' stuff?

On the releases page you might notice there are also downloads for Source Code (zip) and Source code (tar.gz). These are automatically added to the list of downloads by GitHub when creating a "release", and you can ignore them. They're basically a snapshot of the whole repo at the time of the release.

Also on the main repo page, there are folders like "Extra Tools" and "Extra Data" that are not necessary, they are just for anyone who finds them interesting.

---

⮟ Troubleshooting Questions

I'm getting an error such as "Cannot add type. Definition of new types is not supported in this language mode."

This means PowerShell has "Constrained Language Mode" enabled. From my knowledge there are 3 main ways constrained language mode might be enabled:

• Having any AppLocker script rules set up
• Having the __PSLockDownPolicy environment variable set. I have a video where I go into more detail about that here (linked to timestamp).
• Having a Windows Defender Application Control policy set up (Also Smart App Control enabled, which uses WDAC)

I'm getting an error like "setting is overridden by a policy defined at a more specific scope"

You probably have a group policy set at the user policy or machine policy level that defines an execution policy.

You can do this command to see which policies are applied at what levels: Get-ExecutionPolicy -List

I also discuss execution policy and how to change it in the same video mentioned before, linked here to the timestamp.