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 42678]

@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

[roand7802 1]

Hola, tu estás en el programa insider en esos equipos?

 

También puedes intentar hacer esto para descartar permisos:
desde el explorador ve a la ruta  de Emby C:\Program Files\WindowsApps\EmbyMedia.EmbyTheater... y busca la aplicación Emby.Client.WinUI y ejecútala desde allí pero como administrador

 

[Guderian 2]

2 hours ago, roand7802 said:

Hola, tu estás en el programa insider en esos equipos?

 

También puedes intentar hacer esto para descartar permisos:
desde el explorador ve a la ruta  de Emby C:\Program Files\WindowsApps\EmbyMedia.EmbyTheater... y busca la aplicación Emby.Client.WinUI y ejecútala desde allí pero como administrador

 

Hola, mismo error. No estoy en insider.

Tampoco aparecen errores en el visor de eventos ni en %LocalAppData%\CrashDumps

EmbyClient.txt

[sa2000 785]

So whilst you are still getting the same error message as before: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.", you are no longer getting an "Application Error" in the windows Application Event Log and no Application crash 

Strange that this change behavior is happening without a change to the Emby Windows application version - still version 2.310.2.0

I noticed from the procmon PML file that you run wireguard - could it be blocking the Emby Windows attempt to access whatever it was trying to access?

I suggest we revisit getting procmon PML file again and making sure the filter is reset and it is run on the same PC that Emby Windows is being launched on and note down the time the pop-up error message appears - to the second - so noting down hh:mm:ss time and then I can look at see what was happening at that time in the embyclient.txt log and procmon PML file.

In the last log we have 

at 20:30:17 / 20:30:18

2026-07-04 20:30:17.296 Info MainWindow: AppWindow_Visible: Invoke LoadWebView
2026-07-04 20:30:17.307 Info MainWindow: LoadWebView: Before EnsureCoreWebView2Async
2026-07-04 20:30:17.311 Info MainWindow: WebView2X: Start Init
2026-07-04 20:30:17.461 Info MainWindow: WebView2X: Fixed runtime path: C:\Program Files\WindowsApps\EmbyMedia.EmbyTheater_2.310.2.0_x64__svmepx4c03f7m\WebView2\x64
2026-07-04 20:30:18.025 Info MainWindow: WebView2X: environment.UserDataFolder: C:\Users\administrador\AppData\Local\Packages\EmbyMedia.EmbyTheater_svmepx4c03f7m\LocalState
2026-07-04 20:30:18.033 Info MainWindow: WebView2X: Window Handle: 132616
2026-07-04 20:30:18.129 Info Application: ApplicationStateMonitorWinUI.Window_Activated - State: Deactivated

and then at 20:30:25

2026-07-04 20:30:25.480 Info MainWindow: AnimationWindow_ShowLogo invoked
2026-07-04 20:30:25.541 Info MainWindow: AnimationWindow_AnimationHidden invoked
2026-07-04 20:30:25.683 Info Application: ApplicationStateMonitorWinUI.Window_Activated - State: CodeActivated

and then at 20:30:27

2026-07-04 20:30:27.816 Info MainWindow: ==== APP CLOSING ====

it would be good to know if the error "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item" was 20:30:25 and if you acknowledged the prompt at 20:30:27 and with a PML procmon capure for the period, we should see what was happening 

 

Edited 8 hours ago by sa2000

[Guderian 2]

Hola, adjunto varias ejecuciones de la aplicacion, junto con el PML, a ver si hay suerte. Verifica que esta vez aparece el proceso 'Emby*', porque en el procmon, es bastante confuso ver si el proceso en cuestion aparece o no.

He probado a desactivar WireGuard, y sigue fallando. Este solo se usa cuando salgo (no es el caso).

Saludos y gracias.

emby.7z

[sa2000 785]

14 minutes ago, Guderian said:

ola, adjunto varias ejecuciones de la aplicacion, junto con el PML, a ver si hay suerte. Verifica que esta vez aparece el proceso 'Emby*', porque en el procmon, es bastante confuso ver si el proceso en cuestion aparece o no.

He probado a desactivar WireGuard, y sigue fallando. Este solo se usa cuando salgo (no es el caso).

Thank you

Do you have 2 computers named: PORTATIL and  JPCEFM ?

[Guderian 2]

1 hour ago, sa2000 said:

Thank you

Do you have 2 computers named: PORTATIL and  JPCEFM ?

Hola, no.

Portatil es un equipo.

Jpcefm es el dominio al que pertenece (ad).

Saludos

[sa2000 785]

57 minutes ago, Guderian said:

Hola, no.

Portatil es un equipo.

Jpcefm es el dominio al que pertenece (ad).

Saludos

Thank you

So you are using a domain for windows login rather than default setup of a local user account on the computer

This brings in a new angle to follow up on

Can you try as a test creating a temporary windows local user account on PORTATIL and run Emby Client in it and see if that gives different outcome.

[sa2000 785]

An observation on the test you did and the PML file

It shows that the EmbyClient process was already running before starting the test

It would be best to try a test with  a launch where there is no Emby.Client.WinUI.exe process showing in Task Manager - if there is one - kill it

and then launch Procmon and start capture without filtering any

and then launch Emby Windows app

and when the error pops up, note down the time and capture the diagnostics

 

[sa2000 785]

The procmon capture in the PML file you provided started at 11:05:37 and stopped at 11:07:13

The emby windows app was launched at 11:04:56 and exited at 11:06:00

There is an emby client log that shows it re launched at 11:06:11 and closed at 11:06:41 but the procmon capture seems to have been stopped at 11:06:04 and resumed capture at 11:07:03 - did you touch the capture button other than at the end to stop the capture?

It is important the the the time the error pops up is known so can be used to check the procmon and emby client log

Were you trying to get the diagnostics for 11:06:41 exit ?  The procmon capture was stopped at the time and resumed later

[sa2000 785]

sorry for multiple posts - there may be some group policy settings relating to when running on a domain that may be relevant to what the emby client app is trying to do

[Guderian 2]

3 hours ago, sa2000 said:

Thank you

So you are using a domain for windows login rather than default setup of a local user account on the computer

This brings in a new angle to follow up on

Can you try as a test creating a temporary windows local user account on PORTATIL and run Emby Client in it and see if that gives different outcome.

Hola, asi funciona correctamente. Curiosamente, no detectaba que la aplicacion ya estaba instalada y al reinstalarla la instaló en "C:\Users\test\AppData\Local\Microsoft\WindowsApps\EmbyMedia.EmbyTheater_svmepx4c03f7m"

Luego entre de nuevo con la cuenta del dominio (administrador), cambie los permisos y el propietario de la carpeta "C:\Program Files\WindowsApps\EmbyMedia.EmbyTheater_2.310.2.0_x64__svmepx4c03f7m" agregando mi cuenta de dominio con control total y todo correcto.

Voy a verificar que estos cambios funcionen en el resto de los equipos.

Saludos y gracias.