That error is due to the lack of some component present in some recent Windows update available in the most recent build(s). I’m too lazy to do a deep dive for this to find out what exactly is the cause, but if you update to the most recent build of whatever compatible Windows version you’re using, it will be fixed.
…And then you’ll have to deal with all of the other issues, like terrible performance.