Log In PW

There are several people, whom use this Win 10 PC. Somehow a change
was made, so that a password is now required to to a cold boot or a
log on. How can I stop that un-needed step (PC in a private
residence).

wrote:
There are several people, whom use this Win 10 PC. Somehow a change
was made, so that a password is now required to to a cold boot or a
log on. How can I stop that un-needed step (PC in a private
residence).

I can describe the lowest level of security. If your
situation is different than this, you're going to need
to provide a lot more detail.

*******

netplwiz

That gives you access to selecting an account for
autologin. You must know the password of the account,
so that the autologin feature can enter the password
for you. This handles login on a cold boot.

The other thing, is the password when the machine is sleeping.
Normally, it would be something like this.

"Here are steps to disable the password after waking from sleep.

1. Click Start.
2. Click Control Panel.
3. Click Power Options.
4. Click on "Require Password on Wakeup" on the left pane.
5. Select the option "Don't require a password."
"

But for Windows 10, you can see the sleep thing is going
to be more of a PITA to deal with. They suggest buggering
with the LockApp [ Microsoft.LockApp_cw5n1h2txyewy folder ]
and making it so the system cannot find the folder, by changing
the folder name on it.

https://www.cnet.com/how-to/how-to-d...0-lock-screen/

I only use netplwiz, on things like the Win10 Insider,
and that works OK. I haven't tried to defeat the sleep/hibernate one.

Paul

Paul wrote:
wrote:
There are several people, whom use this Win 10 PC. Somehow a change
was made, so that a password is now required to to a cold boot or a
log on. How can I stop that un-needed step (PC in a private
residence).

I can describe the lowest level of security. If your
situation is different than this, you're going to need
to provide a lot more detail.

*******

netplwiz

That gives you access to selecting an account for
autologin. You must know the password of the account,
so that the autologin feature can enter the password
for you. This handles login on a cold boot.

The other thing, is the password when the machine is sleeping.
Normally, it would be something like this.

"Here are steps to disable the password after waking from sleep.

1. Click Start.
2. Click Control Panel.
3. Click Power Options.
4. Click on "Require Password on Wakeup" on the left pane.
5. Select the option "Don't require a password."
"

But for Windows 10, you can see the sleep thing is going
to be more of a PITA to deal with. They suggest buggering
with the LockApp [ Microsoft.LockApp_cw5n1h2txyewy folder ]
and making it so the system cannot find the folder, by changing
the folder name on it.

https://www.cnet.com/how-to/how-to-d...0-lock-screen/

I only use netplwiz, on things like the Win10 Insider,
and that works OK. I haven't tried to defeat the sleep/hibernate one.

Paul

Well, I tried renaming the LockApp, in the hopes that it
controlled the password prompt. I see a blue flash, but then
the prompt still shows up.

So that doesn't seem to be it.

And I'm not finding any other recent references. I guess I
just don't have the right keyword to find a solution.

I tried using ProcMon, but couldn't see anything "interesting"
in the trace when testing with WindowsKey-L.

Paul

Paul writes:

The Win10 in the VM (not activated), didn't have
an entry in Accounts, for disabling password entry
coming back from sleep.

In GPEdit (... Power Management:sleep Setting) there is

Require a password when computer wakes (plugged in)
Require a password when computer wakes (on battery)

which might correspond to the Accounts dialog that is
now missing. There are also examples here of
powercfg commands that can do the same thing.

https://www.windowscentral.com/how-p...resuming-sleep

What makes this moot, is *nothing* seems to correspond
to the Windows-L key combo. I can lock the screen
with that, and it always asks for a password. That's
not sleep. That would be the machine running in S0
or whatever, with the screen locked.

Summary:

There is the Lock Screen (slide show, entertain value),
and there is the Sign-in screen. I think you want the
Sign-in policy altered, so destroying the LockApp is
not needed. I don't know why the majority of my first
search attempts, were only digging up references to
abusing the Lock Screen. Who cares about the Lock Screen ?
I don't.

For Sign-In:

1) netplwiz can do autologin for you, at boot
2) the "when computer wakes" thing, handles sleep or
hibernate - and one of the examples in the WindowsCentral
article might handle that.
3) But so far, I cannot find a way to dodge Windows-L
and locking the screen on purpose while the computer
is still running.

I suppose removing the password might work, and
there are ways to do that. But there would not be
much point, if the first ******* that comes along,
sets another password. They you'll be seeing the
sign-in box again.

Paul

On Tue, 24 Oct 2017 03:58:41 -0400, Paul
wrote:

Paul writes:

The Win10 in the VM (not activated), didn't have
an entry in Accounts, for disabling password entry
coming back from sleep.

In GPEdit (... Power Management:sleep Setting) there is

Require a password when computer wakes (plugged in)
Require a password when computer wakes (on battery)

which might correspond to the Accounts dialog that is
now missing. There are also examples here of
powercfg commands that can do the same thing.

https://www.windowscentral.com/how-p...resuming-sleep

What makes this moot, is *nothing* seems to correspond
to the Windows-L key combo. I can lock the screen
with that, and it always asks for a password. That's
not sleep. That would be the machine running in S0
or whatever, with the screen locked.

Summary:

There is the Lock Screen (slide show, entertain value),
and there is the Sign-in screen. I think you want the
Sign-in policy altered, so destroying the LockApp is
not needed. I don't know why the majority of my first
search attempts, were only digging up references to
abusing the Lock Screen. Who cares about the Lock Screen ?
I don't.

For Sign-In:

1) netplwiz can do autologin for you, at boot
2) the "when computer wakes" thing, handles sleep or
hibernate - and one of the examples in the WindowsCentral
article might handle that.
3) But so far, I cannot find a way to dodge Windows-L
and locking the screen on purpose while the computer
is still running.

I suppose removing the password might work, and
there are ways to do that. But there would not be
much point, if the first ******* that comes along,
sets another password. They you'll be seeing the
sign-in box again.

Paul


Thanks - to all for their assistance. My annoying problem solved!!