CFG-ERR-0106 IBM Cognos Configuration did not respond

[Binway]

Hello Team,
I have recently done a new install of Cognos 10.2.2 on a windows 10 laptop with 32gb ram.  I followed the directions for the easy install for a 64bit machine.
When starting the Services in Configuration Manager i get the error - [ ERROR ] CFG-ERR-0106 IBM Cognos Configuration did not receive a response from the IBM Cognos service in the time allotted.
Check that IBM Cognos service is available and properly configured.
There is no cognosserver.log file available yet and I checked the http://www-01.ibm.com/support/docview.wss?uid=swg21646350 document.  The only scenarios I could see that may have applied was the incorrect JAVA_HOME so I tried both deleting the JAVA_HOME and pointing the JAVA_HOME to the jre in the Cognos 10 installlation directory.
And Scenario 7 where the servlet gateway was installed, configured and failed to start so right click on Cognos Server and click start.  Interestingly both the Servlet GAteway and Cognos Service have the green indicator that they are running and when I go to install other things like Samples I am informed that these two services will be stopped.
But when I try to test the content manager by typing http://localhost:9300/p2pd/servlet I get the web page with the error that the local host refused connection.
Any suggestions appreciated.

[Binway]

Hopefully this helps someone else.
There are a large number of documents that suggest a resolution to this issue.  Unfortunately none of them seemed to help me.
Listed below are some of the changes I made:

• unset the JAVA_HOME variable in my environment variables so Cognos picks up the java from it's installation - with the Config Manager GUI active press Ctrl+F3 to verify.
  
• I uninstalled and reinstalled a number of times
  
• changed from 64bit to 32bit server install
  
• changed from 10.2.2 to 10.2.1 then tried all the way down to 8.2 but 8.2 won't install on Windows 10
  
• changed the location from C:\Program Files\...etc to C:\ibm\cognos\... etc to remove any spaces in the path
  
• changed from WebSphere Liberty Profile to tomcat and upped the max memory to 2048
  
• always start Configuration Manager as Administrator
  

All for no joy.  Then I found a mention of using the startup and shutdown batch files in the installlocation/bin64 directory.  Whilst this is not an ideal solution and not something I would do on a client site, the running of these scripts in conjunction with a "start" in Config Manager got me going well enough for me to do my Demonstrations.

Happy Reporting
Binway