S
Sebazzz
I have a Microsoft Surface Pro 4 tablet with Windows 10, 1709, version 16299.248 installed. On my tablet we have multiple profiles, but something in my profile suddenly has gone corrupt and it causes the following symptoms:
DCOM errors
First I found these errors:
In de machtigingsinstellingen toepassingsspecifiek wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
en APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19)
And:
In de machtigingsinstellingen toepassingsspecifiek wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
en APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) met het adres LocalHost (via LRPC) die wordt uitgevoerd in de toepassingscontainer Niet beschikbaar SID (Niet beschikbaar).
And
In de machtigingsinstellingen standaard voor deze computer wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
en APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) met het adres LocalHost (via LRPC) die wordt uitgevoerd in de toepassingscontainer Niet beschikbaar SID (Niet beschikbaar).
I fixed those by setting the correct settings, first in the registry, then in component services for Runtime Broker, ShellServiceHost, ImmersiveShell respectively. To be exact, that is full activation permissions for both SYSTEM and LOCAL SERVICE.
This didn't resolve the issue however.
Black screen on login & App Readiness service
If I disable the App Readiness service or kill it on logon, the black-screen-on-login issue does not happen. Otherwise, the high CPU usage of AppXService is still a fact.
That solves the login issue, but isn't a nice solution either.
Windows Event Log
The Microsoft-Windows-TWinUI/Operational logs show entries like this:
https://gist.github.com/Sebazzz/a6b91003d145a45d7b1b94e70a0c013a
Also the manual app restore tricks using "Get-AppXPackage Microsoft.MicrosoftEdge | % { Add-AppXPackage ... }" do not work because the shell hangs on "Initialized". This does not appear to time out but not appear to have any progress either. -> edit: This is not entirely true, in AppReadiness event log this appears after a while (37 minutes apparently):
Microsoft.MicrosoftEdge_8wekyb3d8bbwe installeren is mislukt voor *** Email address is removed for privacy ***. Fout: De installatie is mislukt. Neem contact op met de softwareleverancier. (2256.720125 seconden)
Does anyone know a solution to these issues? My guess is that AppXSrv is going in some kind of endless loop, not being able to handle anything it is supposed to do (something with deployments or app installation?)
I'm looking towards a solution to repairing my profile. I am a software developer and have a lot of settings I would not like to repeat in a new user profile. And throwing that baby out with the bathwater is almost never a solution, since this issue might appear again in any situation.
Continue reading...
- Black screen on login; Ctrl+Alt+Delete responds and allows opening task manager. Explorer is present in the processes list, but is obviously waiting for something. High CPU usage from AppXSvc / wsappx can be noted. After waiting several minutes, eventually the desktop and Explorer appears.
- Some built-in apps (like Microsoft Edge, Photos, Windows Security Center) do not start. Nothing happens.
- Installs in Microsoft Store appear to hang on 80-90%
- Above issues do not appear to occur on different user profiles on the same tablet.
DCOM errors
First I found these errors:
In de machtigingsinstellingen toepassingsspecifiek wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
en APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19)
And:
In de machtigingsinstellingen toepassingsspecifiek wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
en APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) met het adres LocalHost (via LRPC) die wordt uitgevoerd in de toepassingscontainer Niet beschikbaar SID (Niet beschikbaar).
And
In de machtigingsinstellingen standaard voor deze computer wordt de machtiging Activeren niet verleend aan Lokaal voor de COM-servertoepassing met CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
en APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) met het adres LocalHost (via LRPC) die wordt uitgevoerd in de toepassingscontainer Niet beschikbaar SID (Niet beschikbaar).
I fixed those by setting the correct settings, first in the registry, then in component services for Runtime Broker, ShellServiceHost, ImmersiveShell respectively. To be exact, that is full activation permissions for both SYSTEM and LOCAL SERVICE.
This didn't resolve the issue however.
Black screen on login & App Readiness service
If I disable the App Readiness service or kill it on logon, the black-screen-on-login issue does not happen. Otherwise, the high CPU usage of AppXService is still a fact.
That solves the login issue, but isn't a nice solution either.
Windows Event Log
The Microsoft-Windows-TWinUI/Operational logs show entries like this:
https://gist.github.com/Sebazzz/a6b91003d145a45d7b1b94e70a0c013a
Also the manual app restore tricks using "Get-AppXPackage Microsoft.MicrosoftEdge | % { Add-AppXPackage ... }" do not work because the shell hangs on "Initialized". This does not appear to time out but not appear to have any progress either. -> edit: This is not entirely true, in AppReadiness event log this appears after a while (37 minutes apparently):
Microsoft.MicrosoftEdge_8wekyb3d8bbwe installeren is mislukt voor *** Email address is removed for privacy ***. Fout: De installatie is mislukt. Neem contact op met de softwareleverancier. (2256.720125 seconden)
Does anyone know a solution to these issues? My guess is that AppXSrv is going in some kind of endless loop, not being able to handle anything it is supposed to do (something with deployments or app installation?)
I'm looking towards a solution to repairing my profile. I am a software developer and have a lot of settings I would not like to repeat in a new user profile. And throwing that baby out with the bathwater is almost never a solution, since this issue might appear again in any situation.
Continue reading...