Hello Roger,
The issue you’re seeing is tied to the AppX Deployment Service (AppXSVC) instability in recent Windows Server 2025 builds. When AppXSVC misbehaves, it can cause shell components like the taskbar (explorer.exe shell UI) to fail to render. Disabling AppXSVC in the registry is not recommended long term, since it breaks UWP shell dependencies. The proper way to restore the taskbar is to re-register the ShellExperienceHost and StartMenuExperienceHost packages. Run the following in an elevated PowerShell session:
powrshell
Get-AppxPackage -allusers Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"}
Get-AppxPackage -allusers Microsoft.Windows.StartMenuExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"}
After that, restart explorer.exe or reboot the VM. If the taskbar still does not appear, check that ShellExperienceHost.exe is running under C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\. If it fails immediately, the issue is likely introduced by cumulative updates KB5074204 or KB5091470, which have known regressions on Server 2025 affecting the shell. In that case, the only reliable remediation is to uninstall the problematic update via wusa /uninstall /kb:5091470 and hold patching until Microsoft releases a fixed cumulative build. If rollback is not possible due to Azure image policy, you’ll need to wait for the next servicing release, as this is a confirmed Microsoft-side regression.
If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Harry.