Minimize OS Problem

[PeterSt]

I am not sure about boleary's situation, but for Mani this may have happened :

I think we all know from W7 SP1 that at a (re)boot there can be this gray progress bar at the bottom of the screen which says "Windows is loading files" (that is, I don't recall this from W7 Vanilla ever). After this progress bar has filled up, the system goes into reboot automatically again.
This happens once in a while and I never saw the reason for it. But it does. Also, when you don't pay attention during the boot, it goes unnoticed. But :

What I expect is that this "resets" something Windows thinks is necessary. Something like a "last good boot situation". Now, it seems logical to me that this is taken from a (registry) "save" the OS always applies herself after a good boot, while Minimize OS goes a sort of against this. I know it does, or in other words, I know it can be done a tad more "official".
Btw, I never noticed this inconsistency.

Solution :
When you can see that the state of the Minimize OS button is not consistent with the actual situation, rightclick on the "Minimize OS" text which comes with the button, and choose to flip the state of the button (I think this is in the 0.9z-6 Release Notes as well). Now apply the reboot by means of the button and all should be as intended.
Keep in mind that the next (reboot) action at using the Minimize OS button is always taken upon its shown state. Thus, does it show "I'm minimized" (red) then using the button will go to normal. And the other way around;
When the shown state is the opposite from reality, a reboot using the button in that wrong state will always end up in how it was. So, reality is Normal but state shows Minimized, will obviously boot into normal again.

Important for your understanding :
The above anticipates a "normal" situation, no matter the shown state is inconsistent. Like the OS changing things behind "XX's back", like what could have happened to Mani.
This means that the state the button shows can only confuse you one time;
This is different from something being wrong at the reboot itself, which happened to Mani as well at using the beta-beta version for this, and what happened to someone else as well as which is why 0.9z-6-1b emerged. Then something really is wrong, and the state of the button will keep on being confusing forever.

Of course people will say : so show the real state - detect it;
This is not possible because all anticipates on the things you may have done yourself already. So, it may detect *that* and the button will stay red forever.

Peter