Problema Emby Client en Windows 11

[Guderian 2]

10 hours ago, roand7802 said:

Cuando te sale el error, en el visor de eventos no te sale algún warning o error o crítico? Quizá allí aparezca algo más...

 

Hola, aqui lo tienes.

Saludos

err_event.evtx

[Luke 42649]

@sa2000elsewhere in the forum someone found some windows setting that had to be disabled for the installer. maybe you can find it. 

[sa2000 785]

Have not found it so far. 

@GuderianCould you try a test for me with Process Monitor installed and running. I do not need a dmp file this time - just the embyclient.txt log and windows event viewer and zip of the PML file from procmon

Procmon uses a lot of system resources - so we only need to run it for short time just before launching the Emby Windows app and stopping the capture once you get the dialogue box saying: 

Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

So please download Process Monitor

Unzip it

Launch procmon.exe

accept EULA and start with default capture filter

Then launch emby windows client app

When you get the error dialogue box, go back to the procmon session and stop the capture

I have circled in green the icon for stopping / starting capture

 

Once stopped, click File from the menu and then choose "Save .." and select the option to save as Native Procss Monitor formar (PML) and choose a path to save the PML file to

Then please also save the full Windows Event Logs (Application and System) into evtx files - do not filter.

Then zip the PML and the 2 evntx files and upload to the link i am going to send you. Please also include the embyclient.txt file 

Thanks

 

 

[sa2000 785]

Thanks @Guderianfor sending the PML and log and event logs files.

I cannot see any Application Errors in the event log as last time. Do you have more than one windows PC's ? Is it posisble this was from the wrong machine?

The last logged event in the Application event log was at 07:37:59 but the EmbyClient.txt log file shows that it was launched at 07:44:08 and closed at 07:44:16 on 30th June

The last Emby Client application error in the event log was on 4th June for version 2.234.2  - so I am thinking may be you have 2 windows machines and you provided the PML and Event Logs from the wrong machine. Is that possible?

 

 

[Guderian 2]

Hola, el mismo problema lo tengo en 3 equipos, pero lo ultimo que te envie es de la misma maquina.

Ahora me acabo de dar cuenta que no aparecen los errores anteriores en el visor de eventos (desconozco el motivo).

Saludos

[sa2000 785]

1 minute ago, Guderian said:

Ahora me acabo de dar cuenta que no aparecen los errores anteriores en el visor de eventos (desconozco el motivo).

And presumably not producing dmp files anymore - 

The PML file you gave me does not show Emby Client app starting on that computer or even attempted to be started. The PML had a gap between 07:44:00 and 07:44:19 and the EmbyClient.txt file you provided shows it was running between 07:44:08 and 07:44:16

Also the Event Viewer Applicationn log had last event at 07:37:59

So it does not add up. 

If all provided diagnostics were from the same machine, one possibility is that Procmon had a filter and excluded the launch of the Emby Client app and that the Emby Client app did not crash. There is an option in Procmon in the Filter menu to reset the filter. Alternatively when you click filter you can just delete everything in the filter display and we will get all events

And please this time include screenshot of what happens when you launch the Emby Client and give the time of that - and since it is different now, have a look also at the "%LocalAppData%\CrashDumps" folder

So if it is not crashing anymore, what is the problem now when using 2.310.2 version?

And lets concentrate on only ONE of your 3 windows machines having the issue. Unless there was a filter in procmon, the evidence suggests that the procmon capture was from the wrong PC