Page 1 of 1

WIN 10 update clash

Posted: Fri May 11, 2018 3:33 pm
by RichardG062
I have just carried out a windows 10 update version 1803. However now when I try to run the software the program hangs. I also have no sound, I am using VB Cable this also appears to have been affected - has anyone else had problems or suggest a solution

Regards

Richard

Re: WIN 10 update clash - UPDAYE

Posted: Fri May 11, 2018 5:59 pm
by RichardG062
OK so after unplugging and then reconnecting each of my RSP1A receivers |I now have the software working again. Still having issues with VB Cable producing no sound despite uninstalling and reinstalling but will pot this question on VB Cable's forum

Regards

Richard

Re: WIN 10 update clash

Posted: Fri May 11, 2018 6:35 pm
by Mike2459
This may be helpful, particularly the comments from VincentBurel.

https://answers.microsoft.com/en-us/win ... 6cd2fcdc79

Re: WIN 10 update clash

Posted: Fri May 11, 2018 10:10 pm
by G7JTT
unistall VB then reinstall worked for me

Re: WIN 10 update clash

Posted: Fri May 11, 2018 10:26 pm
by rob67
This worked for me with VB Cable.In your privacy settings in Windows 10 (after update 1803).Go to your Microphone settings and make sure "Allow access to the microphone on this device" is ON.Also go to "Allow apps to access your microphone" and make sure this is ON.Good Luck.Rob

Re: WIN 10 update clash

Posted: Fri May 11, 2018 11:43 pm
by maximusmike55
Something definitely happened to VAC in the latest Win 10 update. I had 6 VRX in SDRUno connected to 6 copies of MultiPSK with 6 Virtual Audio Cables numbered 1 thru 6.

After the update all of the VAC links were still there, but originally VRX-1 was connected to MultiPSK 1 via VAC-1 etc, but after the update all of the links were mixed up and I had to reset them all. Nothing was broken, it was just the VAC channel numbers appear to have been jumbled up.

Mike

Re: WIN 10 update clash

Posted: Sat May 12, 2018 8:40 am
by DanubeBCL
As Rob already mentioned Windows 10/1803 has changed permissions to access the recording devices of any soundcard in the system. Not only the microphone is affected.
The word "microphone" is misleading, in fact all recordings devices are blocked unless apps are granted permission to use the microphone in the privacy settings of Windows.
The word "apps" is also misleading as it affects all applications, not only those listed under the Windows privacy setting.
Many ham radio, BCL and audio programmes stopped working after Windows 10/1803 update. Among them:
PowerSDR
fldigi, WSJT-X and similar
Dream.exe (for DRM radio decoding)
Audacity ...
In most cases the applications all of a sudden reported a "PortAudio Error" as many of "our" programmes are compiled with PortAudio libraries. Other programmes simply did not work with the soundcard without giving an error message.

Thus, when you have trouble with soundcards after the Windows 10/1803 update, you should indeed check your privacy settings for the microphone! (Even if you do not use a microphone at all.)

73s, Heinrich