It was fairly consistent and I reported it (with screenshots) to Microsoft and eventually it stopped happening-probably from sheer coincidence. In fact, by just running it, I had what sounded like two audio channels competing for control of the audio "fix itself." I suspect that by running the troubleshooter's different tests, some internal virtual circuit got kicked. I also e mailed Focusrite so lets see.įrom my experience over the past several months, the Win 10 Sound Troubleshooter has worked to solve problems, even when it claims in didn't detect the problem. Without wanting to be defeatist, I've used Windows for years and have never seen any Troubleshooter sort anything out! But you never know.if either works I'll post.
If you don't find an anti-malware program, go ahead and try the elevated privilege thing anyway. You don't have to try them in the order I suggest. EXE again and select Run as Administrator. If so, check that box to unblock it and then click OK. In the resulting page, you may see a notice down at the bottom that says "Security: This file came from another computer." etc. EXE file in your download folder and select Properties. One of the icons down there may be for an anti-malware program that you can temporarily disable while you install the driver.Īs for the second, you can try running the installer with elevated Administrator privileges. There might be a "^" icon as well that you can click on to see more system tray programs. To check for the first, you can look in the system tray in the lower right corner where your clock and sound icon and all that other stuff is. These are the most common causes I've seen for this problem. My first two: your system may have anti-malware software that detects installation of drivers and removes them at next system restart, or your Windows user account may not have sufficient privileges when running the installer.
I can only take educated guesses as to why this happens. That's what the trouble is, and what we need to solve. This works just fine, but then you restart the computer, and the computer behaves as if the driver had never been installed. At that point, your system, including Cakewalk, should happily recognise that you have a Focusrite audio interface installed. You have downloaded the driver package for your Focusrite interface, and by running it, you install the driver. The behavior you are witnessing is not normal. That's a good attitude to go with: building a DAW is something of a project, so it may take a bit of fiddling and you may need to learn a thing or two about subjects you don't really care about.
0 kommentar(er)
