Version 2.3.0 64 bit will not install #install


Gary Liebisch
 

I have been using 64 bit version 2.1.2 since Dec 2019.  Today I downloaded 2.3.0 and it will not install.  Clicking on the executable does nothing. Cursor spins a couple of times and then stops.  Rebooted PC twice same result. Tried to run as administrator, same result.   Windows 10 Pro Version 1909.  Would be happy with ver 2.2 in the interim but can't find it to download.

Gary Liebisch
W8GEL
Powell, OH


Floyd Sense
 

Gary - I just installed it on my Win 10 Home 64 bit machine and it's running fine.  The only hitch was Windows Defender telling me it was unsafe to run, but ignoring that warning it installed properly.  Not sure what the Windows maintenance level is on my machine.


Bill Somerville
 

On 01/02/2021 19:46, Gary Liebisch wrote:
I have been using 64 bit version 2.1.2 since Dec 2019.  Today I downloaded 2.3.0 and it will not install.  Clicking on the executable does nothing. Cursor spins a couple of times and then stops.  Rebooted PC twice same result. Tried to run as administrator, same result.   Windows 10 Pro Version 1909.  Would be happy with ver 2.2 in the interim but can't find it to download.

Gary Liebisch
W8GEL
Powell, OH

Hi Gary,

no one else is reporting that issue, perhaps the downloaded installer is corrupt. Is there a Windows Event Log entry for the failure?

We do publish a file of SHA256 cryptographic hashes for each released file, you can use them to verify the downloaded installer.

You can get the SHA256 hash of your downloaded installer with this Windows PowerShell command:

Get-FileHash $Env:UserProfile/Downloads/wsjtx-2.3.0-win64.exe

Which should print:

5DE8E2B88389D1D33AA49D1A3AD54B292A0E50D1D358092BFE3AECE89B562A7B

The full list of hashes is available here: https://sourceforge.net/projects/wsjt/files/wsjtx-2.3.0/

73
Bill
G4WJS.


Herb Blue - WB8ASI
 

Download of 64 bit 2.3.0 went fine for me, but UDP to JTAlert and Grid Tracker having problems.  Went back to 2.2.2 and all OK again.  Will watch for comments and try again. 73, Herb WB8ASI


Mike Koralewski K8VA
 

I loaded 2.3.0 today... And yes it took a while, it's not an immediate install. It has to do a whole bunch of things in the windows registry., Have some patience... 
Also, I had to go to then settings "Audio" and re-check the Codex drivers...It was a little squirelly for a while,, but eventually everything clicked into place... 

--
73 Mike. K8VA


neil_zampella
 

Not having any issues here.   Did you check to make sure all the UDP checkboxes are still checked?  What are you using for a broadcast IP address?

Neil, KN3ILZ

On 2/1/2021 7:12 PM, Herb Blue - WB8ASI wrote:
Download of 64 bit 2.3.0 went fine for me, but UDP to JTAlert and Grid Tracker having problems.  Went back to 2.2.2 and all OK again.  Will watch for comments and try again. 73, Herb WB8ASI



m_scot_alex
 

Windows 10 Home (x64) Build 19041.685 
Intel Core i7-3610QM
16GB RAM
500GB SSD
NVIDIA GeForce GTX 660M
Windows Defender

After bypassing the initial Defender warning, v2.3.0 installed in about 60 seconds, including setting path options. Anyone experiencing much longer installation times are probably having to wait for their security solution to monitor the installation. As many have written, this is likely to get worse for hobby software as security software becomes increasingly aggressive.

73,

Mike - N8MSA 


Herb Blue - WB8ASI
 

Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI


Bill Somerville
 

On 02/02/2021 17:16, Herb Blue - WB8ASI wrote:
Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI

Hi Herb,

it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the default as a minimum. That defect is repaired for the next release, apologies for any confusion.

73
Bill
G4WJS.


Andy_501
 

I had similar experience trying to upgrade to latest version. Downloaded .deb file and did install and all it installs is message aggregator no wsjt-x

On 2021-02-02 11:19 a.m., Bill Somerville wrote:
On 02/02/2021 17:16, Herb Blue - WB8ASI wrote:
Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI

Hi Herb,

it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the default as a minimum. That defect is repaired for the next release, apologies for any confusion.

73
Bill
G4WJS.





Bill Somerville
 

Hi Andy,

that doesn't sound, in any way, similar. Can you explain exactly what went wrong? For example what does this command run from a terminal print:
which wsjtx
73
Bill
G4WJS.

On 02/02/2021 17:32, Andy_501 wrote:

I had similar experience trying to upgrade to latest version. Downloaded .deb file and did install and all it installs is message aggregator no wsjt-x

On 2021-02-02 11:19 a.m., Bill Somerville wrote:
On 02/02/2021 17:16, Herb Blue - WB8ASI wrote:
Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI

Hi Herb,

it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the default as a minimum. That defect is repaired for the next release, apologies for any confusion.

73
Bill
G4WJS.



Andy_501
 

Hi Bill,


I tried downloading the wsjt installer .deb file and having the debi installer install it but always just came back installing only message aggregator alone.

I completely purged older version and reran the same process again and it did the same thing aggregator only. So I purged it all and then just installed the package from the synaptic package manager ; it installed OK and runs but is the older version. Can't seem to get newer versions to install. OS here is ubuntustudio 20.04LTS

which wsjtx =  "/usr/bin/wsjtx"  <--- but this is after reinstalling from synaptic pkg manager.




On 2021-02-02 11:34 a.m., Bill Somerville wrote:
Hi Andy,

that doesn't sound, in any way, similar. Can you explain exactly what went wrong? For example what does this command run from a terminal print:
which wsjtx
73
Bill
G4WJS.

On 02/02/2021 17:32, Andy_501 wrote:

I had similar experience trying to upgrade to latest version. Downloaded .deb file and did install and all it installs is message aggregator no wsjt-x

On 2021-02-02 11:19 a.m., Bill Somerville wrote:
On 02/02/2021 17:16, Herb Blue - WB8ASI wrote:
Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI

Hi Herb,

it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the default as a minimum. That defect is repaired for the next release, apologies for any confusion.

73
Bill
G4WJS.






Bill Somerville
 

Hi Andy,

there will be conflicts if you have something from a repository using apt/aptitude/synaptic installed and then try to install our bare Debian package file. To get the latest v2.3.0 release I recommend removing any other version of WSJT-X and then installing our package using dpkg, or alternatively wait for the repo you were using to be updated, which may not take very long.

73
Bill
G4WJS.

On 02/02/2021 18:27, Andy_501 wrote:

Hi Bill,


I tried downloading the wsjt installer .deb file and having the debi installer install it but always just came back installing only message aggregator alone.

I completely purged older version and reran the same process again and it did the same thing aggregator only. So I purged it all and then just installed the package from the synaptic package manager ; it installed OK and runs but is the older version. Can't seem to get newer versions to install. OS here is ubuntustudio 20.04LTS

which wsjtx =  "/usr/bin/wsjtx"  <--- but this is after reinstalling from synaptic pkg manager.




On 2021-02-02 11:34 a.m., Bill Somerville wrote:
Hi Andy,

that doesn't sound, in any way, similar. Can you explain exactly what went wrong? For example what does this command run from a terminal print:
which wsjtx
73
Bill
G4WJS.

On 02/02/2021 17:32, Andy_501 wrote:

I had similar experience trying to upgrade to latest version. Downloaded .deb file and did install and all it installs is message aggregator no wsjt-x

On 2021-02-02 11:19 a.m., Bill Somerville wrote:
On 02/02/2021 17:16, Herb Blue - WB8ASI wrote:
Found the answer to my problem over on the HamApps Group.  Seems 2.3.0 has a couple new additional fields since 2.2.2.   In Settings>Reporting under the UDP Server setup, the new field "Outgoing interfaces:" was blank.  I changed it to the "loopback" choice, and also had to checkmark the "WSJT-X UDP Multicast on Loopback" Setting in JTAlert.  All is well again. 73, Herb WB8ASI

Hi Herb,

it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the default as a minimum. That defect is repaired for the next release, apologies for any confusion.

73
Bill
G4WJS.



Gary Liebisch
 

On Mon, Feb 1, 2021 at 02:28 PM, Bill Somerville wrote:
Get-FileHash $Env:UserProfile/Downloads/wsjtx-2.3.0-win64.exe
OK I did that, and yes got the same hash result as you suggested.  Also downloaded again.  Same result --what do I try next? I put Norton Security in "Silent Mode" and that did not help either.   If I remove my 2.1.2 then I have nothing that works, don't want to do that. 

 
--
Gary Liebisch
W8GEL
Powell, OH


Gary Liebisch
 

Also nothing in the event log relating to the install attempt.
--
Gary Liebisch
W8GEL
Powell, OH


Bill Somerville
 

On 03/02/2021 00:44, Gary Liebisch wrote:
On Mon, Feb 1, 2021 at 02:28 PM, Bill Somerville wrote:
Get-FileHash $Env:UserProfile/Downloads/wsjtx-2.3.0-win64.exe
OK I did that, and yes got the same hash result as you suggested.  Also downloaded again.  Same result --what do I try next? I put Norton Security in "Silent Mode" and that did not help either.   If I remove my 2.1.2 then I have nothing that works, don't want to do that. 

 
--
Gary Liebisch
W8GEL
Powell, OH

Hi Gary,

please try removing v2.1.2, you can always install it again, the installer is here: https://sourceforge.net/projects/wsjt/files/wsjtx-2.1.2/ if you need it.

73
Bill
G4WJS.


Gary Liebisch
 

I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


William Perry
 

I can’t install 2.3 either on Windows 10
N3VEZ 


On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


Bob Lewis
 

My Norton antivirus blocked it as “too new” and a potential threat. I just selected “install anyway” and it installed and runs fine on Windows 10. This is pretty safe if you know that you have downloaded it directly from the WSJT web site.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of William Perry
Sent: Wednesday, February 03, 2021 1:15 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Version 2.3.0 64 bit will not install #install

 

I can’t install 2.3 either on Windows 10

N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:

I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


neil_zampella
 

What are you using for an antivirus?   Are you sure you're getting a good download? 

Neil, KN3ILZ

On 2/3/2021 12:14 PM, William Perry wrote:
I can’t install 2.3 either on Windows 10
N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH