Have you checked which process calls the 'Could not start On-screen keyboard' error when the Cryptographic Service is running?
Can you run MSInfo32 and click through each of the subcategories to ensure they populate (some might not load, depending on your PC configuration) and then Save As MSInfo32.NFO. Zip that (right-click > Send to > Compressed folder) and attach the zip to a Reply.
[The earlier Dependency Walker errors are a red herring, it looks like the 'missing' files are Windows RT alternatives, my PC threw the same errors and OSK works fine.]
Here you go.