- Aug 28, 2015
- 801
I was actually trying that and you are correct, it worked. Thanks.
You are welcome. Cheers.
I was actually trying that and you are correct, it worked. Thanks.
ConfigureDefender is a portable application. So, it does not need conventional updates. The changes related to available features will be included in the <INFO> on the Protection Level section.Hi,
I started using ConfigureDefender 3.0.1.1 high settings. I have two questions
1. How to proceed in case of an update? Is it updating itself or the new installer should be downloaded?
2. Tamper protection can be enabled or must be disabled as in the case of DefenderUI?
I did not find any answers to these questions in help file.
Thank you!
Thank you very much! It's clear.ConfigureDefender is a portable application. So, it does not need conventional updates. The changes related to available features will be included in the <INFO> on the Protection Level section.
It works with enabled Tamper Protection.
Hi Andy, weird glitch on W11. I downloaded the newest version from your link in the Firewall Hardening thread today. I deleted my older version of CD and moved new version to desktop, when I tried to open these 2 boxed popped up. Just to check I restored old version from Recycle Bin and same thing happened. This leads me to think that maybe its my computer although I've had no issues in the past.
View attachment 266754View attachment 266755
The error is due to a faulty Windows Update, and installing .NET 3.5 is the only solution available at the moment till MS fix it.This error was related to the PowerShell problem - PowerShell is a part of .NET Framework. ConfigureDefender executes PowerShell to get information about Defender settings. I am not sure if installing the old version of .NET Framework 3.5 could solve the problem. It is also possible that the problem was solved via Windows Update (update of .NET Framework).
This error could also appear if another security blocked PowerShell or blocked the execution of PowerShell as a child process of ConfigureDefender.
The flaw in this article is related to the applications that use .NET Framework 3.5. But, ConfigureDefender and PowerShell (on Windows 10/11) do not use .NET Framework 3.5 at all. Most computers with Windows 10/11 (including all my computers) do not have installed .NET Framework 3.5. So, why installing .NET Framework 3.5 could help?The error is due to a faulty Windows Update, and installing .NET 3.5 is the only solution available at the moment till MS fix it.
https://malwaretips.com/threads/mic...fixes-3-zero-days-75-flaws.113718/post-988045
There was a cumulative preview update which is the root cause of this issue. I don't know why .NET Framework 3.5 fixes it for affected users but that's how it is at the moment. Not everyone is having the issue. Looks like there's no update from Microsoft yet fixing it. So the update that was installed on your system on May 12 is not the fix for this. This was also installed on mine along with Patch Tuesday.The flaw in this article is related to the applications that use .NET Framework 3.5. But, ConfigureDefender and PowerShell (on Windows 10/11) do not use .NET Framework 3.5 at all. Most computers with Windows 10/11 (including all my computers) do not have installed .NET Framework 3.5. So, why installing .NET Framework 3.5 could help?
I cannot exclude that some updates could spoil the .NET Framework. In such a case installing .NET Framework 3.5 could possibly solve the issue. This issue is absent on my computer Windows 11 21H2 updated 12.05.2022 (Cumulative Update for .NET Framework Kb5013628). If there was a problem with .NET Framework then it was probably solved by this update.
Its the Windows update issue as only security on this computer is CD and SWH. Installing Framework 3.5 fixed it. Thanks.This error was related to the PowerShell problem - PowerShell is a part of .NET Framework. ConfigureDefender executes PowerShell to get information about Defender settings. I am not sure if installing the old version of .NET Framework 3.5 could solve the problem. It is also possible that the problem was solved via Windows Update (update of .NET Framework).
This error could also appear if another security blocked PowerShell or blocked the execution of PowerShell as a child process of ConfigureDefender.
The issue from the Bleepingcomputer article was limited to the .NET Framework 3.5 applications - the users had already installed .NET Framework 3.5 which was somewhat corrupted by the Windows Update. So, reinstalling the .NET Framework 3.5 was logical and could solve the issue. But, there was no issue with the current .NET Framework 4.0.30319.There was a cumulative preview update which is the root cause of this issue. I don't know why .NET Framework 3.5 fixes it for affected users but that's how it is at the moment.
You can wait until Microsoft will push a new cumulative update for the .NET Framework and then uninstall the legacy version .NET Framework 3.5 (except if you use applications that still use it). But you probably already know it.Its the Windows update issue as only security on this computer is CD and SWH. Installing Framework 3.5 fixed it. Thanks.
In most cases, the execution is postponed for about 6 sec. when the file is uploaded to the cloud. I use 20 sec to include bigger files and possible slowdowns. It is possible to use 60 sec. - the difference will be seen mostly for large installers.Hey,
I have a question regarding the High-mode of Configure Defender. Is there a reason that the Cloud Check Time Limit is at 20s while on Max it is 60s? I personally think, that even in High mode there would be no real issue for inexperienced users if the limit would be 60s too.
Alright, thanks for the fast replyIn most cases, the execution is postponed for about 6 sec. I use 20 sec to include bigger files and possible slowdowns. It is possible to use 60 sec. - the difference will be seen mostly for large installers.
Yes. It is not enabled by default and this probably means something. Anyway, I did not find any reported issues on the web. Sometimes I test it on my computer and it works without issues.I keep forgetting to write this and that is, Microsoft Defender doesn't run in sandbox anymore. It got automatically disabled on my system like a month ago, and I also tested installing fresh stable windows, beta builds and also dev builds. In all these builds, it's off by default on Windows 11.
Either performance issue or bugs made Microsoft do this. I previously shared here a couple of bugs related to this. So I'm not surprised tbh. Maybe it'll return in the future. Of course, anyone can still manually enable it, but I don't think that's recommended.
What I mean is, it's used to come enabled by default on Windows 11, but not anymore.Yes. It is not enabled by default and this probably means something. Anyway, I did not find any reported issues on the web. Sometimes I test it on my computer and it works without issues.
For now, it is not yet included in the ConfigureDefender settings.