Ben, at this point I would stop doing broad Realtek reinstalls. Since reinstalling the ASRock Realtek package did
not fix it, the bad Microsoft update is likely still present as an
audio extension/APO/software component sitting beside the Realtek driver.
The cleanest next moves are:
- System Restore to before the Microsoft driver update
- If no restore point exists, identify and remove the exact APO driver package
- If that still fails, do a Windows repair install while keeping apps/files
1. Best fix: use System Restore
If Windows created a restore point before the driver update, this is the most direct reversal.
- Press
Win + R.
- Type:
rstrui.exe
- Press Enter.
- Choose Show more restore points if available.
- Select a restore point from before the Microsoft Audio Processing Object update.
- Continue and let the system restore.
- After rebooting, immediately pause Windows Update.
This should roll back driver-store/system changes without touching your personal files.
2. Find the exact Microsoft APO package from the log
The three lines you posted confirm version
1.0.3.56670, but we need the surrounding lines that show the
INF name or
Driver Store path.
Open
Terminal/Admin or
Command Prompt/Admin and run:
mkdir C:\Temp
Then run this PowerShell command:
Select-String -Path C:\Windows\INF\setupapi.dev.log -Pattern "1.0.3.56670" -Context 80,80 | Out-File C:\Temp\apo-context.txt -Encoding utf8
Then open it:
notepad C:\Temp\apo-context.txt
Look for lines containing words like:
Code:
oem
inf
Published Name
Driver Store
FileRepository
AudioProcessing
Extension
SoftwareComponent
Please paste that larger section here. The line we especially need is something like:
Published Name: oem##.inf
or a path like:
C:\Windows\System32\DriverStore\FileRepository\something.inf_...
Once we know the exact
oem##.inf, we can remove only that package.
3. Also check Device Manager under software components
This update may not appear under the normal Realtek audio device.
- Right-click Start.
- Open Device Manager.
- Click View > Show hidden devices.
- Click View > Devices by driver.
- Also check View > Devices by connection if needed.
- Look under these areas:
Code:
Software components
Audio Processing Objects
Sound, video and game controllers
System devices
Audio inputs and outputs
- Look for anything dated around 05/04/2026 or version 1.0.3.56670.
- If you find one, open Properties > Driver > Driver Details.
- Post the driver name and version before uninstalling.
Do
not remove random Microsoft system devices unless we can confirm they are tied to that APO/audio update.
4. Disable Realtek/Microsoft audio effects components
Since the issue is choppy/dropout audio, try disabling the effect layer rather than the base Realtek device.
- Open Device Manager.
- Expand Software components.
- Look for entries such as:
Code:
Realtek Audio Effects Component
Realtek Hardware Support Application
Microsoft Audio Effects Component
Microsoft Audio Processing Object
A-Volute
Nahimic
DTS
Dolby
Sonic Studio
- Right-click one suspicious audio effects component.
- Choose Disable device, not uninstall.
- Reboot.
- Test sound.
If audio improves, we found the bad layer. If it gets worse, re-enable it from Device Manager.
5. Try a completely different audio path
This tells us whether the problem is only the onboard Realtek stack or a broader Windows audio engine issue.
- If you have HDMI/DisplayPort audio through a monitor, set that as default and test it.
- If you have a USB headset or USB audio adapter, test that.
- If Bluetooth audio is available, test that too.
If
USB or HDMI audio works normally, the problem is probably the Realtek/APO driver stack.
If
every output is choppy, then the update may have triggered a system-wide audio/DPC latency problem.
6. Restart the Windows audio services
This probably will not permanently fix it, but it is quick to test.
- Open Command Prompt/Admin.
- Run:
Code:
net stop audiosrv
net stop AudioEndpointBuilder
net start AudioEndpointBuilder
net start audiosrv
- Test sound again.
If Windows says one service cannot be stopped, just reboot and continue.
7. If no restore point exists: repair install Windows 11
If the APO package cannot be cleanly removed, the next safest repair is an
in-place repair install. This keeps your files, apps, and most settings, but rebuilds Windows system components.
- Back up important files first.
- Download the official Windows 11 ISO from Microsoft.
- Mount the ISO.
- Run:
setup.exe
- Choose Keep personal files and apps.
- Complete the repair install.
- After Windows boots, install the ASRock Realtek audio driver again.
- Then block driver updates from Windows Update.
This is less destructive than a Reset or clean install.
8. Block driver updates after fixing it
Once audio is working, run this from
Command Prompt/Admin:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f
Then reboot.
To undo later:
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate /f
My recommendation
Given what you’ve already tried, I would do this in order:
- Try System Restore first.
- If no restore point exists, generate
C:\Temp\apo-context.txt and post the surrounding log lines.
- Test USB or HDMI audio to see whether all audio paths are broken.
- If we still cannot remove the APO package cleanly, do an in-place Windows 11 repair install.
The Realtek driver reinstall not helping is the key clue — the bad Microsoft APO/extension component is probably still attached somewhere outside the main Realtek driver.