[WARNING] If you going to try this fix at home, please backup the DLLs, I take no responsibility if your computer audio stop working!
I recently reinstalled windows 10 due to windows updates introduced bugs over two years and finally made the system unusable. after a fresh reinstall, and downloaded all software I use, I noticed this "Driver not installed correctly" on every startup.
The adventure to fix the issue has begun. first, I did some search and found out I'm not the only one who had this problem, and there isn't a permanent solution for it, yet... Until now!!! According to previous adventurers, this issue is caused by windows continuously rest a registry key(two if on amd64 system), they are:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1
so, I tried to create a startup task that reset the registry to the correct value, and then launch VirtualMidiSynth.exe, but it doesn't work every time. I even went on an extreme approach, run a repeating task that reset it every minute for a duration of time after startup, still, not every time.
Since this didn't work, I start to "think differently"(not like what Apple did, I HATE Apple), if I can find out what modified the registry key, then I should be able to stop it from doing it, right? So I set up an event auditing on the effected registry key and restarted the computer, in the event viewer, I found a record that happened during the startup time and the PID of the source points to a system process called "svchost.exe", which corresponds to "Windows Audio Endpoint Builder" Service.
Now I found the suspect, it's time to do a test to verify that my suspicion is correct. I went to the interweb and searched for DLL called "AudioEndpointBuilder.dll". On https://www.dllme.com/, I found these two DLLs from the same 2017 windows release and downloaded them.
I took the ownership of "AudioEndpointBuilder.dll" and "AudioHandlers.dll" located under "C:/Windows/System32/" directory, and replaced them with the one I downloaded online. My theory is since this software worked flawlessly back when I first installed windows 10, an older service DLL should not have this bug. After I replaced those files, I disabled the startup tasks I created and restarted my computer.
Jackpot!!! the registry keys are still intact after a reboot, and I reboot a few more times to make sure this is working.
Feel free to try this fix and let me know if this worked for you guys. This only fixes the problem caused by the 1909 update, no guaranteed success for other causes. If it worked for more people, I might consider making a video on exactly how to do this to help other people who are not that experienced with computer things.
DLL files link: https://mega.nz/file/6h0BTa7C#hLPyCyuj0W09yw2iTcpkfvcS_Se7WHvXgiI-EDFVxvs
I used to be an adventurer like you, then I took an arrow in the knee...