Cannot boot from Flash Drive

[David Bailey]

Hi David,

Do you get an extra boot menu entry every time you start the machine - or is it assigned to a hotkey?

Yep, every time you restart.

I guess if you don't want it any more, you just disable it in the startups.

To get rid of it:



Then:



It will be gone.

 

[David Bailey]

David
Yep, every time you restart.

Why don't you assign it hotkey instead?

Shouldn't be difficult.

post the output of bcdedit -enum -v

That is beyond my expertise.

 

[whs]

David
Yep, every time you restart.

Why don't you assign it hotkey instead?

Shouldn't be difficult.

post the output of bcdedit -enum -v

That is beyond my expertise.

No expertise required. Just paste bcdedit -enum -v into an elevated command prompt and hit Enter. Then copy the cmd window content (rightclick > select all > right click anywhere on the highlighted area > it's now on the clipboard > paste it here).

 

[David Bailey]

Why don't you assign it hotkey instead?

Shouldn't be difficult.

post the output of bcdedit -enum -v

That is beyond my expertise.

No expertise required. Just paste bcdedit -enum -v into an elevated command prompt and hit Enter. Then copy the cmd window content (rightclick > select all > right click anywhere on the highlighted area > it's now on the clipboard > paste it here).

This it ?

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


C:\WINDOWS\system32>bcdedit -enum -v


Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {dbafbbe4-6c4e-11e3-be6e-eca86bae535c}
resumeobject {dbafbbe3-6c4e-11e3-be6e-eca86bae535c}
displayorder {dbafbbe4-6c4e-11e3-be6e-eca86bae535c}
{6670c44c-83b0-11e3-beae-eca86bae535c}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 10


Windows Boot Loader
-------------------
identifier {dbafbbe4-6c4e-11e3-be6e-eca86bae535c}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 8.1
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {dbafbbe5-6c4e-11e3-be6e-eca86bae535c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {dbafbbe3-6c4e-11e3-be6e-eca86bae535c}
nx OptIn
bootmenupolicy Standard


Windows Boot Loader
-------------------
identifier {6670c44c-83b0-11e3-beae-eca86bae535c}
device ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
path \windows\system32\boot\winload.efi
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot \Windows
detecthal Yes
winpe Yes


C:\WINDOWS\system32>bcdedit -enum -vbcdedit -enum -v

 

[David Bailey]

I think some good info has been posted here today.
I repped everybody.

 

[SIW2]

Is there a bit missing from the last entry?

 

[David Bailey]

Is there a bit missing from the last entry?

I selected All & copied it & posted it here.
It is as it is.

 

[SIW2]

My fault, It should be bcdedit -enum all -v

Looking for the Device Options entry.

At a guess it will like this:
Device options
--------------
identifier {whatever}
description Macrium Reflect System Recovery
ramdisksdidevice partition=C:
ramdisksdipath [C:]\boot\macrium\macrium.sdi

 

[David Bailey]

My fault, It should be bcdedit -enum all -v

Looking for the Device Options entry.

At a guess it will like this:
Device options
--------------
identifier {whatever}
description Macrium Reflect System Recovery
ramdisksdidevice partition=C:
ramdisksdipath [C:]\boot\macrium\macrium.sdi

Here is the new one:

custom:46000010 Yes


Windows Boot Loader
-------------------
identifier {6670c44c-83b0-11e3-beae-eca86bae535c}
device ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
path \windows\system32\boot\winload.efi
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot \Windows
detecthal Yes
winpe Yes


Windows Boot Loader
-------------------
identifier {dbafbbe4-6c4e-11e3-be6e-eca86bae535c}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 8.1
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {dbafbbe5-6c4e-11e3-be6e-eca86bae535c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {dbafbbe3-6c4e-11e3-be6e-eca86bae535c}
nx OptIn
bootmenupolicy Standard


Windows Boot Loader
-------------------
identifier {dbafbbe5-6c4e-11e3-be6e-eca86bae535c}
device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Win
re.wim,{dbafbbe6-6c4e-11e3-be6e-eca86bae535c}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Win
re.wim,{dbafbbe6-6c4e-11e3-be6e-eca86bae535c}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
custom:46000010 Yes


Resume from Hibernate
---------------------
identifier {152a5d5e-6c34-11e3-b269-eca86bae535c}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {152a5d60-6c34-11e3-b269-eca86bae535c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No


Resume from Hibernate
---------------------
identifier {dbafbbe3-6c4e-11e3-be6e-eca86bae535c}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {dbafbbe5-6c4e-11e3-be6e-eca86bae535c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No


Windows Memory Tester
---------------------
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes


EMS Settings
------------
identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems No


Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200


RAM Defects
-----------
identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}


Global Settings
---------------
identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
advancedoptions Yes
optionsedit No
custom:16000067 No
custom:16000068 No
custom:16000069 No


Boot Loader Settings
--------------------
identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}


Hypervisor Settings
-------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200


Resume Loader Settings
----------------------
identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}


Device options
--------------
identifier {152a5d61-6c34-11e3-b269-eca86bae535c}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi


Setup Ramdisk Options
---------------------
identifier {ae5534e0-a924-466c-b836-758539a3ee3a}
description Macrium Reflect System Recovery
ramdisksdidevice partition=C:
ramdisksdipath \boot\Macrium\boot.sdi


Device options
--------------
identifier {dbafbbe2-6c4e-11e3-be6e-eca86bae535c}
description Windows Setup
ramdisksdidevice partition=C:
ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi


Device options
--------------
identifier {dbafbbe6-6c4e-11e3-be6e-eca86bae535c}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume5
ramdisksdipath \Recovery\WindowsRE\boot.sdi


C:\WINDOWS\system32>

 

[SIW2]

These are the bits we are interested in:

Windows Boot Loader
-------------------
identifier {6670c44c-83b0-11e3-beae-eca86bae535c}
device ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
path \windows\system32\boot\winload.efi
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot \Windows
detecthal Yes
winpe Yes

Setup Ramdisk Options
---------------------
identifier {ae5534e0-a924-466c-b836-758539a3ee3a}
description Macrium Reflect System Recovery
ramdisksdidevice partition=C:
ramdisksdipath \boot\Macrium\boot.sdi

 

[David Bailey]

These are the bits we are interested in:

Windows Boot Loader
-------------------
identifier {6670c44c-83b0-11e3-beae-eca86bae535c}
device ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
path \windows\system32\boot\winload.efi
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\wadkfiles\media\sources\boot.w
im,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot \Windows
detecthal Yes
winpe Yes

Setup Ramdisk Options
---------------------
identifier {ae5534e0-a924-466c-b836-758539a3ee3a}
description Macrium Reflect System Recovery
ramdisksdidevice partition=C:
ramdisksdipath \boot\Macrium\boot.sdi

What are they useful for ?

I have never dealt with something like this before.

 

[SIW2]

They are useful for me .

If you want to have it on a key, e.g. F9 and not interrupting your startup by being on the visible boot menu, use visualbcd.

Great program. Looks complicated at first, but it isn't really.

D/l it from here: 0.9.3.1

Select New > Custom Actions




Select Macrium in the bottom dropdown, and whatever F key you want in the top dropdown. Then click ADD.




Now it will be on F9 at startup. But it is still on the boot menu.

Remove it from the menu by highlighting bootmgr in the left pane, then click Display order.





Select macrium and delete.

 

[David Bailey]

I get an error message:

 

[SIW2]

Might be an oem protective mechanism. They sometimes do that to be a pain.

You can do it with bcdedit. The purpose of using visualbcd is to find out if you already have custom actions.

They must be sequential. 0x54000001 0x54000002 etc. If you don't already have any, then start with 0x54000001

bcdedit -set {bootmgr} custom:0x54000001 {loader-guid}
bcdedit -set {bootmgr} customactions 0x10000SCANCODE0001 0x54000001

your loader-guid is {6670c44c-83b0-11e3-beae-eca86bae535c}and scancode for F9 is 4300

bcdedit -set {bootmgr} custom:0x54000001 {6670c44c-83b0-11e3-beae-eca86bae535c}
bcdedit -set {bootmgr} customactions 0x1000043000001 0x54000001

 

[David Bailey]

Might be an oem protective mechanism. They sometimes do that to be a pain.

You can do it with bcdedit. The purpose of using visualbcd is to find out if you already have custom actions.

They must be sequential. 0x54000001 0x54000002 etc. If you don't already have any, then start with 0x54000001

bcdedit -set {bootmgr} custom:0x54000001 {loader-guid}
bcdedit -set {bootmgr} customactions 0x10000SCANCODE0001 0x54000001

your loader-guid is {6670c44c-83b0-11e3-beae-eca86bae535c}and scancode for F9 is 4300

bcdedit -set {bootmgr} custom:0x54000001 {6670c44c-83b0-11e3-beae-eca86bae535c}
bcdedit -set {bootmgr} customactions 0x1000043000001 0x54000001

I appreciate your efforts but I'm really not interested in an F KEY.

Someone here might though.

I would give you a rep but I have to spread some around first.

 

[SIW2]

Yes, it is tricky with an oem machine. That may be why macrium doesn't bother and just adds a simple boot menu entry.

 

[David Bailey]

Yes, it is tricky with an oem machine. That may be why macrium doesn't bother and just adds a simple boot menu entry.

The boot menu option works good & you can easily remove it.

I leave it on all the time because I never know when my computer will go haywire.

I use BootUI tuner from Winaero also.

It works good too.

WinAero: Downloads / Software / Boot UI Tuner

 

[David Bailey]

This thread has taught me something about human nature.
I like learning new stuff.

It gives me a guideline of how to do things in the future.

 

[whs]

This thread has taught me something about human nature.
I like learning new stuff.

It gives me a guideline of how to do things in the future.

This is interesting. Would you share the things it taught you. When I posted my little problem, I did not think the thread would have such a success - and longh after my problem was solved.

 

[SIW2]

It doesn't substitute for external media - that is always needed just in case. Access from boot menu can be an extra convenience.

I just made the standard macrium winpe thing on my machine. It doesn't seem to offer to add a menu option. Is it hidden somewhere?

No biggie, if you know where the wim and sdi are, can be added to boot display menu without any trouble. ( Hotkey is better, but more difficult to do. )