Unable to Start Service using PSADT 4.1.8

I am trying to Start the Service (which is in Stopped status) using below command with the PSADT v 4.1.8

Start-ADTServiceAndDependencies (using all the parameters mentioned on the site)
and Start-Service

Above commands are failing to start the service but same commands works with the PSADT 3.10 versions without any issues.

Is there any known issues with Service commands for new PSADT?

There's been some issues found within the setup that have already been repaired. Can you please try this 4.2.0 dev build and let me know if everything is working? All you need to do is replace your PSAppDeployToolkit with one from one of these .7z files.

Thanks for the response.
As per your suggestion I have replaced the PSAppDeployToolkit with the new one. However still no luck with restart of service.

First, I have used below command which resulted in the error mentioned below snippet.

Start-ADTServiceAndDependencies -DisplayName 'RICOH Streamline NX PC Client Service' -PendingStatusWait 00:01:00

I also tried with the command Start-Service -Name ‘SLNXPCClientService' -ErrorAction SilentlyContinue.
It does not give the actual error but no change in the service status.

To give you context I am upgrading the Azul ZULU JRE 8 in my environment and while doing so closing the JAVA.EXE and JAVAW.EXE processes in preinstall section.

Closing the JAVAW.EXE terminating the RICOH Printer app in the background and auto stopping its service.
Result of this, it is not allowing me to relaunch the RICOH Printer in POST INSTALL SECTION OF SCRIPT as service is in STOPPED status.

What happens if you reboot after the upgrade?
Can you restart the service then?

Rebooting the machine AUTO START the service. No intervention needed from our side.

But for the better user experience we trying to restart the service in Post Upgrade section, as our package causing service to stop.

When I use PSADT 3 it does not stop the RICOH service. However, PSADT 4.1.8 does stop this service and not able restart it again.
Below might be the reason for this case.