EnableFastFirstSignIn and Windows 11 24H2 not working

Markus Wehr 1 Reputation point
2024-11-21T22:27:27.76+00:00

Hi,

can someone confirm that EnableFastFirstSignIn does not work under 24H2?

It does not create the candidate accounts defaultuser000001 etc. The same policy on a 23H2 device works as expected.

Additionally I notice a WsiAccount after Autopilot Self-Deploying although I did not configure Web sign-in.

The SharedPC CSP seems to works as expected so far.

best regards

Markus

Windows Autopilot
Windows Autopilot
A collection of Microsoft technologies used to set up and pre-configure new devices and to reset, repurpose, and recover devices.
477 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
10,169 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
5,314 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. S.Sengupta 20,641 Reputation points MVP
    2024-11-22T00:41:10.32+00:00

    In previous versions (e.g., 23H2), EnableFastFirstSignIn would create candidate accounts like defaultuser000001. Is it missing now?

    The appearance of a WsiAccount could indicate that there are underlying changes in how Windows manages accounts during Autopilot scenarios in 24H2, even if Web Sign-In is not explicitly configured.

    Before proceeding the following create a System Restore Point.

    In Start Search type Regedit and hit the Enter key.

    Now navigate to:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Logonui

    Right-click in the right pane, select "New" > "DWORD (32-bit) Value" and name it "EnableFastFirstSignIn"

    Double-click "EnableFastFirstSignIn" and set the "Value data" to "1".

    Reboot.

    0 comments No comments

  2. ZhoumingDuan-MSFT 14,465 Reputation points Microsoft Vendor
    2024-11-22T05:42:32.77+00:00

    @Markus Wehr, Thanks for posting in Q&A.

    For your issue, please check the registry to see whether the policy has been applied to the device. Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Logonui

    Also, please check the information mentioned by @S.Sengupta and see if the issue can be fixed.

    If there is any update, feel free to contact us.

    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.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.