This is a known issue in Deep Security Manager 10.3 and it will be fixed in Deep Security 11.0. There will be no update for this fix, thus, customers need to upgrade to version 11.0.
As a workaround, execute the following SQL command on the database where the Deep Security Manager is located. You can verify the database name from the DSM console under Administration > System information.
update hosts set virtualpowerstate=0 where virtualpowerstate=1