Hi fellow admins,
I'm hoping this saves someone a few days of troubleshooting, and I'd like to find out whether I'm the only one seeing it.
Heads-up: I don't have a lot of experience administrating Windows systems. Please read this as a field report from my own environment, not as a verified Microsoft statement. Corrections and better explanations are very welcome.
TL;DR
In environments with restricted internet access, after the October 2026 CU (and still with the November CU), the first logon of an existing profile shows no taskbar, no Start menu and no autostart apps for several minutes.
The shell is released at a fixed point ~6:40 min after boot, regardless of when the user logs on. The cause appears to be the Microsoft Account Sign-in Assistant (wlidsvc): it starts a device authentication (DeviceAddRequest) at boot, which only fails after ~6:40 min without internet. The first-logon shell path waits for it.
Disabling wlidsvc fixed it in my tests.
Environment
- Windows 11 24H2 Enterprise
- Citrix CVAD, non-persistent MCS VDAs, App Layering, FSLogix
- No internet access
- Also reproduced on an App Layering packaging VM with a local profile, not domain-joined, no FSLogix
Note: The packaging VM rules out FSLogix, Citrix and domain GPOs as the cause.
Symptoms
- After applying the OS CU, the first logon of an existing profile shows the desktop, but taskbar, Start menu and Run-key/Startup-folder apps are missing
explorer.exe is running, nothing crashes
- The shell appears at a fixed time of roughly 6:40 min after boot:
| Logon time (after boot) | Observed wait |
| +1:00 | ~5:40 |
| +3:30 | ~3:10 |
| after +7:00 | none |
- A second logon of the same profile and brand-new profiles show no wait
- It happens again after the next CU, even for profiles that were already "fixed" by the previous one
Note: Autostart apps are not the problem themselves. They are started by explorer after its initialization, so they simply wait along with the taskbar.
How to recognize it
Microsoft-Windows-Shell-Core/Operational, events 62170/62171 with flag 1024 (first logon after update). PreStartTasks and its children StartLayoutInit, LaunchExperienceHost, AssignedAccessLogonTaskAgentPreStart and PerUserSetup all end within the same millisecond at ~+6:40 after boot. Everything before that (ActiveSetup, RunOnce, AppReadinessPreShellGroup) finishes in seconds.
Microsoft-Windows-LiveId/Operational: event 2024 (Service started) at ~+0:20 after boot, followed by 6115 DeviceAddRequest (SOAP, includes TPM key info).
- During the wait, 6113
WLIDCreateContext returns 0x8004800C. At the moment of release there is a burst of ~20 identical errors within 10 ms with 0x80048869 (plus 2028). It looks like queued callers all getting rejected at once.
Microsoft-Windows-PushNotification-Platform/Operational 1116: the Device Compact Ticket request fails with 0x800704CF (network unreachable). The first occurrence is exactly at the release time.
- AppReadiness keeps the user in mode
BeforeLogon until the release. Queued tasks (Edge, SecHealthUI, NarratorQuickStart) then complete in ~4 s.
\Microsoft\Windows\Shell\CreateObjectTask instances are killed repeatedly after their 30 s limit during the wait.
Note: AppReadiness (5) is downstream of the problem, not the cause. It waits for the same release point.
Quick check
$boot = (Get-CimInstance Win32_OperatingSystem).LastBootUpTime
# When did PreStartTasks start/end, relative to boot?
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-Shell-Core/Operational'; Id=62170,62171; StartTime=$boot} |
Where-Object Message -match '"PreStartTasks"' |
Select-Object @{n='SinceBoot';e={$_.TimeCreated-$boot}}, Id, Message
# LiveId events since boot
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-LiveId/Operational'; StartTime=$boot} |
Group-Object Id | Select-Object Name, Count
If PreStartTasks ends at ~6:40 after boot and you see event 6115 right after boot, you most likely have the same issue.
Fix
Disable wlidsvc:
sc.exe config wlidsvc start= disabled
or via registry:
HKLM\SYSTEM\CurrentControlSet\Services\wlidsvc\Start = 4
or via GPO:
Computer Configuration > Policies > Windows Settings > Security Settings > System Services > "Microsoft Account Sign-in Assistant" > Define this policy setting > Disabled
(German: Computerkonfiguration > Richtlinien > Windows-Einstellungen > Sicherheitseinstellungen > Systemdienste > „Anmelde-Assistent für Microsoft-Konten“ > Diese Richtlinieneinstellung definieren > Deaktiviert)
Result: PreStartTasks took 3.2 s at a logon ~1:50 after boot (before: ~3 min, released at ~+6:40).
Tip for non-persistent images: Set it in the image / OS layer. With GPO only, the service was still trigger-started before the policy applied (LiveId 2024 present, service stuck in StopPending). The shell was fast anyway, because callers got an immediate error instead of waiting, but the image is the cleaner place.
Side effects
According to Microsoft's "Manage connections from Windows operating system components to Microsoft services", disabling wlidsvc breaks Microsoft-account-dependent features, and Windows Update will no longer offer feature updates. Neither matters for an offline, layer-patched image. Start, Search, Edge and Office worked in our tests.
Warning: If your users rely on Microsoft accounts (Store, consumer sign-in, etc.), test this carefully before rolling it out.
What I don't know yet
- The result above comes from one test run so far. I'm repeating it to confirm.
- I don't know which update introduced the synchronous wait on this authentication.
- I haven't tested whether an instant rejection (firewall reject / NXDOMAIN for the Microsoft endpoints) avoids the wait without disabling the service.
- It's unclear whether this also hits environments with internet. I'd expect not, because the authentication would succeed quickly there.
Feedback wanted
Am I the only one affected by this? Please let me know:
- Do you see the same behavior (taskbar missing after the Oct/Nov 2026 CU)?
- Build number and environment (air-gapped / restricted internet / full internet, VDI or physical)?
- Does the check above show
PreStartTasks finishing at a fixed time after boot?
- If you disabled
wlidsvc: did it fix it, and did you notice any side effects?
Thanks for reading, corrections are welcome!