On various clean Windows 10 or 11 builds, all of which are domain-connected devices, if I log in from a cold boot using a domain account while having no network connection to the domain, I get lengthy delays before I am logged into the device.
When the device is on the corporate network, it logs in normally.
When off the network, the login delay used to be around a minute. Now, it's closer to 5 minutes.
I get that there may need to be a timeout period. This timeout period appears to be far too long or attempted multiple times or both.
How can I get this timeout down to a reasonable time? Just a few seconds should be plenty to discern if domain services are contactable.
Answering questions in comments:
- Are there mapped network drives? Yes, but I do not think they get mapped until after the desktop appears, which is after the timeout completes.
- Are any file or folders processed at logon? While I don't think so, how may I check that?
- Is the system policy to wait for the network to be ready before processing settings? This group policy is set to Disabled: Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon.
- Do you have roaming profiles and are they large? In System Properties > Advanced > User Profiles > Settings, I show that all profiles are local.
- what are your DNS servers set to when you're working remotely It just uses what DHCP provides, which are my ISP's servers.
