- Jan 27, 2018
- 1,401
Thanks Andy.Interesting. Is the block present if you open Microsoft Store and do nothing?
Please, wait - I have noticed the same now on my computer. I will try to investigate what it means.
Thanks Andy.Interesting. Is the block present if you open Microsoft Store and do nothing?
Please, wait - I have noticed the same now on my computer. I will try to investigate what it means.
SWHThank you. I guess this happens when I go to the Microsoft store and update my apps.
I made some research. The block is for WindowsPackageManagerServer.exe. It can be important for developers who are going to submit their applications to Microsoft Store. When opening, the Microsoft Store tries to access it.Yes.
SWH thenDon't use HC.
True. Everything in the Microsoft Store can be updated manually or automatically as usual. No issues on my computer.I made some research. The block is for WindowsPackageManagerServer.exe. It can be important for developers who are going to submit their applications to Microsoft Store. When opening, the Microsoft Store tries to access it.
This block can be ignored for home users. The updates and installations of UWP apps are not impacted.
I join this.Anyway, it would be good to get rid of it.
Agreed. Quite a pain to manually check for updates for every single hardening tool like SWH, ConfigureDefender, Firewall Hardening etc.I have a feature request for SWH.
Add an option or button in SWH to check for updates or to auto update(Delete previous version and download new one.)
Thats great. Looking forward to it.I have this in my plans.
Nice.This will require some important changes with my repositories on GitHub and MT threads, so I am not sure when it will happen. I am thinking about adding FirewallHardening and RunBySmartScreen to the SWH repository. So, there will be two main repositories: ConfigureDefender and SWH (with DocumentsAntiExploit, FirewallHardening, and RunBySmartscreen).
Seems like a good plan to me.This will require some important changes with my repositories on GitHub and MT threads, so I am not sure when it will happen. I am thinking about adding FirewallHardening and RunBySmartScreen to the SWH repository. So, there will be two main repositories: ConfigureDefender and SWH (with DocumentsAntiExploit, FirewallHardening, and RunBySmartscreen).
Or H_C and standalone (everything else!) tools repositories.This will require some important changes with my repositories on GitHub and MT threads, so I am not sure when it will happen. I am thinking about adding FirewallHardening and RunBySmartScreen to the SWH repository. So, there will be two main repositories: ConfigureDefender and SWH (with DocumentsAntiExploit, FirewallHardening, and RunBySmartscreen).
It is not possible. The H_C must be installed (not a portable application) and the standalone tools like ConfigureDefender, SWH, etc. are portable applications.Maybe H_C could get big buttons that would do the stuff SWH could do (with or without DocumentsAntiExploit, FirewallHardening, and RunBySmartscreen) and the normal (like they are now option) H_C option/settings would just be accessible with a small "advanced user I know the risks" button.
SWH can block such attacks by default due to the special SRP restrictions for shortcuts. The shortcuts are rarely restricted in the business environment even for USB drives. Furthermore, the Applocker and Microsoft Application Control cannot block shortcuts and most administrators do not know how to effectively manage the shortcuts via SRP.
Thanks Andy. I guess no need to block additional Sponsors such as msiexec.exe or odbcconf.exe?
EDIT
Oops this is the SWH thread. I was thinking of H_C which I use, so I'm not even sure if my question can also apply to SWH.