Numbered Menu does not appear in Advanced Startup

Berton said:

I'm probably reading the F/numbered menu part wrong but that suggests the prompt of pressing the F2, F12, Del or Esc key to enter BIOS Setup or Boot choices which appear after maker's logo appears and are not strictly a Windows issue. The BIOS loads followed by the OS/Operating System reading the settings in it so the OS knows what resources are available and sets the machine up as it needs. Sometimes a reboot won't show those while a full shutdown then startup will show them.

I am specifically referring to this menu


- - - Updated - - -

topgundcp said:

You actually don't need to boot into Recovery mode to disable Driver Signature Enforcement.

OPTION 1:
Open Admin Command prompt :
To disable. Copy and paste these 2 commands:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON

To enable: Copy and paste these 2 commands
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF

OPTION 2:
Or use Group Policy:WIN+R and type: gpedit.msc
User Configuration->Administrative Templates->System->Driver Installation->Code signing for device drivers entry->Enabled
then select Ignore from drop down list box.

Restart your PC to take effect

Now Since your EFI Boot partition is on disk 0 and your Windows is on Disk 1. It's easy just to create a EFI Boot partition on disk 1 then delete the EFI partition on Disk 0.

Problem is I've already tried those 2 solutions and they've failed me.I am currently in "Test Mode" and the program is STILL ​activated.I am at a loss on what to do now...The only thing left is popping up the F-menu and try to disable it that way...

topgundcp said:

Looking at the Recovery partition, the size is only 481MB where Winre.wim is loacated. Version 1909 of Windows should have 529M since the WinRe.wim will occupy around 428MB so I wonder if the WinRe.wim in your PC is the latest for this version. Open the Admin command and type:
reagentc /disable
This will move the WinRe.wim back to: C\Windows\System32\Recovery
Set the folder option to show hidden files and report back the size of WinRe.wim. Once done you can enable it again: Reagentc /enable.

topgundcp said:

My version that came with Win10 Fresh install has different size:

Do you have Win 10 version 1909 ISO available ? If so, mount it then use 7-zip to open the install.esd or install.wim under Sources folder, Navigate to Windows\systems32\Recovery and copy both WinRe.wim and ReAgent.xml to Destop first. Use reagentc to disable then copy both the Recovery partition, Re-enable with reagentc. Should put the new version to Recovery partition.

If fail, you might have to re-create the Recovery partition with size=529MB

Actually I'm planning to do a fresh OS install since I'm having trouble downloading a game.(It's launcher refuses to show it's interface) so I wanted to ask, is there a "shortcut", in order to avoid the hassle of setting up every single thing all over again ? Is there a utility to do just that? Or am I gonna have to organize it from scratch ? Thanks for replying, really appreciate your fast help.
Have a good night/day.

dalchina said:

There are 3 ways to try to avoid manually reinstalling and recreating everything:

1. Routinely use disk imaging (as is so often advised here- e.g. Macrium Reflect free-paid) so if you have a recent disk image before things went haywire you can restore that. (No good if before your oldest image of course, or it would mean reverting key data to an older version).

2. An in-place upgrade repair install - rebuilds Windows - replacing system files, services to default etc just like a feature update (upgrade) - takes current build number backwards.
Does not fix user profile problems, so if you don't have the same problem with a different (new) user, it may not help.

3. Use a 3rd party program such as Laplink PCMover or Easeus PCTrans to transfer programs and data from 1 installation to another. One off usage license. Cheaper if you use the disk image approach and version of those- or it used to be- and easier.

When I tried to install the game from within Windows Sandbox, there was no issue.
Are those methods guaranteed to solve my problem? Method 2 seems good but I’m a bit skeptical.
As always thank you for assisting me immediately.
Also good morning.