- This topic has 7 replies, 3 voices, and was last updated 2 years, 11 months ago by
.
-
Posts
-
I am running BAE 1.40.03 on Windows 8.1 64bit. I ran the “uninstall_breakaway” but this fails. It appeared that I’d need to manually uninstall. I attempted to remove all elements of “breakaway” and “vaclcskd” from the registry and from “C:\Windows…” and in “C:\Users\<username>\AppData”. Running the v1.42.00 installer results in pipeline fails to install. I’d imagine I haven’t fully uninstalled the previous. I imaged the computer just before attempting this “scary stuff” so I recovered the original drive after messing up the uninstall/install so now I have a second chance to try this. The current BAE v1.40.03 is installed in “C:\Breakaway” because the original install location “C:\Program Files (x86)” was having problems with the INI not being written (on this machine originally with Win7pro 32bit).
Are there any suggestions for uninstalling manually? Is there a different uninstaller that might work here?
Side note: Had this same issue on a different machine with Win10 Pro where I was able to manually uninstall and then install the latest.
I am not aware of any problems with Windows 8.1. It has been around long enough for these problems to have come to light and be fixed long ago. There was an issue with the latest version not playing happily with one update of Windows 10, particularly the Virtual Audio Cables (“pipeline”) bundled with it.
This has now been fixed, but the actual version still up on their website does not yet include the fix. I have no control over the website, but I have brought it to their notice. I repeat, the issue was only with one Windows 10 update (20H2).
If possible, uninstall both BAE and VAC through control Panel add/remove programs, and then install.
So… In control panel “add/remove programs” there is no entry for the VAC. Only “Breakaway” shows up here. I cleaned my Windows 8.1 Pro 64-bit as much as possible and then decided to attempt a second uninstall. To remove the VAC drivers I opened Device Manager and went to “Audio inputs and outputs” and “uninstalled” the two Breakaway Pipeline entries which appeared to work. Breakaway Pipeline also showed up under “Sound, video and game controllers” in the Device Manager also. I right-clicked and did an uninstall here. This popped up a message warning about the uninstall with a check box to remove the drivers (I selected this). That appeared to function. Now going to the add/remove programs I selected Breakaway and this uninstalled fine this time. I then checked for any “Breakaway” or “Pipeline” entries in the registry and they seemed to be gone here. After restarting several times and updating any apps on the machine I decided to install v1.42.00 and again it fails.
The v1.42.00 install window details were as follows:
Output folder: C:\Program Files (x86)\Breakaway
Create folder: C:\Program Files (x86)\Breakaway
Extract: vaclcskd.inf… 100%
Extract: vaclcskd.cat… 100%
Extract: wdmdrvmgr.exe… 100%
Output folder: C:\Program Files (x86)\Breakaway\x64
Create folder: C:\Program Files (x86)\Breakaway\x64
Extract: vaclcskd.sys… 100%
Output folder: C:\Program Files (x86)\Breakaway
Execute: “C:\Program Files (x86)\Breakaway\wdmdrvmgr.exe” -q -e -h Root\{b9828378-6ae0-489a-a3d1-c3dfba538766}\0000 -i BreakawayPipeline_b9828378-6ae0-489a-a3d1-c3dfba538766 “C:\Program Files (x86)\Breakaway\vaclcskd.inf”
Delete file: C:\Program Files (x86)\Breakaway\x64\vaclcskd.sys
Remove folder: C:\Program Files (x86)\Breakaway\x64\
Delete file: C:\Program Files (x86)\Breakaway\vaclcskd.inf
Delete file: C:\Program Files (x86)\Breakaway\vaclcskd.cat
Delete file: C:\Program Files (x86)\Breakaway\wdmdrvmgr.exe
Output folder: C:\Users\RADIOS~1\AppData\Local\Temp
Remove folder: C:\Program Files (x86)\Breakaway\So… I decided to re-install v1.40.03 and that worked perfectly.
It appears that the installer for v1.42.00 has the issue on Windows 8.1 Pro 64-bit. Hopefully they can update the installer on the website shortly. Unless there is another way to install the new Breakaway (and the new Pipeline).
OK, thank you for the detailed information. I’ll pass it on and seek a resolution. It appears that what was needed to fix Win10 has broken Win8.
Thanks,
Retested a third time and used CCleaner (yikes!) to see if it could find some registry keys that point to strange locations (didn’t find anything that I’d let CCleaner touch). Retried the install and v1.42.00 will not work. Must by something in the registry still blocking the install. v1.40.03 does install reliably we’ll leave it there for a while.
Thanks for looking into it.
Looks like it’s a problem with the VAC install indeed, you should maybe check out this thread [1], with a presumably updated version of Breakaway Pipeline. As I mentioned there, the Breakaway installer will still complain about an “older” version of Pipeline (which is wrong) but maybe you can copy over the install files from another machine, like I did.
I have raised this issue with Leif, and he has responded that he will take care of it. However, he also pointed out that there is absolutely NO advantage in installing the latest version on a Windows 8 PC. The update to 1.42 was to address a Windows 10 problem after a Microsoft update, but the BAE code was unchanged, only the VAC version.
As pointed out, version 1.40.03, which was the current version when Win 8 was the dominant OS, works perfectly.Thanks, that’s the answer I was looking for… If there’s no processing differences (BAE 1.40.03 works very nicely as is) I will leave as is on Win 8.1. After the second uninstall/reinstall BAE is installed normally in “C:\Program Files (x86)\Breakaway” and the INI is located at “C:\Users\<username>\AppData\Local\VirtualStore\Program Files (x86)\Breakaway”. That seems a little odd and fairly hidden (and may be located by a Microsoft preference rather than the BAE installer) it appears to be storing and retrieving the configurations on stop/start.
Sorry for the slow response…
Thanks for the help.
- You must be logged in to reply to this topic.