"86Box did not initialize in time" error in 86Manager after 0 seconds

[headsetguy37]

Describe the bug
When launching a machine through 86Manager in Build 4232 or later (don't know about earlier builds), 86Manager reports that "The 86Box process did not initialize in time", even though I have the timeout set to 5000 milliseconds (5 seconds). I have not made any changes to 86Manager, only 86Box itself.

To Reproduce
Steps to reproduce the behavior:

1. Launch 86Manager.
2. Confirm the build number is 4232 or later.
3. Confirm timeout is set.
4. Launch a VM.
5. See error immediately.

Expected behavior
Error should not appear unless the VM doesn't launch within the specified time.

Screenshots
Error:

Desktop (please complete the following information):

• OS: Windows 10 Pro 21H2
• 86Box version: v3.8 build 4232 or later
• Build information: Old dynarec, 32-bit, normal build

Additional context
This error does not occur on Build 4215. I went straight from 4215 to 4232, and noticed the error happening. I have also tried 4233, 4234, 4235, and 4236 (the latter two have finished compiling the Win32 builds as of the time I'm writing this), and saw the same result. Unfortunately, I don't know which build started this issue, since i have not tested anything between 4215 and 4232.

I'm positive this is not an issue with 86Manager, because I did not make any changes/updates to it, only to 86Box itself. Rolling back to 4215 causes the error to not appear.

[OBattler]

Could easily be that simply adding more machines increased the ROMs checking time enough that it now sends the hWnd too late to 86Manager. 86Manager has to increase the waiting time.

[daviunic]

There is no launch timeout option in 86Box Manager anymore since version 1.7.4. You must be using an older version, in which case I suggest you update to 1.7.4 and see if this issue persists.

[daviunic]

Also keep in mind that the very first launch of 86Box in a Windows session will usually take longer than the subsequent ones. So don't be surprised if it takes a few seconds to appear on the first launch. Actual time depends on your hardware, of course.

[headsetguy37]

Also keep in mind that the very first launch of 86Box in a Windows session will usually take longer than the subsequent ones. So don't be surprised if it takes a few seconds to appear on the first launch. Actual time depends on your hardware, of course.

The error would appear instantly.

In any case, 1.7.4 fixes it. Closing as resolved.