BUG REPORT: Oculus Driver Installer v1.21.5.0 - BadImageFormatException (0x8007000B)

The Problem:
The Oculus/Meta Horizon driver installer consistently fails with:
An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at Daybreak.Core.Native.GetDefaultAudioDevice()
at OculusDriverInstaller.RemoteAudio.Install()

Root Cause:
DaybreakNative.dll is compiled as 32-bit (x86) but the installer runs as a 64-bit process.

This can be verified by checking the DLL in:
C:\Users\[Username]\AppData\Local\Temp\OculusSetup-[GUID]\DaybreakNative.dll

PowerShell verification command:
$bytes = [System.IO.File]::ReadAllBytes("DaybreakNative.dll")
$peHeaderOffset = [BitConverter]::ToInt32($bytes, 0x3C)
$machine = [BitConverter]::ToUInt16($bytes, $peHeaderOffset + 4)
if ($machine -eq 0x014C) { "32-bit (x86)" } elseif ($machine -eq 0x8664) { "64-bit (x64)" }

Result: 32-bit (x86) ← This is the bug

Impact:
- Installer fails after successfully installing most drivers
- Main Meta Horizon application won't install due to rollback
- Prevents users from completing fresh installations

Workarounds That Work:

1. Manual Driver Installation + Older Software Version:

Have File Explorer open to "C:\Users\[Username]\AppData\Local\Temp\"

Run the current installer and let it fail (it will copy driver files to temp first) Quickly copy the entire OculusDriverInstaller folder that appears briefly at C:\Users\[Username]\AppData\Local\Temp\OculusDriverInstaller

Take your quick-copied DriverInstaller folder and right-click > Install each .inf file manually:

- RiftDisplay.inf
- RiftSensor.inf
- OCUSBVID.inf
- Oculus_ViGEmBus.inf
- oculus119b.inf (Audio)
- OCULUSUD.Inf (Rift S Audio)
- riftssensor.inf
- riftsusb.inf
- oculusvad.inf (Virtual Audio)
- android_winusb.inf
- netrtwlanufb.inf
- VirtualScreenDriver.inf

Then: Download and install an older version of Meta Horizon software (pre-v1.77) that doesn't have this bug

2. Use SteamVR Instead:

If you don't need Meta Store games, just use SteamVR.. Works perfectly with manually installed Oculus drivers. No Meta software required

What Meta Needs to Fix:
Replace the 32-bit DaybreakNative.dll with a 64-bit version, or provide a 32-bit installer that matches the DLL architecture.

System Info:
Windows 10 64-bit
Installer Version: 1.21.5.0
All Visual C++ Redistributables installed
Clean Windows installation (SFC/DISM verified)

This is a packaging bug in Meta's installer - the drivers themselves work fine when installed manually.

NEW INSTALLING PATH CREATING PROBLEMS...

Aaaaand turns out I was wrong and NONE of the potential workarounds I listed works at all.. =/ Also, I merged my Meta(Oculus) and Facebook accounts so I can't even edit my original post XD

However what I stated as the problem I believe still stands: 

DaybreakNative.dll is compiled as 32-bit (x86) but the installer runs as a 64-bit process.

In short, fix please? lol I'm going to bed, what a waste of 12 hours >.<

Edit: and the kicker is I can't even open a real ticket with Meta because apparently my Rift S no longer counts as a headset to them so "there are no devices associated with this account" and they won't let me talk to support XD what a !@#$in' joke lol..

same issue also with trying to link my Rift on my windows 11 Gaming PC, no matter how many times ive cleared all previous traces of the app and Re-Download and run the MetaHorizon link app (Setup.exe) , every attempt to try and complete the installation fails when the progress bar reaches the end and shows the same message : "

"Sorry, we encountered an error during installation.

Please restart your computer and try running Link Setup again.

If you still experience issues contact Quest Support".

it looks like alot of people are having the same issues so one of the meta genius's fcked something up but im hoping they actually get it together and sort it out asap.

it makes me wonder if theyre even properly testing and debugging these updates to be abit more stable before they release them instead of a completely useless and non working install. its frustrating..... im all for updates when they actually improve the software but in situations like this...DONT TRY TO FIX SOMETHING THAT AINT BROKEN!!!!!  

So far there is no fix from Meta.

To be honest, I don’t understand why they can’t upload an older version which worked.

Regarding proper testing before a bug release.

Well let 5% of your staff go in order to increase productivity and this is the result we customer has to live with.

Good thing is, there are other PCVR producer.

Ich habe einen Workaround gefunden wie die Installation wieder klappt.

Ihr müsst während der Installation den Ordner: C:\Program Files\Meta Horizon\Support\oculus-drivers durch den "Oculus-drivers" Ordner einer älteren Meta Link Version ersetzten. (Sobald der Ordner bei der Installation erscheint müsst ihr die Daten darin durch die alte Version ersetzten)

Ich hab die Ersatz Datei/Ordner hier gefunden (Version 1.18.0.426075):

Download Meta Quest Link app. | Meta Community Forums - 1289469

Hier ist eine alte Daybreak.dll enthalten welche funktioniert, warum auch immer.

Ich hoffe es klappt bei euch auch.

I found a workaround to get the installation working again.

During the installation, you need to replace the folder
C:\Program Files\Meta Horizon\Support\oculus-drivers
with the “oculus-drivers” folder from an older version of Meta Link.
(As soon as the folder appears during installation, you have to replace its contents with the old version.)

I found the replacement file/folder here (version 1.18.0.426075):

Download Meta Quest Link app. | Meta Community Forums - 1289469

This old Daybreak.dll is included and works—for whatever reason.

I hope it works for you as well.

Same exact problem here. After recent Windows update, Meta Link stopped working correctly.MSFS 2024 locked up with no audio, and after many tries to reinstall Meta Link Horizon, have given up until they fix this issue.  I feel like the Link software is their **bleep** child and if WiFi folks were having issues with AirLink to this extent, this would have been fixed already.  Very frustrated with Meta and looking for different vendor for next PCVR headset.

Here NEW INSTALLING PATH CREATING PROBLEMS... | Meta Community Forums - 1356945

if there no link there, it's becaise META is deleting LINKS .... Because ANY LINK to files that SOLVE a problems for the users, it's a PROBLEM for THEM ... Thanks Meta!

I have the same issue, triggered by the update that switched the install locations. At least for me it seems to be driver installation Meta Virtual Screen Driver

[Debug] [12/12/2025 22:06:33] Beginning uninstallation of: Meta Virtual Screen Driver - Driver package 'C:\Users\tom\AppData\Local\Temp\OculusDriverInstaller\VirtualScreenDriver.inf'
[Debug] [12/12/2025 22:06:33] Ending uninstallation of: Meta Virtual Screen Driver
[Debug] [12/12/2025 22:06:33] Beginning check uninstall health of: Meta Virtual Screen Driver
[Debug] [12/12/2025 22:06:33] Checking if the WUDFRd driver exists in system management
[Debug] [12/12/2025 22:06:33] Driver exists.
[Debug] [12/12/2025 22:06:33] Ending check uninstall health of: Meta Virtual Screen Driver
[Info] [12/12/2025 22:06:33] Health status: -536870142
[Info] [12/12/2025 22:06:33] FAILURE! Failed to uninstall driver: Meta Virtual Screen Driver
[Debug] [12/12/2025 22:06:33] -------------------------------
[Info] [12/12/2025 22:06:33] Successfully unregister magic directshow filter.
[Info] [12/12/2025 22:06:33] Successfully unregister magic directshow filter.
[Info] [12/12/2025 22:06:33] Successfully unregister magic directshow filter.
[Info] [12/12/2025 22:06:33] Successfully unregister magic directshow filter.
[Info] [12/12/2025 22:06:33] SUCCESS! Uninstalled driver: 
[Debug] [12/12/2025 22:06:33] -------------------------------
[Debug] [12/12/2025 22:06:33] About to delete temp directory
[Debug] [12/12/2025 22:06:33] Deleted temp directory
[Debug] [12/12/2025 22:06:33] Reading --ODIVersion string from registry.
[Debug] [12/12/2025 22:06:33] Read --ODIVersion string from registry: ''
[Debug] [12/12/2025 22:06:33] Writing --ODIVersion string to registry: 'Unknown (failed unistall)'
[Debug] [12/12/2025 22:06:33] Wrote --ODIVersion string to registry: 'Unknown (failed unistall)'
[Debug] [12/12/2025 22:06:33] Ending uninstallation
[Debug] [12/12/2025 22:06:33] 
status: False
[Warning] [12/12/2025 22:06:33] Driver exists
                        Error Code: -1
                        Install Step: CheckUninstallHealth
                        Sub Install Step: DoesDriverExist: Meta Virtual Screen Driver
                        Severity: Warning
                        Line Number: 470
                        Caller: CheckUninstallHealth
                        ODI Version: 1.21.5.0
                        File Path: D:\full-fbsource\arvr\projects\oculus_pc_infra\Support\OculusDriverInstaller\OculusDriverInstaller\Driver.cs

from the end of "C:\Users\{myUsername}\AppData\Local\Oculus\OculusDriverInstaller_2025-12-12_22.06.25.log"

Anyone had any success working around it?

Maybe this is the problem?

https://www.reddit.com/r/MetaQuestVR/s/LTkLCnP022