I saw this exact symptom when I had an incorrect .dll file present as well. I had to download an updated .dll from the Microsoft website, as per this thread.
That of course doesn't solve your other issues, but just for context 
1 Like