Rebooting, still logged in as X after logging in as Y! (Hibernation=Off)

How can a password-protected account survive a reboot with
hibernation disabled? ... and can i change this confusing behavior?

If i forget to log out [sign out] and then shut down or reboot,
then the people using the machines normally get into trouble next
time they are shutting down/rebooting their machines from their
accounts.
"Someone else is using this PC. If you shut down now, they could
lose unsaved work. Button:{Shut down anyway}"


Background:
Win10 machines with originally one single account
(AccountType=Administrator), either with Win10 force-installed at
store, or [inappropriately[*1]] force-updated from Win07 via
"Windows Update" over internet. Me asked to help these
acquaintances. They not wanting to have to "log in" when starting
their machines. Me adding a second password-protected account and
making that AccountType=Administrator; then leaving their
original accounts without a password but changing to
AccountType=Standard, in hope it'll make the users slightly less
vulnerable online.
Now, i can use and /administer/ their machine using the
"Administrator" account and in that account changing the ms
duhfaults settings so the OS becomes more useful [for me]. The
above described problem now surface when they use their machines
after i've left, if i forgot to /sign out/ before shutting down
the machine or rebooting to log into their account to see that it
works ok after any changes i might have made.

I've discovered that in the "Task Manager":Users: there are both
accounts listed, /my/ account status=Disconnected (but still
using CPU-resources!)

Lurking here i thought i was onto something and disabled
Hibernation, but that didn't change anything.

Just now, before posting, it hit me that being used to WinXP this
sounds something akin to WinXPs "Fast User Switching" which i
always disable there in the needed post-install
setting-corrections. But i don't remember that "Fast User
Switching" survived rebooting when i encountered it back when.

So, how can a password-protected account survive a reboot with
hibernation disabled?


[*1] [inappropriately] as in machine with Win10 being slow as
molasses, [CPU/GHz=1; RAM/GB=2; Storage=HDD]; in practice =
forcing user to buy new laptop.


--
"For i'm one too many mornings
And a thousand miles behind"

Etal wrote:

Someone else is using this PC. If you shut down now, they could
lose unsaved work.

Sounds like at least one of the users is using "switch user" from the
shutdown or C-A-D menu?

Andy Burns wrote:

Etal wrote:

Someone else is using this PC. If you shut down now, they could
lose unsaved work.

Sounds like at least one of the users is using "switch user" from the
shutdown or C-A-D menu?


On the Start Menu, the bottom menu-choice is the
"On-Off"-Power-icon, where i use "Shut down" or "Restart".

I've never used C-A-D under Win10 before. Ah, there is a "switch
user" option. On the Start Menu, the top menu-choice is the
generic-account-picture-button, with a sub-menu listing the other
(one) account(s). No, i don't use either of these. I use the
sign-out option when needed as described in the next paragraph.

If the machine is already running when i intend to log in and
use the admin-type account, as the standard-type account are
password-less, i have to sign out the standard user or else the
same standard user will be automatically logged on.
Then, being me, on the login screen, i choose the power-button
and "restart" the machine before logging in as an admin-type.

When i'm done, via the Start Menu; when i forget i "Shut down"
the machine and leave; when i remember i use "Restart" and log in
to the Standard-type account to check that all is normal and then
"Shut down" the machine.

It was after new year when i configured the
now_slow_former_Win07 machine i first was startled by this
"Someone else is using ..." notice. During the configuration, i
got a defunct Windows Updating to work again which included the
latest of these mega-upgrades (10.1709). At first i wondered if
this behavior was a side-effect of the machine had been upgraded
from Win07 as i hadn't seen this popup-notice on the store-bought
as Win10 machine i had configured similarly a year earlier.
But, on my next visit to the person with that Win10 laptop, that
machine now also show this /AnotherUserLoggedOn/ -notice. That
machine had AutoUpdated itself with the latest Win10-upgrade
(10.1709) since last i had visited. So either this is new
behavior with that 10.1709 version (or another update from around
that time) or i somehow misremember that there wasn't two
accounts showing up under the Task Manager's Users-tab the year
prior.

My intention is to only use each human-usable account
sequentially on its own, as we using these machines have no need
for anything else.

My thinking is that when i use "Shut down" or "Restart", that
that will include an automatic orderly logging out the current
user as an initial step.


--
"I hot-footed it . . . bare-naked . . .
Out the window!"

Etal wrote:
Andy Burns wrote:

Etal wrote:

Someone else is using this PC. If you shut down now, they could
lose unsaved work.

Sounds like at least one of the users is using "switch user" from the
shutdown or C-A-D menu?


On the Start Menu, the bottom menu-choice is the "On-Off"-Power-icon,
where i use "Shut down" or "Restart".

I've never used C-A-D under Win10 before. Ah, there is a "switch
user" option. On the Start Menu, the top menu-choice is the
generic-account-picture-button, with a sub-menu listing the other (one)
account(s). No, i don't use either of these. I use the sign-out option
when needed as described in the next paragraph.

If the machine is already running when i intend to log in and use
the admin-type account, as the standard-type account are password-less,
i have to sign out the standard user or else the same standard user will
be automatically logged on.
Then, being me, on the login screen, i choose the power-button and
"restart" the machine before logging in as an admin-type.

When i'm done, via the Start Menu; when i forget i "Shut down" the
machine and leave; when i remember i use "Restart" and log in to the
Standard-type account to check that all is normal and then "Shut down"
the machine.

It was after new year when i configured the now_slow_former_Win07
machine i first was startled by this "Someone else is using ..." notice.
During the configuration, i got a defunct Windows Updating to work again
which included the latest of these mega-upgrades (10.1709). At first i
wondered if this behavior was a side-effect of the machine had been
upgraded from Win07 as i hadn't seen this popup-notice on the
store-bought as Win10 machine i had configured similarly a year earlier.
But, on my next visit to the person with that Win10 laptop, that
machine now also show this /AnotherUserLoggedOn/ -notice. That machine
had AutoUpdated itself with the latest Win10-upgrade (10.1709) since
last i had visited. So either this is new behavior with that 10.1709
version (or another update from around that time) or i somehow
misremember that there wasn't two accounts showing up under the Task
Manager's Users-tab the year prior.

My intention is to only use each human-usable account sequentially
on its own, as we using these machines have no need for anything else.

My thinking is that when i use "Shut down" or "Restart", that that
will include an automatic orderly logging out the current user as an
initial step.



https://answers.microsoft.com/en-us/...7-8bc1debaf24f

"It appears that the update from Windows 10 to version 1709,
has changed some settings.

One of the changed settings caused the problem described above

It was caused by a setting under,

Settings - Accounts - Sign-in options

"Use my sign-in info to automatically finish setting
up my device after an update or restart"

was "on" in an account, causing this account to remain logged on.

Set to "off" position, solved the issue.
"

Note that the setting must be changed *per user* account,
and is not a global setting for the machine.

Paul

Paul wrote:

Etal wrote:

... So either this is new behavior with that 10.1709
version (or another update from around that time) or i somehow
misremember that there wasn't two accounts showing up under the Task
Manager's Users-tab the year prior.

My intention is to only use each human-usable account sequentially
on its own, as we using these machines have no need for anything else.

My thinking is that when i use "Shut down" or "Restart", that that
will include an automatic orderly logging out the current user as an
initial step.



https://answers.microsoft.com/en-us/...7-8bc1debaf24f

"It appears that the update from Windows 10 to version 1709,
has changed some settings.

One of the changed settings caused the problem described above

It was caused by a setting under,

Settings - Accounts - Sign-in options

"Use my sign-in info to automatically finish setting
up my device after an update or restart"

was "on" in an account, causing this account to remain logged on.

Set to "off" position, solved the issue.
"

Note that the setting must be changed *per user* account,
and is not a global setting for the machine.


Thanks Paul.

Ha!, so there was a change in this behavior introduced with 10.1709.

On the Win10 i have access to today that setting was "On" in the
Admin-type account, and after turning it "Off" when rebooting and
logging into the standard-type account only the standard user
exists in the Task Manager's Users tab and there is no
ominous-worded dialog-box when shutting down or rebooting from
that account. Great, so the machine now works as we want it in
this respect.

I haven't seen failed Windows Updates listed for a while so i
wonder if having that setting set to "On" has helped in avoiding
that. I'll keep my eyes open if they start failing again. If its
default is to be "Off", i wonder if i didn't find and enable that
setting after a visit when i noticed a number of failed Windows
Updates listed.

( Hmm, So ms doesn't trust the TrustedInstaller account to
install "Windows Updates" updates. )


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Etal wrote:

If it is not running it boots into the standard-user, and i have
to sign out from there.


If the machine is already running when i intend to log in and
use the admin-type account, as the standard-type account are
password-less, i have to sign out the standard user or else the
same standard user will be automatically logged on.
Then, being me, on the login screen, i choose the power-button
and "restart" the machine before logging in as an admin-type.

No i don't .. when sometimes doing that, it just ushers me
directly back to the standard-user's desktop. Instead, i have to
remember to briefly login to the admin-user's account before
rebooting for the computer to stop at the login screen so i can
choose whom i want to log in as.


--

Etal wrote:


( Hmm, So ms doesn't trust the TrustedInstaller account to install
"Windows Updates" updates. )

TrustedInstaller isn't a full account. It doesn't have
a home directory. There's no login password (you should
not see it in a login window as an option).

That implies that perhaps some other account is used
first, and the install step is done with a
"TrustedInstaller token".

It's really more trouble than it's worth :-)

https://borncity.com/win/2017/02/22/...stedinstaller/

"ProcessHacker launches the TrustedInstaller services
and hands over the process, that needed to be run with
TrustedInstaller privileges."

That suggests some service has the necessary token.

Paul