Windows 10: Alphanumeric object in the DVD BCD

Hi

After putting the DVD of Windows 10 in a DVD player and executing the command

Code: C:\WINDOWS\system32>bcdedit /store "D:\boot\bcd" Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows bootmenupolicy Standard detecthal Yes winpe Yes ems No[/quote] I noticed that the values of the osdevice and device elements end with an alphanumeric object.

What is this object? There is an alias for this object?

Thanks

Bye

:)

 

Error Code: 0xc0000034 after upgrade to Windows 10 from Window 7 - Boot Configuration Data file missing required information

I have looked for this problem but all suggest to boot using Windows Installation CD/DVD/USB and get those BCD information. But here problem occurs due to new upgrade i.e. Window 10 and I don't have any way to get that BCD information. Please help to resolve
this.

 

Windows 10 winload.exe status 0xc0000428 after firmware update motherboard

Many thanks to Abdul and Ratandeep for their quick response.

After 4 days of research and trial and error, I finally got back into my win 10 installation.

Looks like after the firmware upgrade of the motherboard, the bootfiles the system uses were nor on my win 7 disk, neither on the win 10 ssd but on the 3 of my 4 disk which is used by Acronis for backup.

I went into recovery prompt mode and on this disk the bootrec /rebuildbcd command found my win 10 installation and added it to the bcd.

I then made the bcd file on the ssd visible by attrib bcd -h -r -s and copied the correct bcd to the ssd.

PS One of my Original problems was that I could not boot from DVD. Although I was able to write the dvd, it would not recognize the drive while booting. Changing to another loose sata cable (other port) solved this problem ???

All in all, I am now a happy win 10 user again ! Thanks again guys

 

It is called: GUID
Globally unique identifier - Wikipedia, the free encyclopedia

 

If I run this command on another computer, this GUID changes?

Thanks

Bye

 

Yes. The GUID is pointing to the DVD drive. Think of the GUID as a serial number for that drive. Different drive in a different computer means different GUID. It's used so the program always looks in the same place for data once it starts, regardless of what drive letter is assigned, in this case back to the device that was used to boot with.

The command bcdedit is processing the information it is reading from the BCD store, not just displaying the read only file. If you open the bcd store file in notepad, all you will see is unreadable binary garbage.

 

So, can you explain one thing:

I copied the contents of the DVD on my hard disk and then I wrote the following commands:

Code: C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows bootmenupolicy Standard detecthal Yes winpe Yes ems No C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" /set {default} osdevice ramdisk=[boot]\sources\boot.wim,{ramdiskoptions} Operazione completata. C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" /set {default} device ramdisk=[boot]\sources\boot.wim,{ramdiskoptions} Operazione completata. C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{ramdiskoptions} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{ramdiskoptions} systemroot \windows bootmenupolicy Standard detecthal Yes winpe Yes ems No C:\WINDOWS\system32>[/quote] Why, in the final output, the ramdiskoptions alias is not converted into its alphanumeric code as it is done in the initial output?

Thanks

Bye

 

That one I don't know. I am not that well versed in BCD functioning. Looking forward to answers that the experts might offer, though, because it is something I want to learn more about.

 

First, you should show all entries in the Boot Code (/v is verbose mode - it shows the GUID for well known objects)

bcdedit /v /enum all

That will help you understand the relationships.

Code: Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} description Windows Boot Manager locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {7619dcc9-fafe-11d9-b411-000476eba25f} displayorder {7619dcc9-fafe-11d9-b411-000476eba25f} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 30 Windows Boot Loader ------------------- identifier {7619dcc9-fafe-11d9-b411-000476eba25f} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} . . .Device options -------------- identifier {7619dcc8-fafe-11d9-b411-000476eba25f} ramdisksdidevice boot ramdisksdipath \boot\boot.sdi[/quote] If you follow the GUID reference to the identifier, it becomes clear that the Boot code on the DVD says:
Create a RAMdisk to use as the boot device

Boot to ramdisksdidevice {7619dcc8-fafe-11d9-b411-000476eba25f}
Load System Deployment Image (boot\boot.sdi)
Load WinPE (\sources\boot.wim)




Source
Sometimes the GUIDs are very close - so you have to read them carefully

Windows Boot Loader
-------------------------
identifier {7619dcc9-fafe-11d9-b411-000476eba25f} device {7619dcc8-fafe-11d9-b411-000476eba25f}
If you're going to experiment - make sure you back up your BCD, even if you're working on a different store. It's not hard to forget to specify /store and then you're working on the live BCD file.

bcdedit /export <filename>

Example: bcdedit /export "C:\Data\BCD Backup"

This command exports the contents of the system store into a file. This file can be used later to restore the state of the system store. This command is only valid for the system store.

<filename>
The filename to be used as the destination for the export. If the filename contains spaces, it must be enclosed in quotation marks ("").

 

If you follow the GUID reference to the identifier, it becomes clear that the Boot code on the DVD says:
Create a RAMdisk to use as the boot device

Boot to ramdisksdidevice {7619dcc8-fafe-11d9-b411-000476eba25f}
Load System Deployment Image (boot\boot.sdi)
Load WinPE (\sources\boot.wim)


Source
Sometimes the GUIDs are very close - so you have to read them carefully

Windows Boot Loader
-------------------------
identifier {7619dcc9-fafe-11d9-b411-000476eba25f} device {7619dcc8-fafe-11d9-b411-000476eba25f}
If you're going to experiment - make sure you back up your BCD, even if you're working on a different store. It's not hard to forget to specify /store and then you're working on the live BCD file.bcdedit /export <filename>

Example: bcdedit /export "C:\Data\BCD Backup"

This command exports the contents of the system store into a file. This file can be used later to restore the state of the system store. This command is only valid for the system store.

<filename>
The filename to be used as the destination for the export. If the filename contains spaces, it must be enclosed in quotation marks ("").
[/quote] Code: C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" /v /enum all Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} description Windows Boot Manager locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {7619dcc9-fafe-11d9-b411-000476eba25f} displayorder {7619dcc9-fafe-11d9-b411-000476eba25f} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 30 Windows Boot Loader ------------------- identifier {7619dcc9-fafe-11d9-b411-000476eba25f} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows bootmenupolicy Standard detecthal Yes winpe Yes ems No Windows Memory Tester --------------------- identifier {b2721d73-1db4-4c62-bf78-c548a880142d} device boot path \boot\memtest.exe description Windows Memory Diagnostic locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} Settings Emergency Management Services ------------ identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9} bootems No debugger settings ----------------- identifier {4636856e-540f-4170-a130-a84776f4c654} debugtype Serial debugport 1 baudrate 115200 Global settings --------------- identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} inherit {4636856e-540f-4170-a130-a84776f4c654} {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9} 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} description Hypervisor Settings hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Device options -------------- identifier {7619dcc8-fafe-11d9-b411-000476eba25f} ramdisksdidevice boot ramdisksdipath \boot\boot.sdi C:\WINDOWS\system32>bcdedit /store "C:\Users\\Downloads\DVD\boot\bcd" /enum all Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows bootmenupolicy Standard detecthal Yes winpe Yes ems No Windows Memory Tester --------------------- identifier {memdiag} device boot path \boot\memtest.exe description Windows Memory Diagnostic locale en-US inherit {globalsettings} Settings Emergency Management Services ------------ identifier {emssettings} bootems No debugger settings ----------------- identifier {dbgsettings} debugtype Serial debugport 1 baudrate 115200 Global settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} Boot Loader Settings ------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} description Hypervisor Settings hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Device options -------------- identifier {7619dcc8-fafe-11d9-b411-000476eba25f} ramdisksdidevice boot ramdisksdipath \boot\boot.sdi C:\WINDOWS\system32>[/quote] By chance, this is an internal alias for the "Device options" object?

Its alphanumeric string is fixed or changes each boot or any device used? If it changes, what should I put in the osdevice and device elements to avoid boot problems?

Thanks

Bye

 

From your code box (I removed ramdisk=[boot]\sources\boot.wim, from the Boot loader section to make the relationship clearer)

Windows Boot Loader device {7619dcc8-fafe-11d9-b411-000476eba25f} osdevice {7619dcc8-fafe-11d9-b411-000476eba25f} Device options
identifier {7619dcc8-fafe-11d9-b411-000476eba25f}
You're right on target - the GUID in Bootloader referenced the information in Device options

Does it change? Yes and no - it all depends on the ISO or tool used to create the bootable device.

Rather than mucking about in the boot code for simple things, let the tool create what's needed.

Why do you want to to do this? If you want to copy USB install media - just copy it - the boot structure is the same.

It's only when you have multiple installs that you have to worry about what partition the install is on so you can tell the boot manager to load Windows from there.

On external boot media, you always boot from the media.

A Repair USB is a bit different - it has to know where the recovery partition is located.

I'm not sure this is the best way to learn about the boot code. You have a starting point, now you should read a lot more.

Here are two tools for editing BCD

Visual BCD Editor

EasyBCD - NeoSmart Technologies
scroll down to the free version - registration required to download)
alternative download: EasyBCD - MajorGeeks

 

Then, the {7619dcc8-fafe-11d9-b411-000476eba25f} string always identifies the "Device options" object . Right?

This also applies to Windows 7/8.x or this string is different?

Thanks

Bye

 

No not always. I showed you examples form my machine and they were different form your machine, so the answer is the GUIDs will be different on every machine.

This is why you need to read more about boot code. I'm not going to be able to provide proper instruction. I asked why you're doing this and didn't get an answer, so I'll bow out at this point. You have a start, not sure what you're doing, but you have a start.

The GUIDs are created when the boot store is created and have no reference outside of that store. The external references might be different on machines as well (I might boot from D: which is the 5th partition on drive 4) that would be different from C:, right?

I think you're looking for an answer that can't be answered.

A GUID always identifies an object - the GUID will be different on different machines.
Walk down the BCD you have and match the labels in each object to the GUIDs throughout that store.

You can compare it to your live BCD store

bcdedit /v /enum all > %TEMP%\bcdLive.txt

That's all I have, good luck.

Bill.