Quantcast
Channel: Windows – Born's Tech and Windows World
Viewing all articles
Browse latest Browse all 4440

Windows 10 V1709: Fix for ‘sign-in twice’ bug

$
0
0

[German]Some users of Windows 10 Fall Creators Update (version 1709) are reporting login issues. They have to log-in twice to access the user desktop. But there’s a fix for that.

What the problem?

Users who have upgraded their system to Windows 10 Fall Creators Update (version 1709) may run into a problem. The log-in to the user account must be done twice by PIN or password.

Windows 10 Anmeldung

After entering the first login information, the login page shown above will re-appear and the user has to enter the PIN or password a second time to reach the desktop. A user at reddit.com wrote.

I use a PIN number to log on to my PC and since the Fall Creators Update, I need to enter the number twice. After the first PIN entry, I’m back at the lock/login screen. Any ideas?

Also some posts at Microsoft Answers forum are mentions this behavior. According to this MS Answers forum thread, this is a known issued in Windows 10 Fall Creators Update. Some people proposing an autologon. However, this is not the best solution, if somebody want to secure the user accounts by password or PIN.

A fix for the logon issue

The problem curiously does not occur for every user, but there is a workaround that prevents double logon..

1. Open the Start menu and select the Settings app icon.

2. On the Settings app start page, click to Accounts to go to the Accounts page.

3. In the left-hand column of the next page, select Sign-in options.

4. Turn off “Use my sign in info to automatically finish setting up my device after an update or restart” within the Privacy setting.

Repeat these steps under each user account. Afterward the user logon should work as usual by entering a password or a PIN only once.

I interpret the workaround in such a way that something went wrong with the device setup or an update installation for affected user accounts. Therefore, Windows 10 V1709 requires the second logon process. I assume that Microsoft will fix this bug with an update at some point.


Viewing all articles
Browse latest Browse all 4440

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>