PlayStation 4 - Troubleshooting

If you cannot find the solution to your problem in the troubleshooting section, please contact us.

Restart SuitestDrive

Restart SuitestDrive after applying any fixes to allow changes to take effect.


.NET Framework not installed

To be able to add the PlayStation 4 console to Suitest you will need to have .NET Framework 4.7 (or newer) installed on the Windows 10 computer which is running SuitestDrive and controlling the console via the USB - CEC Adapter.

PlayStation SDK not installed

To be able to add the PlayStation 4 console to Suitest you will need to have the PlayStation SDK Manager and Target Manager Server installed. If you are unsure how to do so, please consult the Sony developer documentation which will provide you will all the details. Please also make sure that it is installed on the computer running SuitestDrive and controlling the console via the USB - CEC Adapter.

PlayStation 4 is unresponsive to the virtual remote control

If you find that the PlayStation stops receiving inputs from the virtual remote control or test editor.

To solve the issue, try the following:

  1. Verify that the USB - CEC Adapter is correctly connected to the devices.
  2. Unplug then plug back in the USB - CEC Adapter to Windows 10 computer.
  3. On the Windows 10 computer, make sure that the USB - CEC adapter is recognized in Device Manager.
  4. Restart the Windows 10 computer if all above steps fail.

PlayStation SDK Target Manager Server install location

It is highly recommended to install the PlayStation SDK Target Manager Server in its default install location. However, if this is not possible for you or you are using a different drive letter other than C: then please following the steps below.

No C: drive

If you do not use a C: drive, then you will have to create a virtual drive using subst:

subst C: YOUR_DRIVE:\

For example, lets say you only have a D: drive and you need to map it to C::

subst C: D:\

Default location

Suitest requires the Target Manager Server to be placed in its default location.

Default location: C:\Program Files (x86)\SCE\ORBIS\Tools\Target Manager Server\bin

If it is not found in the default location, then there is a fallback location.

Fallback location: C:\PlayStationTMS

Therefore, if you do not have the SDK installed in its default location, you must create a symbolic link into fallback path using mklink.

mklink /d C:\PlayStationTMS YOUR_LOCATION

For example:

mklink /d C:\PlayStationTMS "X:\Cookie Monster\PlayStation\SCE\ORBIS\Tools\Target Manager Server\bin"