Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 915348" data-attributes="member: 32260">I investigated this issue a little on the AutoIt forum. The problem can be related to upgrading from Windows 8 or 8.1 to Windows 10 and still preserving the possibility to downgrade. In this situation, the AutoIt function recognizes that the system is not fully Windows 10. That is good for ConfigureDefender, because there could be a problem when the user did apply the advanced settings and next downgraded to Windows 8 or 8.1 (preserving the WD setup). These settings can be configured only by PowerShell ver. 5.0+ which is not present in Windows 8 and 8.1.So the current behavior of ConfigureDefender is in fact the safest for the user.I will add the info about it in the ConfigureDefender manual.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /></blockquote>

[QUOTE="Andy Ful, post: 915348, member: 32260"] I investigated this issue a little on the AutoIt forum. The problem can be related to upgrading from Windows 8 or 8.1 to Windows 10 and still preserving the possibility to downgrade. In this situation, the AutoIt function recognizes that the system is not fully Windows 10. That is good for ConfigureDefender, because there could be a problem when the user did apply the advanced settings and next downgraded to Windows 8 or 8.1 (preserving the WD setup). These settings can be configured only by PowerShell ver. 5.0+ which is not present in Windows 8 and 8.1. [B]So the current behavior of ConfigureDefender is in fact the safest for the user.[/B] I will add the info about it in the ConfigureDefender manual.(y) [/QUOTE]

Verification