Long Delay Before Splash Screen Appears Prior to Windows Starting

steamship · Nov 3, 2025

This is an odd one I noticed a couple of days ago, and may have happened previously, but not certain as I just start it and do something else in the meantime, but it's usually only for a very short time.

In this instance, I powered on the laptop and was glancing over at it whilst doing other things in the room. After a time when I expected to see the Windows login screen, the screen was still black. At this point I thought that maybe I pressed the F12 or Delete button by mistake, so went over to start it again, only to see that the power light was lit. Around this time, the HP Omen splash screen appeared, followed a couple of seconds later by the Windows login.

I used Wintoys to see my boot time, and it 51.3 seconds. Checking it ever since, the boot times are around the 8.1-8.5 seconds.

I've checked the Event Viewer for Warnings and Errors, and this is what I get for the last three days (I didn't check further back), all the same. However, this is just Windows stuff, and the delay was prior to Windows starting, so is there any way to check the BIOS for debugging issues?

Level Date and Time Source Event ID Task Category
Warning 01/11/2025 10:09:48 Microsoft-Windows-Kernel-PnP 219 (212) "The driver \Driver\WUDFRd failed to load.
Device: ROOT\DISPLAY\0000
Status: 0xC0000365"
Warning 01/11/2025 10:09:51 Microsoft-Windows-Kernel-PnP 219 (212) "The driver \Driver\WUDFRd failed to load.
Device: ACPI\AMDI0080\1
Status: 0xC0000365"
Warning 01/11/2025 10:12:12 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:12:12 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:12:12 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:14:47 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user Omen16\seans SID (S-1-5-21-885587194-2609459467-771910491-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Error 01/11/2025 10:15:05 Microsoft-Windows-TPM-WMI 1796 None The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult Error code: 0x800700c1. For more information, please see Secure Boot DB and DBX variable update events - Microsoft Support
Warning 01/11/2025 10:18:55 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:18:55 Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:18:55 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning 01/11/2025 10:18:55 Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

glasskuter · Nov 3, 2025

If this happened only once maybe windows update was applying an update in the background at boot.
If everything is normal now, I wouldn't worry about it.

steamship · Nov 4, 2025

glasskuter said:
If this happened only once maybe windows update was applying an update in the background at boot.
If everything is normal now, I wouldn't worry about it.

With Windows updates, I usually choose the option to Update and Restart. I then login in again and then choose Shut Down.

Bearing in mind that the laptop hasn't even gotten to the POST screen, how is it possible for Windows to perform updates?

Rollback_Jockey · Nov 4, 2025

Try the following in an elevated powershell, one after the other:-

DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase

DISM /Online /Cleanup-Image /RestoreHealth

SFC /ScanNow

Try3 · Nov 4, 2025

Check your Bios settings for something like my computer's POST behaviour, FastBoot setting:-

09.05 POST behaviour, FastBoot - closeup.webp

Denis

JLArranz · Nov 4, 2025

Unlike my desktops, my miniPC (more similar to a laptop) doesn't beep when it posts successfully. Up to now no POST issues. What I'm asking here is if your laptop can do beeps. Nothing "Windows" (or DOS or Linux or whatever) is done in a computer until the POST succeeds.

A suspect is an intermittent hw difficulty that delays the POST. When I upgraded the RAM in one desktop, the "black screen" interval went from about 1-2 seconds to 9-10 seconds. I'm sure the actual interval is very exact in both cases, but I haven't measured it with precision. I attribute this difference to the "auto tune" (whatever the name) the BIOS does with the RAM, more difficult after the upgrade. There's even a setting in the BIOS about that (it's a year 2009 high-end motherboard with some low level settings). The 16 GB it has now is its maximum, previously it had 8 GB.

I think you should ascertain if the issue is pre-POST or post-POST, enabling the beep or connecting a "PC speaker" if possible (*), the HD LED if present (pre-POST it might be solid on or off but not blinking irregularly as if the HD was working) or whatever can help you, like noise patterns specially fans.

(*) The "PC speaker" doesn't have to do at all with the speakers connected to the sound card. In non pre-built desktops it's part of the case, it's either in the case itself and a cable goes to the motherboard, or in a small bag along with screws and similar stuff. The historically initial role of this device is just signaling a successful POST with one short beep, afterwards the BIOS makers invented sound codes (two short beeps, one long beep, several short,...) to signal different causes for not posting. Some motherboards have LEDs or even seven-segment (numbers) displays for this.

Scott · Nov 4, 2025

I like to hear the POST beep(s)

https://www.amazon.com/Motherboard-Computer-Casemini-Speakers-Internal/dp/B088KN6B9Q/

steamship · Nov 5, 2025

Rollback_Jockey said:
Try the following in an elevated powershell, one after the other:-

DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase

DISM /Online /Cleanup-Image /RestoreHealth

SFC /ScanNow

The results from running these are as follows:

- DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.6899

[==========================100.0%==========================]
The operation completed successfully.

- DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.6899

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

- SFC /ScanNow

Windows Resource Protection could not start the repair service

I had to run these commands to get 'SFC /ScanNow' to run:
sc config trustedinstaller start= auto
net start trustedinstaller

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

These are the corrupt files found:

2025-11-05 18:58:05, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthA2dp.sys
2025-11-05 18:58:05, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthA2dp.sys
2025-11-05 18:58:05, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthHfEnum.sys
2025-11-05 18:58:05, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthHfEnum.sys
2025-11-05 18:58:05, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\bthmodem.sys
2025-11-05 18:58:05, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\bthmodem.sys

Bluetooth drivers, which I don't even have enabled.

Search

Long Delay Before Splash Screen Appears Prior to Windows Starting

steamship

Well-known member

My Computer

System One

glasskuter

aka Mama Glass

My Computers

System One System Two

steamship

Well-known member

My Computer

System One

Rollback_Jockey

Well-known member

My Computers

System One System Two

Try3

Well-known member

My Computer

System One

JLArranz

Active member

My Computer

System One

Scott

Well-known member

My Computers

System One System Two

steamship

Well-known member

My Computer

System One

Similar threads

Latest Support Threads

Latest Tutorials