-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WASAPI Capture Catastrophic Failure #1187
Comments
@cryingsauerkraut Windows Services has no access to Users mic input in WasapiCapture. |
@rdyhalt It's worked on all versions of Windows prior to a recent update, so I don't think it's intended, it seems to be a regression. |
@cryingsauerkraut the problem from a Windows Service is that a User Session can be a Remote Desktop, Citrix Desktop or any other virtual disktop and not only Console Desktop. In Remote Desktop and Citrix Dekstop, there can be 100s of users online on the same Windows. So, what WasapiCapture interface to use ? Perhaps try to liste all device, when running in Windows Service ?
|
@rdyhalt, running that snippet on my test machine with the project deployed and running as a service I get:
When the project is run in debug mode from Visual Studio the output is the same. It may be worth noting that I also experience a similar error when I try recording from the mic with WaveIn. WaveIn also works when running from Visual Studio and not when deployed. |
My guess will be, that a call to Try point out what MMDevice to use, both in when you try it in Visual Studio and as Windows Service. |
I still get the catastrophic failure hresult when explicitly creating the capture with a specific, plugged in, capture device. I have seen the COM exception when there's no default capture device before and handle it in the catch block omitted from my initial snippet, and it's a different hresult. That was back when the application was functioning before it was broken by a Windows update. |
Attempting to start a WASAPI capture with the default constructor returns an exception from hresult 0x8000FFFF, Catastrophic failure when called from a Windows service. Since the latest Windows 11 update, my app has been crashing on trying to start a WASAPI mic capture and is deployed as a self contained, single file Windows service.
Initializing the capture:
And the result is:
This only happens when the application is deployed as a service, it runs fine when running from Visual Studio. I've been spinning my wheels on this problem for months, does anyone have any ideas?
The text was updated successfully, but these errors were encountered: