APOProcess function is not called.

Takayama Shin-ichi 116 Reputation points
2021-02-01T09:04:41.03+00:00

I am making a custom APO. However, the process does not go through the APOProcess function.

APO is made based on the following sample code.
(Added DllRegisterServer function and DllUnregisterServer function)
https://learn.microsoft.com/en-us/samples/microsoft/windows-driver-samples/sysvad-virtual-audio-device-driver-sample/

The sample code above does not include a GUI project, so I am using the WDK 8.1 sample code below.
https://github.com/uri247/wdk81/tree/master/Microsoft%20slate%20system%20virtual%20audio%20device%20driver%20sample

I put the OutputDebugString function at the beginning of each function.
The process goes through the constructor and the Initialize function, but not through the APOProcess function.

Question:
(1) Why isn't APOProcess function called?
(2) Is the registration registry correct?
{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},1 = {B48DEA3F-D962-425a-8D9A-9A5BB37A9904}
{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},2 = {06687E71-F043-403A-BF49-CB591BA6E103}
(3)Do I need to change other registries?

OS:Windows10 1909
Platform toolset:WindowsApplicationForDrivers10.0
Windows SDK version:10.0.19041.0

Best Regards.

Windows Hardware Performance
Windows Hardware Performance
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Hardware Performance: Delivering / providing hardware or hardware systems or adjusting / adapting hardware or hardware systems.
1,557 questions
0 comments No comments
{count} votes

Accepted answer
  1. Takayama Shin-ichi 116 Reputation points
    2021-02-04T09:01:36.173+00:00

    When I executed the following items, the dll worked.
    -Created a folder in C: \ Program Files and copied the APO dll.
    -Registered the dll with the regsvr32 command.

    If the redistributable package is not installed, you must put msvcr120.dll and msvcp120.dll in the same folder.
    (When creating a dll with Visual Studio 2013)

    0 comments No comments

0 additional answers

Sort by: Most helpful