login problem. i get a windows security request every time

Hello flemming madsen, welcome to Microsoft Q&A forum.

The netplwiz fix (disabling auto sign-in) mentioned earlier is for Windows login, not browser passwords. The repeated Windows Security prompts when editing saved passwords are likely due to cached credentials in Edge/browser or Windows Credential Manager.

1. Clear Edge/browser saved passwords:
   • Open Edge > Settings > Passwords
   • Find the old password entry and click Delete
   • Or go to Settings > Privacy > Clear browsing data > Passwords > Clear now
2. Clear Windows Credential Manager:
   • Open Control Panel > Credential Manager
   • Under Web Credentials or Windows Credentials, find the old entry
   • Click Remove
3. If prompts persist:
   • Open Command Prompt as Admin and run: cmdkey /list cmdkey /delete:TargetName (Replace TargetName with the credential name from the list)

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

To remove the Windows security request that appears every time you try to edit your saved passwords, you can follow these steps:

1. Clear Cached Credentials:
   • Open Control Panel.
   • Go to Credential Manager > Windows Credentials.
   • Look for any entries related to the account in question and remove them.
   • Restart your computer and check if the prompt still appears.
2. Disable Automatic Sign-in:
   • Press Windows + R, type netplwiz, and press Enter.
   • In the User Accounts window, select your account and uncheck the box labeled "Users must enter a username and password to use this computer."
   • Click Apply, then enter your current password when prompted, and click OK.
   • Restart your device to see if the issue is resolved.

If the problem persists, you may want to check with your IT department or look into any domain or policy-related restrictions that might be causing the issue.