Windows 10: Change BCD during setup/upgrade to show edition etc.

Every time windows setup installs or upgrades a windows 10 installation, it changes a meaningful (to me) edited BCD bootmenu entry to plain boring uninformative "Windows 10" - sometimes "on volume x" if it is multibooting:





I know I can edit the entry after the fact, and more than one ways how to do it.

The volume number entry is plain un-Windows like - why not give a volume label - labels are at least more permanent - I can understand why not the (worse than useless, and long outdated) "drive letter" is not used, since it is more often than not "C:", but where in Windows can you find the volume number without going into Diskpart, or other low level utilities?

Is there no way during or prior to setup to define what the bootmenu entry for the new installation or upgrade will be? A clever app maybe that I haven't spotted?

Or a clever way to automatically change this during OOBE?

:)

 

Feature update to Windows 10, version 1709 fails to install

You are welcome. I think that is correct. The clean install already went through Windows Update to pull in OS Build
16299.309 which is currently the latest one. It was the system partition (that holds the BCD) on the HDD that was the real troublemaker. That BCD was activating during reboots that required the one on the SSD, I think. Windows writes to them during an
upgrade.

 

Windows 10 upgrade consistently fails at 24% (installing from USB created with the 'creation tool')

Not the case, Ubuntu had been removed and none of its partitions nor UEFI boot entry existed. However during that install Grub did alter the BCD..

In short, at the time of Windows 10 upgrade there was no Linux anything left on the system except a modified BCD..

 

If you aren't using a OEM key you could try creating a script %WINDIR%\Setup\Scripts\SetupComplete.cmd

Code: bcdedit /set {current} description "Whatever"[/quote] Add a Custom Script to Windows Setup

 

Thanks Ix07, I'll try to get my head around that tomorrow and post back if & when I have any success - it looks like I shall have to open up a VM to do it!