Windows 11 App Refusing to Load

[Natelanxon 28]

Hi. I just installed Emby from the Windows 11 Store and it refuses to open. I checked Task Manager and after clicking the app, I briefly get one instance of Emby.Client.WinUI appearing but then disappearing after about 2 seconds and then nothing happens. I checked Windows Event Viewer logs for instances of a crash and can find nothing. What can I check to find something helpful in diagnosing this problem?

This is my system:
Edition    Windows 11 Pro
Version    25H2
Installed on    ‎04/‎10/‎2025
OS build    26200.8655
Experience    Windows Feature Experience Pack 1000.26100.315.0
 

Emby installed version is 2.315.2.0

Thanks

[Mahinepua 118]

can you see your server on the web app from the same machine?

[Natelanxon 28]

I can yes. I used the web app when the native app wouldn’t load. I’d prefer to be able to use the native one though if there’s a way. 

[Mahinepua 118]

hmm, try updating to the latest windows version, it should be under the optional update section.

plan B, uninstall and reinstall.

[Natelanxon 28]

Tried these. I also tried updating to the preview update as well. Nothing seems to do anything. 

[Neminem 1780]

Are there any logs in this dir?

C:\Users\%username%\AppData\Local\Packages\EmbyMedia.EmbyTheater_svmepx4c03f7m\LocalCache\logs

That might show what's going on.

[sa2000 788]

On 10/07/2026 at 11:58, Natelanxon said:

I checked Windows Event Viewer logs for instances of a crash and can find nothing.

Was that checking the "Application" log in "Windows Logs" for Source: "Application Error" relating to the Emby app ?

A suggested the logs may have some clues

 

[softworkz 5289]

On 7/10/2026 at 11:58 AM, Natelanxon said:

Hi. I just installed Emby from the Windows 11 Store and it refuses to open. I checked Task Manager and after clicking the app, I briefly get one instance of Emby.Client.WinUI appearing but then disappearing after about 2 seconds and then nothing happens. I checked Windows Event Viewer logs for instances of a crash and can find nothing. What can I check to find something helpful in diagnosing this problem?

@Natelanxon

 

• Is this a cloud VM?
• Did you perhaps enable and use the original Windows administrator account where you don't need/have any elevation requirements and you don't get any UAC (user account control) prompts?
• Can you run other Windows Store apps without problems?
• Is your machine member of a Windows domain?
• Do you have any group-policies configured which might prevent the launch?
  => run gpresult.exe /v

And please look for logs like @Neminemsuggested.

Thanks

[Natelanxon 28]

On 11/07/2026 at 13:07, Neminem said:

Are there any logs in this dir?

C:\Users\%username%\AppData\Local\Packages\EmbyMedia.EmbyTheater_svmepx4c03f7m\LocalCache\logs

That might show what's going on.

No, that folder doesn't exist. Everything up to /LocalCache is there, but there is no log dir.

21 hours ago, softworkz said:

@Natelanxon

 

• Is this a cloud VM?
• Did you perhaps enable and use the original Windows administrator account where you don't need/have any elevation requirements and you don't get any UAC (user account control) prompts?
• Can you run other Windows Store apps without problems?
• Is your machine member of a Windows domain?
• Do you have any group-policies configured which might prevent the launch?
  => run gpresult.exe /v

And please look for logs like @Neminemsuggested.

Thanks

It's not a cloud VM but it is a VM. My other apps, including those from the Windows Store, all work fine. It's only Emby that doesn't launch.

I also tried launching the app as an admin but that didn't make a difference other than to give me the elevation prompt by Windows.

It's not part of a domain and there shouldn't be any group policies as it's a pretty standard Parallels VM that runs a handful of apps.

I'm guessing the nature of it being a VM is part of the issue but it seems strange my other apps work fine. I wonder if there's anything I can try?

[Natelanxon 28]

Incidentally, the old Windows Theater app worked fine. I've just pulled that from Github to test and it works. I guess if nothing else works I can still use the old version.