Finally, the problem is solved.
I have not done anything about this since June 14, 2017.
Today, the solution came unexpectedly on this.
There was a major update for Win10 to solve this problem.
After the update, I tried to enable WebsiteX5 ver.12 and then it worked as it should.