Handbrake 1.6.1 can't connect to worker process

[shawhu]

Problem Description

When I turn on process isolation, handbrake stops working. Can't connect to worker instance

I've disabled the firewall and antivirus (windows defender)
Does "process isolation" work? It seems it stopped working long time ago. It used to work.
If I disable process isolation then it worked but I have a 32 cores cpu, one process only gives about 60% cpu usage.

Activity Log, Crash Log or any other details

HandBrake 1.6.1 (2023012300)
OS: Microsoft Windows NT 10.0.19044.0
CPU: AMD Ryzen 9 3950X 16-Core Processor            
Ram: 65442 MB, 
GPU Information:
  NVIDIA GeForce RTX 2080 SUPER - 31.0.15.1694
Screen: 2560x1440
Temp Dir: C:\Users\xxx\AppData\Local\Temp\
Install Dir: C:\Program Files\HandBrake\
Data Dir: C:\Users\xxx\AppData\Roaming\HandBrake

-------------------------------------------

 # Starting Encode ...

[12:03:23] base preset: 1080p
[12:03:23] Remote Process started with Process ID: 32224 using port: 8039. Max Allowed Instances: 2
[12:03:23] Worker: Starting HandBrake Engine ...
[12:03:23] Worker: Starting Web Server on port 8039 ...
Unable to connect to the HandBrake Worker instance after 10 attempts. Try disabling this option in Tools -> Preferences -> Advanced.

 # Job Failed (-10)

What Operating System are you running?

Windows 10

What version of HandBrake are you running?

1.6.1

Where did you download HandBrake from?

handbrake.fr

[sr55]

Yup, it works. It's default on, so we have a large user base of folks using it.

Turn it off, start another encode and if that works correctly without error, then something on your system is causing it problems.

You could also try changing the port range it uses

[sr55]

You could also try a development snapshot build: https://github.com/HandBrake/handbrake-snapshots/releases/tag/win

This will update in a bout an hour or 2 which includes some additional logging. Would be interesting to see why the HTTP servers not kicking off on your system.

[sr55]

We've not heard back in a while. If you can provide any further feedback that would be appreciated. If not, we'll close the issue out in the next day or so.

Thanks