I know. Been there done that.
The process that loads your APO (audiodg.exe) is running under the Local
Service account.. It usually does NOT have access to user profiles.
Second. The APO should be packaged and deployed as part of an audio driver
package and thus ends up in the System32 directory where it belongs.
So when you are experimenting and doing your dev put it in a separate
folder away from the user profiles and make sure Local Service has access.
Den ons. 24. jul. 2019 kl. 19.03 skrev Matthew van Eerde <
I don’t know. If you can share logs of a failed attempt to load your APO
from the user directory that might shed light on the matter.
*From:* wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx>
on behalf of Artem <smirnoff.artem@xxxxxxxxx>
*Sent:* Wednesday, July 24, 2019 1:24:23 AM
*To:* wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
*Subject:* [wdmaudiodev] APO not loaded from user home directory
I'm experimenting with APO and found that audio service doesn't load
APO from user home directory (where development takes place).
Is this by design? Are there any other limitations on place & security
rights for APO to be loaded?
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx ;<wdmaudiodev@xxxxxxxxxxxxx>
URL to WDMAUDIODEV page: