![block adobe hosts windows 10 block adobe hosts windows 10](https://winaero.com/blog/wp-content/uploads/2016/11/disable-tips-about-Windows-10.png)
I also realize that the issue apparently here is blocking only.īut with that said, what about independent developers running their own web application on their machine ? If you're a web developer and you do your coding locally, it makes sense to use your host file to send a domain like to 127.0.0.1.Īgain, I know it looks like Windows 8 won't interfere with that. I agree that for blocking or for network-wide control using HOSTS is a horrible idea. I don't fucking CARE that it's used for malware. Whatever the user puts in there, should work as intended. Hosts was never meant to be used for blocking sites, but it works well enough as a consequence and the behaviour should be left alone. THIS is a prime example of why the hosts file still exists and the behaviour should not be fucked with by those assclowns at Microsoft. I make use of the hosts file for various purposes, including getting my forum users set up with hosts file entries to the new server, beforehand, whenever our DNS entries are changing so they can still reach the forum while changes are propagating. We expect implementations of the TCP/IP protocol in clients to behave in established ways and Microsoft has no right to change that. Microsoft can't "kill the hosts file off" because the behaviour is part of the IP specification (defined in the RFC's) 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.These people defending MIcrosoft's behaviour are just tools.
BLOCK ADOBE HOSTS WINDOWS 10 SOFTWARE
I do no expect Kaspersky to handle beta software correctly. I understand that this is not Kasperskys problem. I have been able to get it running by setting “Do not monitor application activity” (see image below). I wrote this hoping to get some information to send back to Flywheel, the maker of programs.
![block adobe hosts windows 10 block adobe hosts windows 10](https://i1.wp.com/pureinfotech.com/wp-content/uploads/2017/08/edit-hosts-file-windows-10.jpg)
This has become two issues, but for me it is one that matters the most. Ok, apparently I was a bit unclear above )Īnd I thank you for your will to investigate this I have found two differences, that may or may not affect the “write block” 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).
![block adobe hosts windows 10 block adobe hosts windows 10](https://i2.wp.com/www.nextofwindows.com/wp-content/uploads/2017/06/Where-is-the-hosts-file.png)
This feels like a very temporary solution… 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. 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”. This program works fine and I have not needed to anything to get it to work, Kaspersky does nothing.īut 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 they need to edit the hosts file when setting up new sites locally. 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. Yes, I get and error when the program tries to modify C:\Windows\System32\drivers\etc\hosts