Is it really necessary to get it out of bcdedit specifically ?Merci pour la suggestion, @Ginko!
This is a very fair request. Unfortunately getting the correct encoding out of bcdedit is a serious pain; getting it to work for EasyBCD required some rather dark magic, but it shouldn't be too hard to replicate that with iReboot as it has been working swimmingly and without any complaints in EasyBCD for some time now.
The only thing that matters here is identifying the console encoding, there is no need to change the console behaviour in any manner.Those APIs cannot be used (as in, they do not have the intended effect) when calling a console application from a .NET process. You can see the discussion here: Force StandardOutputEncoding to UTF8
The only thing that matters here is identifying the console encoding, there is no need to change the console behaviour in any manner.
The correct encoding is handled by EasyBCD, why iReboot, which is supposed to have been written by the same programmer or programming team, couldn't be able to do the same?
Unfortunately getting the correct encoding out of bcdedit is a serious pain; getting it to work for EasyBCD required some rather dark magic, but it shouldn't be too hard to replicate that with iReboot as it has been working swimmingly and without any complaints in EasyBCD for some time now.