After installing Java JRE 1.8.0_261 (8u261) or later on Windows with the local adminitrative console enabled, Symantec Protection Engine (SPE) no longer starts. The symcscan service remains in a stopped state and cannot be started manually.
Starting with Java JRE 1.8.0_261 (8u261), Oracle moved to using the Microsoft Visual Studio 2017 tool chain to build releases. This move requires changing the runtime library that JRE depends on (see the Oracle Java release notes for more information). Because of this change, there may be unexpected behavior when the Java UI is enabled and when Java JRE has been updated to 1.8.0_261 and later.
Windows Server with Oracle Java JRE 1.8.0_261 (8u261)
Protection Engine 8.2 will be released with changes necessary to function properly with new Java JREs. Until Protection Engine 8.2 is released, please use one of the workarounds listed on this page.
Your organization can consider the following workarounds.
In some instances, the issue is caused by certain Java files no longer being findable in the Java directory using the existing PATH variable. Adding the Java bin path (by default: C:\Program Files\Java\jre1.8.0_261\bin) to the system PATH environment variable may allow the service to start in these instances.
The local administrative console is completely optional in all supported versions of Protection Engine. It is fully functional and manageable without the console. You can perform all actions via the commandline that you normally would in the console. For information on how to do this, please see the chapter in the Implementation Guide titled "Working with the Core server only mode" or this section of the online help guide.
Protection Engine 8.0 added a cloud-based console. You can upgrade to SPE 8.0 and utilize this console to perform some management tasks on the scanners
If your policies allow it, you can use the older versions of Java JRE to continue to use the local administrative console.