When I turn on the computer in the morning, I double click the icon for Launcher.  The Win10 circle spins, and Launcher doesn't appear.  If I double click on the Launcher icon again, I get a message box telling me its already running, but it isn't on screen.  It was installed into c:\DXLAB\Launcher

 

If I go into Task Manager and kill the DXLauncher program, then double click it again to start it, same thing happens.  If I go in and fiddle with "Run as an Administrator", sometimes it starts and sometimes it doesn't.  

 

I'm figuring that I installed something incorrectly, but I can't find my error.  

+ That sounds like interference from your anti-malware. To see if that's the case, reboot Windows into "Safe mode with networking", and then start the Launcher. What happens?

+ You'll need to reboot Windows normally after performing the above experiment.

       73,

              Dave, AA6YQ

This is happening here also, after a win10 update. If I wait
3-4 mins it starts. If I try to just start DXKeeper without
starting Launcher, the same thing happens. Launcher takes 3-4 mins.
And then it takes 3-4 mins for DXKeeper to start.

+ That's almost certainly interference from your anti-malware, which you can confirm by temporarily rebooting Windows into "Safe Mode with Networking", if you wish.

+ Configure your anti-malware to consider each DXLab application to be "safe". If you're running Microsoft's Windows Defender, update it to the latest malware definitions:

https://www.microsoft.com/en-us/wdsi/definitions

     73,

           Dave, AA6YQ

When I restart in Safe Mode with Networking, DXLauncher 2.1.7  opens right away.

 

Once I reboot and go into the normal Win10 startup, the program takes a while to open.

I reported yesterday that it didn't display, but I discovered that my issue is just like N4UOZ's

issue- it starts, but after a delay of 3 1/2 minutes the Launcher WIndow appeared.   Once that

is on screen, Commander loads <5 sec, DXKeeper <8 seconds.  

 

DXLauncher also has a shield on it.

 

Windows 10 version 22H2.  I5-4570 CPU, 8Gb ram, 210Gb SSD.  WSJT starts in <3sec.

 

Once it is displayed, if I close it and then reopen it Launcher opens <1sec.

 

If I right click the icon, choose "Run as Administrator", the same delay is present.

If I right click the icon, choose Advanced, then click on "Run as Administrator", same delay.

 

I signed on as the administrator when I installed the program.

 

So far, no joy. 

+ You have identified the root cause of the problem: one of the applications that Windows starts automatically when booted "normally" is interfering with communication among your DXLab applications. The culprit is almost always your anti-malware. You must either configure it to consider each of your DXLab applications to be "safe"; if you can't do that, get help from the provider of your anti-malware. If they don't succeed, then you must remove your current anti-malware and replace it with something competent.

+ If you're using Windows Defender, updating it with Microsoft's current malware definitions should be sufficient:

https://www.microsoft.com/en-us/wdsi/definitions

      73,

           Dave, AA6YQ

When I restart in Safe Mode with Networking, DXLauncher 2.1.7  opens right away.

Once I reboot and go into the normal Win10 startup, the program takes a while to open.

I reported yesterday that it didn't display, but I discovered that my issue is just like N4UOZ's

issue- it starts, but after a delay of 3 1/2 minutes the Launcher WIndow appeared.   Once that

is on screen, Commander loads <5 sec, DXKeeper <8 seconds.  

DXLauncher also has a shield on it.

If I right click the icon, choose "Run as Administrator", the same delay is present.
If I right click the icon, choose Advanced, then click on "Run as
Administrator", same delay.

When I restart in Safe Mode with Networking, DXLauncher 2.1.7 opens right
away.
Once I reboot and go into the normal Win10 startup, the program takes a
while to open.
I reported yesterday that it didn't display, but I discovered that my issue
is just like N4UOZ's
issue- it starts, but after a delay of 3 1/2 minutes the Launcher WIndow
appeared. Once that
is on screen, Commander loads <5 sec, DXKeeper <8 seconds.
DXLauncher also has a shield on it.
Windows 10 version 22H2. I5-4570 CPU, 8Gb ram, 210Gb SSD. WSJT starts in
<3sec.
Once it is displayed, if I close it and then reopen it Launcher opens <1sec.
If I right click the icon, choose "Run as Administrator", the same delay is
present.
If I right click the icon, choose Advanced, then click on "Run as
Administrator", same delay.
I signed on as the administrator when I installed the program.
So far, no joy.
Dennis W1UE
On Thu, Feb 9, 2023 at 4:16 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

When I turn on the computer in the morning, I double click the icon for
Launcher. The Win10 circle spins, and Launcher doesn't appear. If I
double click on the Launcher icon again, I get a message box telling me its
already running, but it isn't on screen. It was installed into
c:\DXLAB\Launcher

If I go into Task Manager and kill the DXLauncher program, then double
click it again to start it, same thing happens. If I go in and fiddle with
"Run as an Administrator", sometimes it starts and sometimes it doesn't.

I'm figuring that I installed something incorrectly, but I can't find my
error.

+ That sounds like interference from your anti-malware. To see if that's
the case, reboot Windows into "Safe mode with networking", and then start
the Launcher. What happens?

+ You'll need to reboot Windows normally after performing the above
experiment.

73,

Dave, AA6YQ

> DXLauncher also has a shield on it.

That really looks like some kind of anti-malware

Something worth trying. Rather than starting Launcher immediately after starting/rebooting Windows. Delay the startup of Launcher for a few minutes to give Windows time to gets its house in order. Go and make a coffee or something so that you are not sitting fixated on what Windows is doing or not doing during its startup. After Windows has started and the PC usage has dropped to normal (idle) levels than start Launcher, does it start normally or are the delays still present?

Something worth trying. Rather than starting Launcher immediately
after starting/rebooting Windows. Delay the startup of Launcher for a
few minutes to give Windows time to gets its house in order. Go and
make a coffee or something so that you are not sitting fixated on what
Windows is doing or not doing during its startup. After Windows has
started and the PC usage has dropped to normal (idle) levels than
start Launcher, does it start normally or are the delays still present?

Once upon a time, it was possible to configure Windows to download updates and notify you that they are available, but no install them until you direct it to do so.