Thank you Beverly.
Both problems are resolved.
This already happened to my teammate a few years back. 
But I had forgotten that my new laptop was originally configured for a non-developer and I had forgotten that having the run-time dll's/pbd's of PowerBuilder also in 'C:\Windows\SysWOW64' could cause those problems.