All throughout windows, it is very common to have to enter and save passwords, and, what's worse, when a password is changed, you have to try to remember everywhere that it was set.

A good example is inside of an Active Directory environment where you have Services that run under a specific user. If you change the user's password, then you have to go to each server and update the password.

I suggest that features like this be re-architected to take advantage of OAuth (or a similar technology) very similar to how Facebook and Twitter let you Authorize Apps.. I should be able to tell a service to "Run As" a user, enter that user's credentials once, and then have an OAuth relationship created between that user and that service. This would have a few important advantages:
1. Saved passwords become a thing of the past.
2. Greater stability for services when implementing best-practices with passwords.
3. Ability to see all "Authorizations" that a user has granted.