Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 785551" data-attributes="member: 32260">There is the right way to do it, that disables CMD only for the particular account (you know it already). <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite135" alt=":giggle:" title="Giggle&nbsp; &nbsp; :giggle:" loading="lazy" data-shortname=":giggle:" />But, this can disable some BATs used by Intel to autostart its gadgets. Also OneDrive uses CMD to delete leftovers after updates, and some USB hubs can use BATs, etc. So, disabling CMD have to be made by the advanced user. Furthermore, CMD without admin rights is commonly used to create/download/execute more powerful script types or PowerShell commands.Disabling Windows Script Host script execution, MSHTA interpreter, and restricting PowerShell, will work without problems on most computers in the home environment. They are used by most of malicious scripts (over 90%).</blockquote>

[QUOTE="Andy Ful, post: 785551, member: 32260"] There is the right way to do it, that disables CMD only for the particular account (you know it already). :giggle: But, this can disable some BATs used by Intel to autostart its gadgets. Also OneDrive uses CMD to delete leftovers after updates, and some USB hubs can use BATs, etc. So, disabling CMD have to be made by the advanced user. Furthermore, CMD without admin rights is commonly used to create/download/execute more powerful script types or PowerShell commands. Disabling Windows Script Host script execution, MSHTA interpreter, and restricting PowerShell, will work without problems on most computers in the home environment. They are used by most of malicious scripts (over 90%). [/QUOTE]

Verification