Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 989266" data-attributes="member: 32260">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? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure&nbsp; &nbsp; :unsure:" loading="lazy" data-shortname=":unsure:" />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.</blockquote>

[QUOTE="Andy Ful, post: 989266, member: 32260"] 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? :unsure: 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. [/QUOTE]

Verification