Windows 10 1903 update breaks VSPE

User avatar
W1JA
Posts: 28
Joined: Sun Apr 09, 2017 3:19 pm

Windows 10 1903 update breaks VSPE

Postby W1JA » Thu Jul 18, 2019 3:31 pm

I use Eterlogic VSPE to connect Thetis to DXLab Commander and N1MM+ for CAT control. After I updated Windows 10 on my shack PC to version 1903, the communications between these devices stopped, and CPU usage increased to nearly 100% whenever Thetis was running.

It turned out that VSPE was the problem, and they already fixed the issue. On June 4 they released their version 0.940.5.097, which "fixed issues with the latest Windows 10 update," it says on their website http://www.eterlogic.com/Products.VSPE.html

I upgraded to the latest version (now 0.941.5.134) instead of 0.940.5.097, and it fixed the problem.
User avatar
w-u-2-o
Posts: 1895
Joined: Fri Mar 10, 2017 1:47 pm

Re: Windows 10 1903 update breaks VSPE

Postby w-u-2-o » Thu Jul 18, 2019 5:05 pm

Thanks for the "heads up" on this! I will try to update BEFORE getting hit with 1903!
Segrest
Posts: 16
Joined: Sun Apr 09, 2017 3:05 pm
Location: Rixeyville, VA, USA - FM08xn

Re: Windows 10 1903 update breaks VSPE

Postby Segrest » Thu Jul 18, 2019 5:16 pm

It may also be worth mentioning that you must reboot your system after updating the VSPE application...

Bob
KO2F
User avatar
w-u-2-o
Posts: 1895
Joined: Fri Mar 10, 2017 1:47 pm

Re: Windows 10 1903 update breaks VSPE

Postby w-u-2-o » Thu Jul 18, 2019 7:16 pm

I had to re-enter my licensing information.

Also, if you have a script that automatically starts VSPE on startup you may need to modify it (I did) because the folder arrangement is now different after the new install.
ik7ytt
Posts: 48
Joined: Tue Mar 12, 2019 11:48 am

Re: Windows 10 1903 update breaks VSPE

Postby ik7ytt » Thu Aug 01, 2019 8:03 pm

same problem if you Virtual audio Cable software by

i have to reinstall and restart the engine....this is the explenation by the software developer


The problem is that upgrading Windows from a release to release is a
very complicated procedure. Instead of replacing only particular
components on Windows Update, the upgrade process rebuilds Windows
from scratch. To prevent you from reinstalling all the software,
Windows tries to reproduce user's software files and settings in the
new system installation. For user-mode software, it is usually
successful, but VAC contains a kernel-mode driver, and every driver
requires a special installation process, so some drivers may not be
migrated automatically, and require a reinstallation.

In addition, after an upgrade you got a completely new Windows
installation. Some internal settings that were optimized in the
previous installation, may be altered, so the new system may behave
slightly differently, and may need a tuning to become optimized again.

A software vendor cannot affect these issues. All upgrade actions are
performed by Windows itself, with no user's software intervention.

4.60 is quite stable, but 4.15 is stable too. In a correct
environment, both of them work perfectly. But you can upgrade VAC to
4.60 to get advantages of its new features.

With best regards,
Eugene

Return to “Digital Mode, Rig Control & Logging Software”