[FEATURE REQUEST] - Preserve bcd description

%3CLINGO-SUB%20id%3D%22lingo-sub-1953066%22%20slang%3D%22en-US%22%3E%5BFEATURE%20REQUEST%5D%20-%20Preserve%20bcd%20description%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1953066%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20performing%20an%20in-place%20upgrade%20please%20save%20the%20bcdedit%20%7Bcurrent%7D%20description%20into%20a%20variable%20%2F%20textfile%20to%20restore%20it%20after%20a%20successful%20upgrade.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ereason%3A%3C%2FP%3E%3CP%3EUsers%20with%20multiboot%20systems%20have%20to%20restore%20their%20description%20for%20individual%20OSes%20after%20every%20upgrade.%3C%2FP%3E%3CP%3EWhich%20means%20nearly%20every%20week%20when%20being%20in%20Insider%20Dev.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecurrently%20setup%20will%20reset%20the%20bcd%20description%20to%20Windows%20or%20Windows%20Server%20after%20an%20upgrade.%3C%2FP%3E%3CP%3EWhich%20makes%20it%20hard%20to%20distinguish%20the%20OSes%20in%20the%20first%20place.%20As%20the%20volume%20IDs%20do%20not%20help%20much.%3C%2FP%3E%3CP%3EThank%20you%20for%20consideration%20%2F%20triage%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F53017%22%20target%3D%22_blank%22%3E%40Elden%20Christensen%3C%2FA%3E%26nbsp%3Band%20team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1953066%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServer%202019%20Preview%20LTSC%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2226128%22%20slang%3D%22en-US%22%3ERe%3A%20%5BFEATURE%20REQUEST%5D%20-%20Preserve%20bcd%20description%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2226128%22%20slang%3D%22en-US%22%3EDear%20Server%20Team%2C%3CBR%20%2F%3EI%20am%20aware%20that%20using%20a%20multi-boot%20Windows%20OS%20enviroment%20is%20not%20the%20usual%20production%20scenario%20by%20far.%20I%20hope%20you%20can%20discuss%20with%20the%20relevant%20team%20if%20this%20proposal%20I%20have%20suggest%20in%20the%20feedback%20hub%20is%20technically%20sufficient.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FAA6x3x6%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FAA6x3x6%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20change%20would%20affect%20Windows%2010%20SAC%20%2F%20LTSC%20and%20also%20Windows%20Server%20version%20xxxx%2C%20SAC%20%2F%20LTSC%20setup.%3CBR%20%2F%3E%3CBR%20%2F%3Ebasically%20also%20Azure%20Stack%20HCI%2C%20but%20given%20the%20usecaase%20it%20will%20not%20be%20as%20relevant%20as%20weekly%20installing%20and%20restoring%20descriptions%20and%20boot%20menu%20default%20time%20out%20in%20other%20SKUs.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20your%20feedback%20on%20this.%3C%2FLINGO-BODY%3E
Frequent Contributor

When performing an in-place upgrade please save the bcdedit {current} description into a variable / textfile to restore it after a successful upgrade.

 

reason:

Users with multiboot systems have to restore their description for individual OSes after every upgrade.

Which means nearly every week when being in Insider Dev.

 

currently setup will reset the bcd description to Windows or Windows Server after an upgrade.

Which makes it hard to distinguish the OSes in the first place. As the volume IDs do not help much.

Thank you for consideration / triage @Elden Christensen and team.

1 Reply
Dear Server Team,
I am aware that using a multi-boot Windows OS enviroment is not the usual production scenario by far. I hope you can discuss with the relevant team if this proposal I have suggest in the feedback hub is technically sufficient.

https://aka.ms/AA6x3x6

This change would affect Windows 10 SAC / LTSC and also Windows Server version xxxx, SAC / LTSC setup.

basically also Azure Stack HCI, but given the usecaase it will not be as relevant as weekly installing and restoring descriptions and boot menu default time out in other SKUs.

Thanks for your feedback on this.