Not yet tried with the installation of 8.2 personally, but it would be better if you can able to share at which step it is failing during install/upgrade and what errors are being noticed during that step. That way we can able to help you in finding its root cause.
The environment is not starting after the upgrade, nor after a fresh new installation.
The error message is the following:
ERROR - Could not activate managed run [pyFTSIncrementalIndexer] during server startup java.lang.IllegalStateException: Cannot resume run [pyFTSIncrementalIndexer] with status [Resuming]. Reason: Cannot transition run to Resuming at com.pega.dsm.dnode.impl.dataflow.task.ResumeRunTask$ResumeTaskResult.generateException(ResumeRunTask.java:113) ~[d-node-8.2.1-225.jar:?] at com.pega.dsm.dnode.impl.dataflow.task.TaskResultHandler.propagateExceptionIfExists(TaskResultHandler.java:13) ~[d-node-8.2.1-225.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.DataFlowOperationsRunHandler$6.resume(DataFlowOperationsRunHandler.java:273) ~[d-node-8.2.1-225.jar:?] ....
Based on the above stack trace it seems to be an issue with your DNodes, where it is failing to resume one of your DNode while server start up, may be the respective SMEs should able to help you on this issue. Also you can share the complete stack trace for their analysis going forward.
I was able to install 8.2.1 successfully on Windows 10.
On Windows 7 it does not work properly. After logging on using Administrator@pega.com/install, it puts me on Dev Studio. This is as expected. However, when I try to create Admission, UIKit is missing and PegaApp cannot be chosen since Radio button is disabled. Unsure what the issue is.
I have tried on 2 different Windows 10 machines. Worked.
I have tried on 2 different Windows 7 machines. Does not work. I realize Windows 7 is seeing it's last days but it should work.
Based on the Thread Dump stack, the system is locked / blocked on Tomcat connection pool implementation.
In Tomcat, there are 2 connection pool types JDBC Connection Pool org.apache.tomcat.jdbc.pool and Apache Commons DBCP connection pool. The default Apache Commons DBCP connection pool can occationally cause Thread blocks.
Use the JDBC Connection Pool org.apache.tomcat.jdbc.pool by including factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" setting in Tomcat's context.xml and restart the server.