FlexVSP Disappeared

N1UW

My fault, I know.  Somehow in the process of upgrading to SmartSDR 1.9.13 (and deleting the previous version) I disappeared FlexVSP.  I ran the SmartSDR 1.9.13 installer again but FlexVSP is still not installed.

The 6500 works fine with SmartSDR but I cannot get my sound card apps to transmit, etc.

The Flex virtual ports show up in Device Manager with the yellow warning triangles.  The ftv drivers all appear to be in the WINDOWSsystem32drivers folder.  Using Win10.

How do I reinstall FlexVSP?

Jim Gilliam

Once you get this problem resolved, consider making a hard drive image of your computer. From what I have read, you need to methodically eliminate all vestiges of SmartSDR and reinstall....or you could spend 10 minutes reimaging your computer.

Jim, k6QE

Tim - W4TME

Try this
https://helpdesk.flexradio.com/hc/en-us/articles/205665325-How-to-Repair-the-FlexVSP-Virtual-Serial-...

Kevin

I'm not sure this will help but I recently had problems with parts of SSDR and its components left behind. It had to do with soundcards but maybe the solution the Flex helpdesk suggested to me could help you. They asked me to install and run Revo uninstaller.

I hate uninstallers, registry cleaners, speeder uppers, etc. But, I have to admit, my soundcard issue (ghost devices) is gone and I was able to do a clean installation of SSDR 1.9.13 including CAT, DAX and FlexVSP (as I had that removed during the uninstall).

Oh, and backups are an excellent recovery method though I'm not sure it only takes 10 minutes to reimage. Maybe system snapshots before install? Can you can go back to a previous snapshot?

Best of luck!

Kev K4VD

Tim - W4TME

I have read, you need to methodically eliminate all vestiges of SmartSDR and reinstall....or you could spend 10 minutes reimaging your computer.

THIS IS NOT TRUE!!!!  Please this is disinformation that causes problems.  People think they have to start deleting things and this is what messes up drivers and makes recovery difficult.

N1UW

FlexVSP is not there to repair.  It is not in the list of installed programs.

Jim Gilliam

https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSD...

Am I to assume not to use the above information or when does it apply and not apply?

Jim, K6QE

Tim - W4TME

It applies when you upgrade to Windows 10.

Tim - W4TME

Not certain what has occurred to your PC, but the FlexVSP service is no longer installed, but the PC still thinks it is which is preventing it from being installed. I recommend that you open a HelpDesk Support ticket so we can address this issue with you one-on-one.

Jim Gilliam

I am not trying to be cute, just learn. Does that mean when I have installed Windows 10, I should not use the uninstall program?

Jim Gilliam

Backup is not quite the correct term as that implies just backing up files. Imaging is putting the disk back to the time it is imaged. If one uses USB drives for imaging and restoration, it can take as long as an hour. If you have installed a second SSD SATA drive in your computer a restoration is extremely fast and I typically restore in less than five minutes.

Tim - W4TME

This procedure was written to provide a way to completely remove all of SmartSDR from a PC before the operating system is upgraded to Windows 10. SmartSDR needed to be removed prior to the upgrade to Windows 10 because the upgrade process did not properly update the SmartSDR components. If you are already running Windows 10, you have already upgraded.

N1UW

Wilco.  I failed to mention before that SmartSDR CAT launches when the computer starts up.  I don't know if FlexVSP and SmartSDR CAT are related.

Tim - W4TME

Very related. FlexVSP provides the virtual com ports that CAT uses. If FlexVSP is not working properly, CAT will not start.

Jim Gilliam

That doesn't answer my question. I have had Windows 10 and when Windows 10 upgraded my SmartSDR went to **** in a hand basket. I followed your procedure to uninstall SmartSDR and reinstalled and everything worked. Now you are saying not to do a complete uninstall because it might corrupt drivers, etc. I am very confused with your answers.

Jim, K6QE

Tim - W4TME

The procedure listed in the HelpDesk for completely uninstalling SmartSDR is a "nuclear option" of last resort in most cases.  This procedure (usually) works regardless of the issues that may arise from an operating system "upgrades".

So let's look at this terminology of Windows "upgrades".

With Windows 10, they use the same terminology for two different processes; upgrading from one operating system version, such as Win7 to a new version, Windows 10 and for major changes to Windows 10 (this used to be known as service packs a long time ago).

For the first type of "upgrade" completely removing SmartSDR from your Win7 (Vista or Win8) PC before upgrading to Win10 is essentially a requirement.

For the 2nd type of "upgrade", an upgrade from one minor version of Win10 to another, it is not a requirement.  Usually what breaks during this type of "upgrade" are the virtual kernel mode drivers (FlexVSP and DAX) and they can be easily "repaired" or manually re-installed.  Completely removing SmartSDR and reinstalling is usually not necessary.

You stated, "you need to methodically eliminate all vestiges of SmartSDR and reinstall..." in the context of this post which was an issue Frank (N1UW) experienced upgrading SmartSDR, not from either of the two Windows upgrade events.  This implies that you have to use the "nuclear option" to completely remove SmartSDR when upgrading to SmartSDR and that is just not true.

As part of my work here at FlexRadio, I test all sorts of code changes.  I have literally installed hundreds of version of SmartSDR; alpha, betas, development, and feature releases in addition to the public releases.  Not once have I ever had to resort to the "nuclear option" for eliminating all vestiges of SmartSDR to install or get a version of SmartSDR to work.  It just isn't necessary.

However, we field more than a few support incidents where users have been following this advice, using said procedure, and end up in situations where they cannot get SmartSDR to work properly. Sometimes issues are compounded by manually trying to force remove SmartSDR components.  This always results in a less than satisfactory user experience.

My point is, completely removing SmartSDR from your PC using the procedure in the HelpDesk is not necessary and can result in making matters worse.  I am trying to correct this misconception that you have to go through a convoluted process of completely removing SmartSDR to upgrade to a new version of SmartSDR when it isn't necessary.

The only time I ever recommend the "nuclear option" in the context of upgrading to a new version of SmartSDR is when users have many old versions of SmartSDR loaded on their PC and they want to do some serious house cleaning.  In this case, removing everything so that you can perform a "clean" install can provide some benefit.

Jim Gilliam

Well, I think this whole thing is a bloody mess. I have 9 versions of SmartSDR lingering in my computer and I am afraid to touch them because I don't want have to go through the throes of this so-called "nuclear option." It would be  nice if your company could provide an auto uninstall of your program before installing a new one. I have made this statement several times and will continue to do so.

Jim, K6QE

Rick Hadley - W0FG

Revo Uninstaller Pro makes a full and complete uninstall of SSDR or any other program, including searching for leftover files and folders, and cleaning the registery, simple.  I use it to do a full wipe each time before I install a new version of SSDR.  That way I have no traces left.  I'm sure Tim will say its overkill, but it's worked very well for me.

Tim - W4TME

Jim - we do have an uninstall option; I use it all the time.  You just have to run it.  Unfortunately, Windows 10 hides the option from the Program Files menu, so you have to go to Change Remove Programs, select the app and chose the uninstall option.  When prompted, do NOT uninstall the DAX drivers.

Tim - W4TME

Issue resolved via the HelpDesk.  Windows was not allowing the service installer to run.