Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 995577" data-attributes="member: 32260">The list was created several years ago. Now, adding other PowerShell extensions except PS1 is not necessary on Windows Home and Pro:<ol>
<li data-xf-list-type="ol">The user cannot accidentally run any PowerShell file. Windows built-in default settings will force opening it in the notepad or the file will not be opened at all (extension not registered).</li>
<li data-xf-list-type="ol">The PSM1 files do not support the &quot;Run with PowerShell&quot; option in the right-click Explorer context menu.</li>
</ol>The PSM1 script can be run by using CmdLine, but this cannot be blocked by adding PSM1 extension to &lt;Designated File Types&gt;. The author uses a config related to Enterprises, where the default Windows PowerShell settings are different.Finally, Hard_Configurator blocks by default all possible PowerShell scripts (also PSM1) not by SRP, but via the &lt;Block PowerShell Scripts&gt; option from the H_C right panel.I could add the PSM1 extension, but I did not test it, so I do not know how this could impact the users who skipped the &lt;Block PowerShell Scripts&gt; option. The PSM1 files are for PS1 files like DLLs for EXE files. The PSM1 modules are used to store functions that can be imported by PS1 scripts.</blockquote>

[QUOTE="Andy Ful, post: 995577, member: 32260"] The list was created several years ago. Now, adding other PowerShell extensions except PS1 is not necessary on [B][COLOR=rgb(0, 168, 133)]Windows Home and Pro[/COLOR][/B]: [LIST=1] [*]The user cannot accidentally run any PowerShell file. Windows built-in default settings will force opening it in the notepad or the file will not be opened at all (extension not registered). [*]The PSM1 files do not support the "Run with PowerShell" option in the right-click Explorer context menu. [/LIST] The PSM1 script can be run by using CmdLine, but this cannot be blocked by adding PSM1 extension to <Designated File Types>. The author uses a config related to [COLOR=rgb(184, 49, 47)][B]Enterprises[/B][/COLOR], where the default Windows PowerShell settings are different. Finally, Hard_Configurator blocks by default all possible PowerShell scripts (also PSM1) not by SRP, but via the <Block PowerShell Scripts> option from the H_C right panel. I could add the PSM1 extension, but I did not test it, so I do not know how this could impact the users who skipped the <Block PowerShell Scripts> option. The PSM1 files are for PS1 files like DLLs for EXE files. The PSM1 modules are used to store functions that can be imported by PS1 scripts. [/QUOTE]

Verification