Avoid computer to show automatically password wizard option after time out

Question

The issue

Regularly, the following happens:

1. A Mac computer, running mac OS 10.15.3 (19D76), with Filevault enabled, is turned on,
2. If the user logs in immediately, everything is normal.
3. Otherwise, after a couple of minutes, the following message appears:

   If you’re having a problem entering your password, press and hold the power button on your Mac to shut it down. Then press it again to start it up in the Recovery OS.

4. After ~5 minutes, the screen goes black.
5. Then, the screen can not be brought back up. Pressing keys or touching the touchpad does not bring back the screen.
6. The only way to interact with the computer again is by hitting the "Power" button. Once hit, there is a ~2 minutes waiting time, and the "Reset password wizard" appears.
7. Since we do not want to reset the password (after all, we know it!), we have to reboot the computer, which takes some time, and to go back to step 1.

Can you make password recovery starts only if explicitly asked, and not if this time limit, or whatever it is, was triggered?

What I've Tried

• Reset NVRAM an PRAM,
• Updated all software,
• Plugged in a keyboard at start up,
• Ran diagnostics,
• Ran disk utility,
• Deleted all the preference files.

None of that raised any issue nor changed this behavior.

Related Questions

The process looks fairly similar to what's described here.

I'm assuming this comes from some time-delay we trigger, but it is annoying. We are not not entering the password because we forgot it, but simply because we were doing something else at the time.

This question is loosely related, and suggests that this behavior comes from enabling Filevault. I do not want to deactivate it, but would like for the log-in screen to "simply come back" when the mouse is moved or a key pressed, without having to exit the "reset password wizard" and rebooting.

Answer 1

Even if it is not mentioned in the release notes, it seems that migrating to macOS Catalina 10.15.4 fixed the issue.