Booting to calendar screen and requests password after using feedback

caperjack said:

so there is nothing wrong, really, ,it normal to have to login when going from one acct to the other

Yes when going from one acct to another. No, it should not be normal when going from one app to another, especially if the user is not explicitly aware of the changes being made or their consequences.

As I said earlier, the first time this happened to me:

1) I could not understand why the password page had suddenly appeared on the subsequent bootup.
2) I did not realize that the sudden appearance of the password screen was linked to my use of the feedback app the night before.
3) I did not understand that it required my Microsoft account password, which I had only ever used before when logging into my account on the Microsoft website. I have always used a User acct without password for Windows.
4) I tried random numbers and digits but of course it would not let me back into Windows.
5) I asked the Microsoft Community for help and a support engineer replied that I need to boot in safe mode. He did not seem to understand that I could not get back into Windows because I did not understand what password it required. He did not know what I meant by a password. LOL!
6) Due to my total bewilderment I ended up re-installing Windows 10 from a back up that I had made 2 days earlier. This took considerable time, which I only now see had been a total waste of time. I only had to use my Windows account password. But it didn't actually ask me for that explicitly and at that time I did not know that this was the password it required.

In short, Windows apps should be designed to be "user friendly", not "user bewildering".

You well may laugh at my "comedy of errors", but I came across another Windows 10 forum on which many people had also been bewildered by the sudden appearance of the password screen. Some had become so frustrated that they had resorted to re-installing Windows. Many ideas were posted about the reasons for the problem. Some thought it came about due to a bad update, or an update that had not installed properly, or was not finished installing. The irony is that none of them considered the feedback app, which they had all no doubt been using to contact Microsoft about the problem.