Axthorpe

Well I added one more “checkbox” in exclusion and got it working :) I checked these three: Do not monitor application activity Do not inherit restrictions from the (application’s) parent process Do not monitor the activity of child applicationsThe boxed that I left out was “inherit parent”, which I don’t really understand. But the beta is working, and it is a beta so I can live with it for now. The reason I asked about giving one program access to one file, was that I had som other AV-software years ago that could do that. But otherwise quite happy with Kaspersky, so keep up the good work. And thank you for quick response here in the forum. 👍 Kind regards Håkan

Ok, so it is not possible to assign write access on one specific file for one specific program. “let c:\programs\my.exe have read/write on the file c:\filename.txt” This can not be done with Kaspersky Total Security, correct?

Can you please answer my questions? I only want to know the feature I look for exists in Kaspersky Total Security for me as a user. Is there a possibility to allow access for one program to a specific file? Does it in Kaspersky Total Security exist an option/function/tab/…, where I can: Select one program Allow this program to edit a specific file Can I in Kaspersky Total Security select one file and give a specific program full acces to that file?

Before we do anything else, can you answer my main issue/questions: Is there a possibility to allow access for one program to a specific file? Does it in Kaspersky Total Security exist an option/function/tab/…, where I can: Select one program Allow this program to edit a specific file Can I in Kaspersky Total Security select one file and give a specific program full acces to that file?

Ok, apparently I was a bit unclear above ;) And I thank you for your will to investigate this 👌 This has become two issues, but for me it is one that matters the most. Is there a possibility to allow access for one program to a specific file? I want to allow the beta to be able to write to the hosts-file. I do not know if this is possible with Kaspersky Total Security. The beta is getting installed with “Low restrict”, possibly have a bad certificate and do not have write access to the hosts file (see image below). This is not the main issue. I wrote this hoping to get some information to send back to Flywheel, the maker of programs. I have been able to get it running by setting “Do not monitor application activity” (see image below). I understand that this is not Kasperskys problem. I do no expect Kaspersky to handle beta software correctly. The reason I sen the two links above about the certificate differences was that I hoped that that would be a clue to why Kaspersky handled the programs differently. I am fine with this temporary solution, but it is for me a temporary solution until: Flywheel fixes their program or I can set file access to the hosts fil (point 1 above) And I also have a ticket and some forumposts going with Flywheel about this, because it is really their problem to get their program to work as good as the first one ;) --- write block history --- --- image on how I got the beta to work ---

Beta or no beta, my initial question still stands. How can I allow access for a program to edit the hosts file (C:\Windows\System32\drivers\etc\hosts)? Is this something that can be done?

(ops forgot a bit) I have found two differences, that may or may not affect the “write block” ...and the beta does not have a valid certificate.

Yes, I get and error when the program tries to modify C:\Windows\System32\drivers\etc\hosts I am using “Local by Flywheel” and it works fine, it is a tools for creating and running WordPress sites locally and the publishing to their hosting platform. So they need to edit the hosts file when setting up new sites locally. This program works fine and I have not needed to anything to get it to work, Kaspersky does nothing. But Flywheel has recently released a new version in beta and that program is being blocked when it tries to add something in the hosts-file . So the stable version is grouped as “Trusted” and the beta is grouped in “Low restricted”, but even when I manually put it in “Trusted” I still get the “write block”. So what I had to do to get the beta working is to turn off program monitoring for that exe; “Do not monitor application activity”, in Program Rules/Exclusions Tab. This feels like a very temporary solution… What i really would like is to add a rule that allows the beta to edit the hosts-file, which feels like a better solution than turning off all monitoring for the program (a program that runs php-code from WordPress, plugins etc). I have found two differences, that may or may not affect the “write block” 3.3.0 - the stable working release https://whitelisting.kaspersky.com/advisor?lang=en-US#search/65649B07BA77BF632C21AA0BEC1BABC2 5.0.7 - the new beta https://whitelisting.kaspersky.com/advisor?lang=en-US#search/4A1A5AC0E20C56C3A008AE99D1D2FAD2

Hi, How can I allow access for a program to edit the hosts file (C:\Windows\System32\drivers\etc\hosts)? Kind regards Axthorpe