The obsession with the "Quiet Boot"

It is a personal thing for Operating System, but I have an obsession with the "Quiet Boot". If your computer and OS configuration is stable, why do you want to see all the messaged on the boot of the OS every time you turn it on?

The idea will be that you will only see some error on boot if something is not working as it should, like the case of some device driver being not able to start the device, or something that had changed on your computer that is causing issued on boot.

I want to use this wiki page to document which drivers are not able to be quiet on boot, just to dream forward that someday this list will change.

Which drivers can not be "Quiet"

 * ACPI.PSD :


 * JFS.IFS :


 * VBOXGUEST.SYS : I opened a ticket suggestion this (2017/07), but there had been no reply


 * TCPBEUI.OS2 : I think it is putting an empty space.


 * NETBIOS.OS2 : It produce a blank line when booting.


 * LVMALERT.EXE : It produce a blank line when booting.


 * CNTRL.EXE: It produce a blank line when booting.


 * ACPIDAEMON.EXE: It produce a blank line when booting.

A step closer to the dream

 * IFX.EXE : For version 1.22 a /Q mode was included. Thanks.