Hi Hugo Michel,
The first step to resolve this is isolating the Fast Startup mechanism, which saves a kernel-level snapshot into the hibernation file to speed up subsequent boots. If a driver state becomes glitched or a system update is pending a deep hardware state change, Fast Startup can repeatedly reload this problematic state. You can disable this by modifying the registration entry known as HiberbootEnabled, located within the system registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power. Changing this value from one to zero tells Windows to perform a completely clean boot, forcing the operating system to rebuild its connections with your hardware devices from scratch.
If a clean boot does not eliminate the five-to-seven-minute delay, you can extract the precise telemetry of the startup sequence using the built-in Windows Event Viewer. By opening this utility and expanding the folders for Applications and Services Logs, Microsoft, Windows, and finally Diagnostics-Performance, you will find the Operational log. Within this log, look for Event ID 100, which serves as the master record documenting overall boot degradation. To find the specific culprit, examine the adjacent logs, where Event ID 102 specifically flags driver initialization delays and Event ID 103 isolates slow system services, revealing the exact file name or component responsible for the timeout.
Hope this answer brought you some useful information.
VPHAN