Re: Windows 10 Start menu does not list Commander
|
Ed, that is great that it's working for you again.
However, if you don't add an exception you may need to repeat these steps again in the future. Not everyone is comfortable adding exceptions to their virus protection.
If you decide to add the exceptions, in the same window where you found the current threats, click on Manage Settings under Virus & Threat protection settings.
Scroll down to Exclusions, and click Add or remove exclusions.
Click on Add an exclusion, and choose the type of exclusion to add. Some will exclude an entire directory. What I typically do is try to only do the file needed, and go from there if it doesn't solve the problem.
I have added an exclusion for the executable file for each DXLab application that I run (C:\DXLab\Commander\CI-V Commander.exe, C:\DXLab\DXKeeper\DXKeeper.exe, etc.)
On Tue, Apr 7, 2020 at 12:41 PM Ed < wa6wgs@...> wrote: For me, Dave was right on the money.
In WIN10 Search for:
Search/Security at a glance in Win10
Click on Virus&Threat protection
Click on Current threats/Protection history
Looking at All recent items/in my case, There were Threats blocked marked Severe/click on down arrow beside each threat/at the bottom of the new window, there is a selection ( it was restore or allow) choose .
In my case, I had 4 threats, all for Commander. I cleared all 4 of them.
Now commander 14.5.5 shows up in DXlab launcher Configuration
Was able to upgrade to 14.5.5
DXLab Launcher 2.1.2 now brings up commander 14.5.5 as it should.
In my case, all is now well and good at this end.
Thanks Dave for all you do!!!!!!
ED? WA6WGS
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave AA6YQ
Sent: Tuesday, April 7, 2020 1:12 AM
To: [email protected]
Subject: Re: [DXLab] Windows 10 Start menu does not list Commander
+ AA6YQ comments below
I've found that MS virus shield identify CI_V Commander executable as a trojan.
And put C:\DXLab\Commander\CI-V Commander1453.exe in quarantine.
This is the problem:
+ See <>
+ After you satisfy yourself that Commander1453.exe is not infected, direct your anti-malware to "unquarantine" it.
? ? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
