A bad configuring in bcdedit is recovered but how to make sure the Boot Loader is valid again?

Question

The truncatememory command results in bad configuration by allocating a wrong hexadecimal (probably to insufficient memory 0x1--), system is restored by external cmd*, truncatememory is deletedvalue and allowedinmemorysettings acquires a new value that amounts to 2 GB (from a previous 0x1-- to 0x8--). Task manager reports again the initial 3.5 GB available from 4.0 installed,

but how to be sure allowedinmemorysettings is properly configured? (possibly its initial code included letters with numerics?)

Answer 1

Hello there,

Yes the Bootloader should have the exact value .

The BCD Windows Management Instrumentation (WMI) provider consists of a set of classes exposed as COM objects that support programmatic access to BCD stores. The BcdElement class is the base for all elements. Each BCD element represents a specific boot option. All elements share a common header that describes the element type and data format.

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

Indicates whether or not an in-memory BCD setting passed between boot apps will trigger BitLocker recovery. This value should not be modified as it could trigger a BitLocker recovery action. The element data format is BcdIntegerElement.

Ref:
https://learn.microsoft.com/en-us/previous-versions/windows/desktop/bcd/bcdlibraryelementtypes

Answer 3

However, you could check this contiguous query that comes up at

https://learn.microsoft.com/en-us/answers/questions/1160369/to-what-should-be-ascribed-a-discrepancy-in-the-bc

If you may, do not think it is not congruous with the present query, but it's faithfully constructed..