Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 905170" data-attributes="member: 32260">Thanks for reporting.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />WD blocks access to the installer so &quot;Install By SmartScreen&quot; cannot work. You cannot also copy the file to another location. Adding the ASR exclusions for blocked installers will not solve the problem because the next installer will be blocked, too. Whitelisting in H_C cannot help, because this block is not related to SRP.As I noted in one of my previous posts, the simple solution is setting the prevalence ASR rule to Audit, run the installer to update (reboot or Log off not necessary), and finally run the updated application. Next, you can set this ASR rule to ON again. WD will remember that it should not be blocked.Edit.The file pb-setup-x64-6.1.0801 is now allowed by ASR on my computer.It was pushed to Softpedia 15.09.2020, so the block has lasted 2 days.</blockquote>

[QUOTE="Andy Ful, post: 905170, member: 32260"] Thanks for reporting.:) WD blocks access to the installer so "Install By SmartScreen" cannot work. You cannot also copy the file to another location. Adding the ASR exclusions for blocked installers will not solve the problem because the next installer will be blocked, too. Whitelisting in H_C cannot help, because this block is not related to SRP. As I noted in one of my previous posts, the simple solution is setting the prevalence ASR rule to Audit, run the installer to update (reboot or Log off not necessary), and finally run the updated application. Next, you can set this ASR rule to ON again. WD will remember that it should not be blocked. Edit. [B]The file pb-setup-x64-6.1.0801 is now allowed by ASR on my computer. It was pushed to Softpedia 15.09.2020, so the block has lasted 2 days.[/B] [/QUOTE]

Verification