Win10 Mail App Put PW on PC

elt · 22 Sep 2016

Woke up this morning to find the PC was updating... a process that took 45+ minutes. I assume this is what's called the Anniversary update. Since over the past few days Windows 2012 mail finally stopped working I finally signed up with the Win10 mail app. Entering the PW it said something about the PC but I didn't quite understand it. That was dumb because there's now a PW on the PC itself and I don't want one.

In account settings I told it to never ask me for a PW when I come back from being away... but that setting does nothing.

Any ideas how I can get rid of that PW on the PC?

Thanks

(if the suggestion is to jump through the on-line MS security hoops... AHHHHH!!! I tried getting on line to see if I could make any changes but MS's security check system seems to be broken. 15 years ago I had MSN internet with a number of accounts. I picked the C user account to be the backup should something happen to the E user. The C email account shows up to send a security code to... but after 4 tries... no mail is sent there because it no longer seems to be associated with the E user which once was the admin for all the MSN users. I can't reset the security info because I only have one phone... and it says that number is already in the system... and on and on it goes... but my main question is how do I remove the PW from the PC itself?)

dalchina · 23 Sep 2016

For anyone puzzled by the above it seems PW = password.

In account settings I told it to never ask me for a PW when I come back from being away... but that setting does nothing.

- that setting works for me, and applies to resuming from sleep. Could you try that explicitly?

If you are logging in as a local user (which I assume you are) please see
Password of User Account - Remove in Windows 10 - Windows 10 Forums

from the Tutorial section which is full of clear guides, and which it's often worth searching and worth being aware of.

elt · 23 Sep 2016

dalchina said:

- that setting works for me, and applies to resuming from sleep. Could you try that explicitly?

Thanks for the speedy reply dalchina. Yup... that's how I found out I suddenly needed a password after 15 years of not having one. Image my surprise. Luckily I guessed which one of the 100+ I must have. I'll give your suggestion a try. Win10 Anniversary threw me for a loop. I had been using Classic Shell (a win7 substitute for the lost start menu on Win8) and now even Control Panel and the search/run box was gone. >>>>>>>UPDATE: I did get rid of the user PW by signing in with the "local account". I don't even know when MS added the network password as an option. I only found out by accident when I started using the Win10 mail app. Thanks again!!

dalchina · 23 Sep 2016

Strange- I was using C Shell before the AU, and still am- no issues. Have you tried reinstalling it?

elt · 23 Sep 2016

dalchina said:

Strange- I was using C Shell before the AU, and still am- no issues. Have you tried reinstalling it?

I did install the newest version and it doesn't work. The version that Anniversary said was incompatible was over a year old... when I first got Win8 after using Vista... and spent the first week swearing at it. UPDATE: I feel my PC is gaslighting me. When I got rid of my password, the PC logged me out and when I went back in... Classic Shell was back... and with it my option to hibernate which was missing from the Win10 Anniversary powers options.

dalchina · 24 Sep 2016

I must admit to being somewhat confused about what you're experiencing.

I'm wondering if you're actually logging in as a different user?

I'm using the latest Classic Shell -4.3 - no problems.

elt · 27 Sep 2016

dalchina said:

I must admit to being somewhat confused about what you're experiencing.

I'm wondering if you're actually logging in as a different user?

I'm using the latest Classic Shell -4.3 - no problems.

As I noted above, I got classic shell running... but it only happened after I was able to get rid of the PW on my account. At that point, Windows logged me out, and when I went back to desktop (there's only one account on the machine), classic shell was running. Don't ask me why. It may have needed for me to log out of my account to become active.