[SOLVED] Modifications that affect Login behavior?

LoneCrusader

New Member
Messages
14
Reaction score
1
Working on creating a Windows 10 Pro image with several removals and tweaks. Using the last Oct2025 official ISO as a base.

My removals fall somewhere between the default given Templates; not including every item of any given set but most of the Privacy template items are included.

I've encountered an issue where the default behavior of the system with regard to "Autologin" is changed by the Modifications that have been made.

If I set up an install of Win10 using the official ISOs, I can simply leave the password blank during SETUP and the system will automatically log in to the created account when booted. And, I can subsequently enable the built-in Administrator account, delete the other account, and have the same "autologin" conditions. This is without any modification to any related setting; no configuring Unattended, etc etc.

After creating a custom ISO with the desired changes, this behavior is changed. Now I even have to type the User name to log in every time.
Did some searching; tried the fixes suggested (modify registry setting to show "users must enter" checkbox; changed checkbox setting, etc). These had no effect, and all of these settings appear to be the same as they are in an install created using the official ISO where it works.

I ran a test build using the official ISO and just the "Privacy" template and the resulting ISO seems to retain the default behavior. So I'm certain that this change comes from a deeper level component change. My guess is that it is caused by one of the modifications that uses Group Policy to implement.. disabling Windows Update maybe?

Is there a list of which modifications are implemented using Group Policy; and, is there any way to view these policies directly in the resulting image or prior to its creation?

I have a system set up where I had originally installed Windows 10 from the official ISO and subsequently made desired changes to the live system with other tools, some of which also use Group Policies. But the live system modified with the other tools does not have this login issue.
 
Changed title to hopefully clarify the question...


EDIT:

Found the culprit.

Configure>Settings>Tweaks>Privacy>Display last user name in logon screen

From the description of this it sounds like it is only a cosmetic change; it is not obvious that selecting it would break the default behavior described above, since no interaction is required on the Logon screen when using this method.

Setting the associated Registry entry to "0" corrected this issue on an installed system.
 
Last edited:
Back
Top