I have a program that creates a unique batch file (.bat). Defernder always flags the files and subsequently, the program aborts prematurely. The batch files are created in the same directory each time, but the name of the batch file is constantly changing. I can’t seem to find a way to tell Defender to ignore batch files in that particular directory. I want to use something like c:\folder*.bat, but can’t find a way to do it.
Why struggle with Defender if you could use CIS. In CIS you give the program the Installer/Updater policy and you’re done.
Call me stupid, but I can’t figure out how to do what you suggest. *.bat appears in the list of protected files. Do I just delete this entry from the list? The name of the batch file changes with each “running” of the executable that creates the batch file. The executable is already listed as a trusted application. I am at a loss as to how to define a continuously changing batch file so that it isn’t prevented from executing.
Are you talking about Windows Defender, or Defense+? Defense+ is a component of CIS, Windows Defender is a product from Microsoft that you will probably want to get a hold of them for specifics on how to configure it.
If you were talking about Defense+, you’ll probably want to set the folder containing the .bat files as a file group, and give the file group the Installer or Updater policy. This way, and .bat in that folder will be able to run, no questions asked by Defense+.
If you take a look at this page from the online help file, down near the bottom of the page, it tells you how to create a new file group.
Sorry for the confusion. I am addressing a Defender+ issue. Somehow, after my last post I did manage to do what you suggested (I think) as the program ran without causing an issue in the *.bat file. However, I’ll go back after reviewing your refernce to make sure I did define the folder correctly.