Every bug report should contain three things – what you did, what you expected
to happen, and what actually happened.
You have two of the three. What actually happened?
Is the audio engine loading the version of the .dll in C:\windows\system32? Is
it trying to load the version of the .dll in the other location, but failing?
If it is failing, what is the error code?
Whenever you make a copy of the sample APO, it is very important to change the
APO CLSID. Otherwise, if your driver ends up on the same system as someone
else’s, your APO CLSIDs will collide, and there is no good possible outcome.
You will need to change the CLSID in both the APO implementation and in the COM
registration in the .inf.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Rajendra Sethi <rajendra.sethi11@xxxxxxxxx>
Sent: Monday, March 4, 2019 4:03:12 AM
To: Etienne Dechamps
Subject: [wdmaudiodev] Re: Why my apo dll is only loads from c:\windows\system32
Thanks for the suggestion.
On Mon, Mar 4, 2019 at 4:59 PM Etienne Dechamps
The Windows Audio Engine service that loads APO DLLs runs under
limited privileges and doesn't have access to large parts of the
To solve this problem, either make sure that service has the necessary
filesystem ACLs to access your APO DLL, or move the DLL to some
location the service has access to.
Pointing the Process Monitor tool to the audiodg.exe process is a good
way to troubleshoot this kind of problem.
On Mon, 4 Mar 2019 at 10:32, Rajendra Sethi
I am trying to load the apo dll which is a copy of windows sample swapapo
project from different location(not c:\windows\system32). But I am not able
to load the dll.
I am registering the DLL using regsvr32 "Location\swapapo.dll".
Thanks And Regards