I don’t know why Unity isn’t at least making this error message more clear, and as far as I’m aware they are letting users fend for themselves.
I believe the error started in 2018.3, so if you can’t resolve it you can use 2018.2.x for the time being. Some people report installing certain OS updates resolve the problem.