I have never seen a password expire on Windows before.
Why would Microsoft do such a thing? How am I ever meant to set up and test anything if Microsoft lays traps like this.
It's possible that the expiry is a function of how I created this
user, (I used net user on the command line) but at the moment I'm
unable to use the "standard" Windows 10 way to create local users
because "Something went wrong" after I indicated that this user does
not have Microsoft account.
Am 28.10.2022 schrieb Sylvia Else <sylvia@email.invalid>:
I have never seen a password expire on Windows before.
It is possible for a long time, especially companies use it.
You can change the settings in gpedit.msc IIRC.
Why would Microsoft do such a thing? How am I ever meant to set up and test >> anything if Microsoft lays traps like this.
Do you have a company-administrated machine connected to AD?
Maybe the admins there set that option.
It's possible that the expiry is a function of how I created this
user, (I used net user on the command line) but at the moment I'm
unable to use the "standard" Windows 10 way to create local users
because "Something went wrong" after I indicated that this user does
not have Microsoft account.
Is it Windows 10 Home?
MS made it difficult to create local users there. Disconnect from the internet and try it in that state.
Does control userpasswords2 work?
But the underlying problem of MS laying traps remains.
Am 28.10.2022 schrieb Sylvia Else <sylvia@email.invalid>:
But the underlying problem of MS laying traps remains.
I don't have a windows system to test, but is a local user with
expiring password the default for a normal Win 10 installation?
At least in older versions it wasn't.
Am 28.10.2022 schrieb Sylvia Else <sylvia@email.invalid>:
But the underlying problem of MS laying traps remains.
I don't have a windows system to test, but is a local user with
expiring password the default for a normal Win 10 installation?
At least in older versions it wasn't.
On 28-Oct-22 10:10 pm, Marco Moock wrote:
Am 28.10.2022 schrieb Sylvia Else <sylvia@email.invalid>:After further testing, it appears to be specific to using the command
But the underlying problem of MS laying traps remains.
I don't have a windows system to test, but is a local user with
expiring password the default for a normal Win 10 installation?
At least in older versions it wasn't.
line NET USER command to create the user. That command creates a user
with an expiring password, and has no option to disable that. The method using PowerShell creates a user with an expiring password by default,
but has an option to disable the expiry.
On Sat, 29 Oct 2022 08:44:02 +1100, Sylvia Else wrote:
On 28-Oct-22 10:10 pm, Marco Moock wrote:
Am 28.10.2022 schrieb Sylvia Else <sylvia@email.invalid>:After further testing, it appears to be specific to using the command
But the underlying problem of MS laying traps remains.
I don't have a windows system to test, but is a local user with
expiring password the default for a normal Win 10 installation?
At least in older versions it wasn't.
line NET USER command to create the user. That command creates a user
with an expiring password, and has no option to disable that. The method
using PowerShell creates a user with an expiring password by default,
but has an option to disable the expiry.
The non Powershell command:
NET ACCOUNTS /MAXPWAGE:UNLIMITED
removes password aging from all users.
"Something went wrong" was fixed by a reboot. How many people remember
when the standard fix was "reinstall Windows"?
Turns out I can use PowerShell to create a local user whose password
does not expire.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 388 |
Nodes: | 16 (3 / 13) |
Uptime: | 06:07:21 |
Calls: | 8,221 |
Calls today: | 19 |
Files: | 13,122 |
Messages: | 5,872,364 |
Posted today: | 1 |