Hello,
I haven't seen this error before so it's a bit shooting in the dark with a water pistol to try to kill a fish. But, that aside, here is how I would personally start to look at it.
Windows has a tool which looks for corruption of system files. It doesn't always detect the problem and, even if it detects it, the tool doesn't always fix the issue.
The first step would be to check the drive doesn't have corruption.
1. Run a disk check.
In the Windows file explorer, right click on your system driver, then select properties, then tools, then Check. If there are errors, correct them and reboot. Then check there's none left.
2. Run the System File Checker tool
This is the Microsoft tool looking for system file corruption which might not find it. Here is
the official way of using it. Here is the
way to use it from a website I always advise to users as I find it very clear. I advise you choose Option 2.
There are other ways to add drivers to the driver store, but I doubt they will work.
I believe what you need first it to address this driver store corruption. I've seen that error mentioned when having issues with Windows Update (WU) components. I'm not sure how it could be relevant to you as you're not using WU here, but it could be that an update has locked the driver store, this I know is possible... Therefore, if all fails, you can go through the very manual process of going through the steps described in that
Windows KB. The wizard did not solve my issues, so I recommend going the long way straight away... But my issue may have had a different root cause.
Kind regards,
Alban