Derbolfinger

Oh tank you. For files and subfolder also? Or need I k:\folder\xyz_user*\* for files and subfolders?

Thank you OK. But I'm not sure now if I'm interpreting this correctly. Would k:\folder\xyz_user*\* work to exclude from scanning in all folders k:\folder\xyz_user1 to k:\folder\xyz_user50 all subfolders and files contained there? Or does something like xyz*\ not work for all folders starting with xyz?

Hello , on our server, we have about 50 numbered subfolders in a folder, in addition to other folders and files. These subfolders have the syntax xyz_user1 to xyz_user50, if a new user is added, the folder xyz_user51 is created. If I only want to exclude all these subfolders xyz_user## with content from the virus scan, the policy would then be correct: k:\folder\xyz_user* or does this not work at all? Thanks for help and hints

nobody has an idea? Or is there no other way than to turn off all warnings via GPO?

May be closed, it is wrong, it is a problem with Eset File Security on a terminal server.

A few days ago I had already described the problem under "Endpoint Products" (wrong) because I get wrong information myself. During RDS sessions Outlook / an add-in always gives a warning message like "A program is trying to access on data in Outlook or e-mail address information stored in Outlook. ... Allow access for 1 ... 10 minutes." The AntiVirus status in the Trust Center is not valid "Not available. This version of Windows does not support virus detection." (The translation may be not exact) How to tell Outlook that Eset Antivirus is installed? We don't want to turn off the warnings generally via GPO or something like that.

Oh oh, sorry. I got wrong informations, this problem is possibly only on the terminal server, and there is antivirus status not valid in the Trust center! "Not available. This version of Windows does not support virus detection." Eset File Security for Microsoft Windows Server 7.2.12004.2

Please be patient a little longer. Last week the producer of the basic program still said that the problem was due to the antivirus program. But now there is an update for the main program with an included update of the Outlook Add-in, what is unusual. Maybe the error is in the add-in. I will be back again in a few days - with procmon log or with the message that everything is ok.

No, only when the add-in is active on working. The add-in copies certain e-mails from Outlook to an external archive, and only when it is supposed to do so, the message appears.

Yes, Antivirus status: Valid And I don't want to disable the warnings in general (Resolution Method 2 of your link to microsoft).

Hello, We have on 30? computers with Windows 10 or on terminal server with Outlook 2019 a problem with a warning message. In outlook is an add-in to archive e-mails in an enterprise software, i don't know exaclty the warning message in English, but it is like: "A program is trying to access on data in Outlook or e-mail address information stored in Outlook. ... Allow access for 1 ... ?0 minutes." Previously it was possible to completely disable the message, now access must be granted continuously for a few minutes maximum. The program manufacturer and a web search (at Microsoft) think it's a dificulty with the antivirus program, but Windows and Eset ( Endpoint Security 7.3.... / File Security on the terminal server) seem to be satisfied 😉 In WIndows security everything is green and windows reports Eset Security as active. Do you have any tips or ideas?

I have reinstalled both and it looks like it works correctly. I don't think so. There exists no special policies for this computer in cloud administrator and about 40 computers work well. I will watch the computer for a few days and then back to the staff with it. 🙂 Thank you both for the support

No, no "bad image" since this dll. But "Unable to load module MODULE_ID_SSL. Reason: 7001" in trace.log

I have wrote you, that i have renamed the protobuf.dll to protobuf.alt on this not working system und replaced it with a protobuf.dll from an other computer with working Eset Endpoint Security. Yes, you're right, this protobuf contains only zeroes, amazing. Virus? windows file system failure? hard drive failure? Looks not friendly. That could be the reason for error 0xc000012f "Bad Image" Protobuf.dll, or not? Can't we go further with the trace.log? protobuf.zip with the working dll from the other computer (same license) Protobuf.zip

oh sorry, I misunterstood you. I renamed the file to Protobuf.alt and replaced it by a Protobuf.dll from a working computer, and so i get the trace.log. Both Protobuf.dll had the same size and date. Inside the zip ist no the renamed file Protobuf.zip