Startup Boot Choice Delay Length

I have been trying to get the delay in which Windows sits at startup with the f2/del boot choice, f8 for this, f11 for that menu. No matter what I do it never changes from 30 seconds. I have changed it in the Computer Configuration tool to various numbers. I have used BCDedit /timeout function. Both of them record the change on the gui as well as bcdedit /enum and it reports that the change has been made but upon boot it still is 30 seconds. I have changed the Advanced System Settings "Startup and Recovery" menu with the time to display boot choice and time to display recovery if necessary time outs that doesn't change anything. There is a function in my ASRock uefi settings that mentions a startup delay but doesn't seem to change anything. I read that BitLocker and/or Secure Boot may inhibit the change but with any combination of them being on or off makes a difference I am not sure what the dilemma is but it is driving me crazy. I am not trying to use Fast Boot. I just want to change it from 30 to 5ish seconds. It is seemingly a simple change but nothing I can do works.

Anyone have any suggestions? because I am out of ideas. Any tips at all would be appreciated. thanks

ASrock AB350M Pro 4, Ryzen 7 3800x, Aorus 3080 Master 10g Rev 2.0. 64gb G Skill Trident Z RGB 3200 (16x4). 2tb Samsung 970 M.2.

Dougyyyyy said:

Computer Configuration

Click to expand...

i'm assuming you meant System Configuration (msconfig), correct?

dacrone said:

View attachment 110620
i'm assuming you meant System Configuration (msconfig), correct?

Click to expand...

yeah thats the one my bad


Microsoft Windows [Version 10.0.26100.1876]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
flightsigning Yes
default {current}
resumeobject {7be44d91-2d79-11ef-bac1-ed94e47c4cb3}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 6

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {7be44d93-2d79-11ef-bac1-ed94e47c4cb3}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
flightsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {7be44d91-2d79-11ef-bac1-ed94e47c4cb3}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
bootlog Yes
sos Yes

change it in msconfig, then check if advanced system settings > startup and recovery > settings
reflects the same as msconfig

In MSCONFIG, the 30 second delay can be changed, but cannot be reduced to less than 3 seconds.
Just remove the Zero behind the 3, and don't forget to save your change.
That's one of the first things I do on every Windows Install. Been doing it for years.
I also go into "Advanced" and tell it how many CPU cores I want it to use.

Old habits die hard,
TM

Dougyyyyy said:

I have been trying to get the delay in which Windows sits at startup with the f2/del boot choice, f8 for this, f11 for that menu. No matter what I do it never changes from 30 seconds.

Anyone have any suggestions? because I am out of ideas. Any tips at all would be appreciated. thanks

ASrock AB350M Pro 4, Ryzen 7 3800x, Aorus 3080 Master 10g Rev 2.0. 64gb G Skill Trident Z RGB 3200 (16x4). 2tb Samsung 970 M.2.

Click to expand...

Perhaps you could upload a screenshot so people can see what you are referring to.

TechnoMage2021 said:

In MSCONFIG, the 30 second delay can be changed, but cannot be reduced to less than 3 seconds.
Just remove the Zero behind the 3, and don't forget to save your change.
That's one of the first things I do on every Windows Install. Been doing it for years.
I also go into "Advanced" and tell it how many CPU cores I want it to use.

Old habits die hard,
TM

Click to expand...

You are right about MsConfig however with sysdm.cpl , you can take it down further to 2 seconds!

TechnoMage2021 said:

In MSCONFIG, the 30 second delay can be changed, but cannot be reduced to less than 3 seconds.
Just remove the Zero behind the 3, and don't forget to save your change.
That's one of the first things I do on every Windows Install. Been doing it for years.
I also go into "Advanced" and tell it how many CPU cores I want it to use.

Old habits die hard,
TM

Click to expand...

I appreciate the response and not to be a jerk but as I said in my post that is precisely what I have been doing. I even posted the bcdedit /enum. I have tried MSConfig more times than I can count. Using both BCDEdit and the gui of msconfig. I have tried plethora of times. As you can see in my BCDEdit /enum currently it is set to 6 seconds but still takes 30 at startup. Tried selective start up, normal startup. I dont get it.

The Startup and recovery also makes no difference as I have tried an extensive number of combinations.

None of this delay stuff matters if the device only has one boot loader entry, which is the case here, as shown in post #3. Under those circumstances, you can set your delay to 10 seconds or 120 seconds; your PC will boot in the same amount of time.

It would be best if OP could take a picture or screenshot as requested by SIW2. This sounds more to me like a BIOS/UEFI boot menu than a Windows boot menu.

TechnoMage2021 said:

In MSCONFIG, the 30 second delay can be changed, but cannot be reduced to less than 3 seconds.
Just remove the Zero behind the 3, and don't forget to save your change.
That's one of the first things I do on every Windows Install. Been doing it for years.
I also go into "Advanced" and tell it how many CPU cores I want it to use.

Old habits die hard,
TM

Click to expand...

why bother specifying the processors at startup? what difference does that make?

That setting is used to limit the number of processors used (it's actually the number of threads, not physical cores). You would use that for debugging purposes really. If you want Windows to use all available processing power, just leave that setting alone.

pseymour said:

None of this delay stuff matters if the device only has one boot loader entry,

Click to expand...

Exactly.

dacrone said:

https://www.spamsite.com/threads/bo...Boot_Menu_Timeout_Wont_Change_from_30_seconds

This you? If so, how many OS are running on the drive?

Click to expand...

That's a spam site that copies our posts.

pseymour said:

None of this delay stuff matters if the device only has one boot loader entry, which is the case here, as shown in post #3. Under those circumstances, you can set your delay to 10 seconds or 120 seconds; your PC will boot in the same amount of time.

It would be best if OP could take a picture or screenshot as requested by SIW2. This sounds more to me like a BIOS/UEFI boot menu than a Windows boot menu.

Click to expand...

That is a very good point and I have wondered the same thing. In he UEFI I have scoured to see but the only time I see in there is set to 1 already but still stays at 30. The only other thing is to turn on fast boot but that has consquences.

Dougyyyyy said:

That is a very good point and I have wondered the same thing. In he UEFI I have scoured to see but the only time I see in there is set to 1 already but still stays at 30. The only other thing is to turn on fast boot but that has consquences.

Click to expand...

I have never see consequences on fastboot. Are you sure you are not confusing fastboot with fast start which often has consequences, especially on multiboot devices?