zachd [MSFT] wrote:
Quote:
> That's correct, there's not one right answer.
>
> Many applications over-reboot, some may under-reboot. For example, the
> Windows Media Player 10 install installing to a system where the deskband
> was in use by the shell. You "should" reboot to get the updated deskband
> available in the shell - but if you don't, the player is still functional
> (just not the deskband). Should you reboot? (The answer was that the
> player installer will say you can use WMP now, but it won't work fully until
> reboot.)
>
> If you check the PendingFileRenames queue and the RunOnce, RunOnceEx, and
> etc queues, you can get an appromixate feel for whether or not a reboot was
> really needed.
>
> The only particularly dangerous times as regards reboots are where they put
> in a non-temp-pathed file into the pendingfile queue. If you then installed
> something that reinstalled that marked-deleted file and rebooted, you'd end
> up in a rogue state.
>
> There's a little unsupported command line powertoy, rebootchk.exe, I wrote
> once that has a vague idea about reboots. If you look for that on MS Live
> search, you'll find it (Google evidently didn't notice it). It's dumb, but a
> minor time saver. *shrug*
>
> There's definitely not one perfect answer here, not from your standpoint,
> and not really from any standpoint. =)
>
Thanks for visiting again, I appreciate that "Insiders" get a lot of
annoyance which likely puts them off visiting these groups but when some
real solid info is forthcoming it helps everybody here a lot, in fact
I'd say that lack of such visits actually contributes to
dissatisfaction, but at the same time it is understood that employees
are in a vulnerable position and unable to directly influence corporate
policy. I am sure many frustrations are common to all but the less said
the better
