SoundId Installation Failed windows 11 error 0x80070643

I am having this same issue, as far as I can tell the problem is caused by something in systemwide - I am guessing the .sys file .inf driver store etc.. everything with sonar works installs except the core application. I got this issue after installing a new SSD and cloning my old SSD I got a hardware ID issue I think and sonarworks just started failing to launch not sure if it was x33 or something error. On trying to reinstall it just wouldn't install the reference ID because the installer has coded into it instructions to roll back the install if it detects a previous install it cannot remove (basically its programmed not to reinstall)  - worse even after manually rebuilding as much as I am aware of the soundid app still won't load via the webapps, not sure why but this is a unique problem with sonarworks, even the google login will not load, as I think the javascript is tied to the soundid core app which won't reinstall so its sort of self fullfilling programming to prevent the app from being used  or reinstalled. I am not sure if this was caused by the cloning but I highly suspect it was cauesd by transfering the previous drives contents, not sure if the program includes different drives as different device locations as this was also done with SSL plugins which also didn't like being changed to a new drive. I'm not sure the cause or how to fix it, but it seems it is just really bad programming to lock out someones ability to reinstall software if a trace of a previous install is detected - worse making removing files like the .sys files is doubly problematic as leaving behind system files and not providing a way to remove them is just bad practice.

Note I finally got this working for install after days of tearing the install appart.   Although I did a lot of steps the ones that finally resolve this and may be key are reregistering the services and dll's.   SoundID provides an installer but in that installer is an installer that contains MSI installers, those individual MSI installers include one that is "SoundID Reference" the others are measure and the plugins. The sound ID reference contains the system wide and APO  and services etc..  if you arrange your directories in the proper order you can register the services with sc command and you can register the dlls except one that is special with regsrv32.  

Make sure you have these registry entries

# Add-RegistryEntries.ps1

# Define keys to create (only valid registry key paths)
$keysToAdd = @(
   "HKCU:\Software\Sonarworks\SoundID Reference",
   "HKLM:\SOFTWARE\Classes\Installer\Products\08B83AFB92334344A90CE2D39E953B80",
   "HKLM:\SOFTWARE\Classes\Installer\Products\91BBC6CBB641EEB46AEC990CFDBA899B",
   "HKLM:\SOFTWARE\Classes\Installer\Products\D3F7B79F02441CF48A97083F625FDEA8",
   "HKLM:\SOFTWARE\Classes\Installer\Products\D8FC9DD7B3A1A7843A67CDA02C742233",
   "HKLM:\SOFTWARE\Classes\Installer\Products\EC67C17D6F504814591BBB5266BA35FC",
   "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\{D71C76CE-05F6-4184-95B1-BB2566AB53CF}",
   "HKLM:\Software\Microsoft\Windows\CurrentVersion\Installer\Folders",
   "HKLM:\System\CurrentControlSet\Services\Sonarworks Driver Interface",
   "HKLM:\System\CurrentControlSet\Services\SonarworksAPOConfigService",
   "HKLM:\System\CurrentControlSet\Services\SonarworksWDMDriverService"
)

foreach ($key in $keysToAdd) {
   if (-not (Test-Path $key)) {
       try {
           New-Item -Path $key -Force | Out-Null
           Write-Host "[+] Created key: $key"
       } catch {
           Write-Warning "[-] Failed to create key: $key - $_"
       }
   }
}

# Set registry values with valid paths and value names
# These values will need valid parent keys; create them first if necessary

# Friendly app/company names (HKCR paths use HKCR: drive)
$muiCacheKey = "HKCR:\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files\Sonarworks\SoundID Reference\Systemwide\"
if (-not (Test-Path $muiCacheKey)) {
   New-Item -Path $muiCacheKey -Force | Out-Null
}
New-ItemProperty -Path $muiCacheKey -Name "SoundID Reference.exe.ApplicationCompany" -Value "Sonarworks" -PropertyType String -Force
New-ItemProperty -Path $muiCacheKey -Name "SoundID Reference.exe.FriendlyAppName" -Value "SoundID Reference" -PropertyType String -Force

# Example ProductName values for installer entries
$productKeys = @(
   "08B83AFB92334344A90CE2D39E953B80",
   "91BBC6CBB641EEB46AEC990CFDBA899B",
   "D3F7B79F02441CF48A97083F625FDEA8",
   "D8FC9DD7B3A1A7843A67CDA02C742233",
   "EC67C17D6F504814591BBB5266BA35FC"
)

foreach ($id in $productKeys) {
   $path = "HKLM:\SOFTWARE\Classes\Installer\Products\$id"
   if (Test-Path $path) {
       New-ItemProperty -Path $path -Name "ProductName" -Value "SoundID Reference" -PropertyType String -Force
   }
}

# Installer folder paths (example only — Windows may not allow adding custom values here)
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Installer\Folders" -Name "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\" -Value 0 -PropertyType DWord -Force
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Installer\Folders" -Name "C:\WINDOWS\Installer\{D71C76CE-05F6-4184-95B1-BB2566AB53CF}\" -Value 0 -PropertyType DWord -Force

# Example image path values for services
New-ItemProperty -Path "HKLM:\System\CurrentControlSet\Services\Sonarworks Driver Interface" -Name "ImagePath" -Value "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\swdriver.sys" -PropertyType String -Force
New-ItemProperty -Path "HKLM:\System\CurrentControlSet\Services\SonarworksAPOConfigService" -Name "ImagePath" -Value "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\swapo.exe" -PropertyType String -Force
New-ItemProperty -Path "HKLM:\System\CurrentControlSet\Services\SonarworksWDMDriverService" -Name "ImagePath" -Value "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\swwdm.sys" -PropertyType String -Force
 

 sc.exe create "SonarworksWDMDriverService" binPath= "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\WDMDriverManagement\SonarworksWDMDriverService.exe" start= auto

sc.exe create "SonarworksAPOConfigService" binPath= "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\APO\APOConfigService.exe" start= auto

sc.exe create "SonarworksDriverInterface" binPath= "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\VirtualASIO\SonarworksDriverInterfaceServer.exe" start= auto

regsvr32 "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\APO\SonarworksAPODriver.dll"  ←-(this may not register)
regsvr32 "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\APO\SonarworksMDAPODriver.dll"
regsvr32 "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\VirtualASIO\SonarworksASIODriver.dll"

pnputil /add-driver "C:\Program Files\Sonarworks\SoundID Reference\Systemwide\Winx64\soundidreference.inf" /install

C:\Program Files\Sonarworks\SoundID Reference\Systemwide\Winx64\soundidreference.inf

Install the msi's all should install except soundid reference. You can manually unpack soundid reference msi with either an unarchiver or using the msiexec command

The installer has rollback enabled if it cannot install meaning you may be unable to unpack the core files unless you unpack them through 

Start-Process msiexec -ArgumentList '/i', 'C:\Path\to\yourinstaller.msi', 'DISABLEROLLBACK=1' -Wait -NoNewWindow  unsing an unpacker like UniExtract will probably be easiest as it will recognize the msi extraction.   If you try to manually install the msi it will always rollback because the default configuration of the installer is rollback DISABLEROLLBACK=0 meaning the files are never installed.

There were more steps I took such as unlocking the .sys file with unlockit but this may not be required in fact a lot may not be required situationally, but this is some of the last steps I took to get things reinstalled.

Also the online activation is problematic and 100% requires you to have the services above working atleast one of them interfaces with the online activation without it running and active you can't activate - although there is a json file that contains activation and whether it is a first load or not that may be able to be manually altered but I didn't try that step.

If you had the same issue I had with this - I this the two things that are important is to reenter the registry settings and reregister the services. Once you get everything active you are able to run the installer again as normal and it will do a fresh install overtop.  

Since I spent days getting it working again I wanted to share some of the steps I took in hopes it will save someone else the frustration and time as these things like manually editing the registry and reregistering services and dlls will be beyond basic knowledge of most people using windows. imo  BUT it may be essential to get soundID working again because the installer will not repair or reinstall - it will only install if there are no system irregularities.

Juan William Ashley please stand by, a fix for the issue is coming later this week with a new Beta release. We will notify you as soon as it's available. 

A fix for the issue has been delivered in our latest 5.12.2.1 Beta update. Since you have already managed to get it up and running with the current version, it should be as simple as installing the new Beta update for a permanent fix. See Beta install instructions here: SoundID Reference Beta software releases

Let us know if there are any further issues, thank you!