AME runs AE as background process on PC

Hello everyone,

not sure if anyone noticed already, but after latest updates AME runs renders with After Effects as a Background process opposed to child. Attaching before and after images.

Meaning - when you begin encoding, After Effects runs as an instance among Background Processes in Task Manager, versus child process as it was doing all the time in the past. You wonder what is the difference?

If render got slow or stuck, in the past you could have just killed AE process, and it automatically triggered new AE instance for render, to pick up where it has left. Now, as it appears in background processes - this does not remain to work in the same way. Sometimes, when AE process is killed - it doesn't trigger new instance anymore, which causes renders to fail completely if exporting to single output.

The questions are:

1. Why its no longer a child process and is it really the latest update change? As it started behaving this way only recently. 

2. Is there a way to manually trigger AE renderer and link to to AME, in order to pick up where stuck render got finished?

Not to mention its no longer rendering on further CPU capacity than earlier versions, buts thats another topic.

In the past:

(AME used to trigger renderer under child processes)

Now:
(Blue is GUI instance of AE, red is AME rendering)