Windows Emby App Startup Problem

[softworkz 5065]

That's interesting. 

The process tree looks quite different here:

 

It could be due to Windows 10 (your on 10, right?)

How does it look like when it doesn't hang?

And when it hang, can you please right-click "Microsoft Edge WebView2" (the one without the green icon), then Properties and check the file location.

Thanks!

[frankmb 41]

I am on Windows 10 yeah.

When it does not hang it looks like this. There is a 2nd Edge

 

 

When it does not hang the location is

 

 

I will report what is the location is when it hangs the next time it hangs.

[frankmb 41]

I tested a bit more. Normally there is only one "Microsoft Edge WebView2" when Emby launches successfully.

However if Emby hangs on launch then is shut down, the next time Emby is launched there are 2 "Microsoft Edge WebView2" in the task manager.

[softworkz 5065]

Thanks a lot for testing. The number of processes is not that important, it's the same like chrome.exe or msedge.exe, there are often multiple processes due to sandboxign and separation of rendering and management code.

It was only the non-Emby icon which caught my attentiion and I thought this might be the system-webview2 instead of the webview2 runtime included with Emby.
Yet it seems that the difference is only the icon, which might be due to platform differences (10 vs. 11).

So, unfortunately, we're back to start.

Can you enable debug logging and post/send the log file when it hangs again?

Thanks!

[frankmb 41]

Here is a debug log for failed launch. I launched on 7:19 and I waited until 7:21 to shut it down.

Also here is the debug log for the successful launch just after.

EmbyClient hang on launch.txtEmbyClient successful launch.txt

[softworkz 5065]

Thanks a lot for the logs. The cause is that the DOMContentLoaded event doesn't get fired, even though it's unclear why.

Yet that gave me an idea for a potential fix. A new 2.226.0 beta is coming in a few hours, hopefully it will do the trick.

Thanks

[softworkz 5065]

@frankmb - Could you give it another try with the new 2.226.0 beta?

Thanks!

[softworkz 5065]

A new test by @Neminemindicates that it might be fixed in 2.226: https://emby.media/community/index.php?/topic/138510-new-windows-xbox-beta-222600-beta/#findComment-1442030

[frankmb 41]

7 hours ago, softworkz said:

@frankmb - Could you give it another try with the new 2.226.0 beta?

Thanks!

I don't know where to get the Beta

[softworkz 5065]

Sorry, I thought you'd be a beta member as I remembered seeing your name before  

(there's no new onboarding at the moment, so we'll have to wait until it's published)

Thanks

[frankmb 41]

No problem. Yeah I was on the Roku app beta

[SLMK 19]

Is there any update on this issue? it happens almost every day for me on first launch.

If I close the app and open it again it will launch fine.

[Luke 42077]

14 hours ago, SLMK said:

Is there any update on this issue? it happens almost every day for me on first launch.

If I close the app and open it again it will launch fine.

Hi, we are looking into it. Thanks.

[softworkz 5065]

On 7/11/2025 at 6:32 AM, SLMK said:

Is there any update on this issue? it happens almost every day for me on first launch.

If I close the app and open it again it will launch fine.

@SLMK The reported issue in this conversation has been resolved since version 2.226

Please create a new topic and describe your symptoms including .logs.

Thank you

[Lessaj 467]

On 7/14/2025 at 7:42 AM, softworkz said:

@SLMK The reported issue in this conversation has been resolved since version 2.226

Please create a new topic and describe your symptoms including .logs.

Thank you

I really don't think it was or it wouldn't have been bumped. The CoreWebView2_DOMContentLoaded event is still not being fired sometimes or at least not completing and thus not logging, exactly as you previously described. I am a very infrequent user of the Windows app, probably less than once a month, but that's the only observation I've come to during this failure to load. I am on Windows 10. Yes closing and opening it again does work.

[softworkz 5065]

35 minutes ago, Lessaj said:

The CoreWebView2_DOMContentLoaded event is still not being fired sometimes or at least not completing and thus not logging, exactly as you previously described.

Right. But 2.226 has a change that it also monitors the NavigationCompleted event - which always fires and since then, none of the participants in this conversation has ever reported that it would still be a problem for them.

This is evidence enough to assume that @SLMKis facing a different issue. We need a new topic and logs from him to look at. Or from yours, @Lessajif you still see this with the latest version.

Thanks

[Lessaj 467]

6 minutes ago, softworkz said:

Right. But 2.226 has a change that it also monitors the NavigationCompleted event - which always fires and since then, none of the participants in this conversation has ever reported that it would still be a problem for them.

This is evidence enough to assume that @SLMKis facing a different issue. We need a new topic and logs from him to look at. Or from yours, @Lessajif you still see this with the latest version.

Thanks

I don't see the NavigationCompleted event, but I created a new thread as requested with logs.

[michaeltruncale 6]

Any updates on this one? 

[Luke 42077]

4 minutes ago, michaeltruncale said:

Any updates on this one? 

Hi, we are working on chasing this down. Thanks.

[frankmb 41]

On 7/15/2025 at 5:01 PM, softworkz said:

Right. But 2.226 has a change that it also monitors the NavigationCompleted event - which always fires and since then, none of the participants in this conversation has ever reported that it would still be a problem for them.

This is evidence enough to assume that @SLMKis facing a different issue. We need a new topic and logs from him to look at. Or from yours, @Lessajif you still see this with the latest version.

Thanks

I still have this same startup problem. It has never stopped. Please don't assume that users disappearing ever means that a bug is resolved.

 

So many issues reported on this forum never get fixed that I imagine people lose interest in reporting. That is certainly how I feel. 

[softworkz 5065]

18 hours ago, frankmb said:

I still have this same startup problem. It has never stopped.

Yes I know - it's an open issue.

 

18 hours ago, frankmb said:

Please don't assume that users disappearing ever means that a bug is resolved.

We do not make assumptions. For everything that is tracked internally, we try to get user confirmation before marking it as done. 

And yes, users who have reported already and are remaining silent is not a suitable measure. But what _is_ a suitable mesasure is when the user counts are increasing but reports on the issue are not. 
I know very well how annoying these things can be, but neither impact (users affected) nor severity (nit > annoyance > showstopping > security-issue) would justify working on it out-of-the-line. Even more, since we cannot reproduce. This means we need  an interactive approach witth the affected users going over several versions in order to identify a suitable solution. We have a dozen of other issues of this type and it's not possible to do such experimental work with stable releases - it requires a beta phase.

 

18 hours ago, frankmb said:

So many issues reported on this forum never get fixed that I imagine people lose interest in reporting. That is certainly how I feel. 

I understand that and I think we shouldn't create the impression that we would be always working on everything. We simply cannot do that.
The problem with creating that impression is that people are eagerly waiting, expecting it to - possibly - happen any other day.

So, to kind-of break out of this pattern, the direct and truthful answer is this:

• There won't be any work on this until the next beta, so there's no fix to be expected meanwhile
• When the next beta starts - you (and all other affected users) are very welcome to join, test and provide feedback, and we'll work on this until it is resolved for everybody.
  I'm looking forward to it, and while I can't give any ETA, be assured that it will be worked on, then.

Thanks for your understanding

[SirKelsaLot 5]

This is a persistent issue for me on Windows 10 as well. I'm on a train now and no matter how many times I open, close, or restart my PC it never loads. defeats the whole purpose of having downloaded movies for offline viewing since the app doesn't start at all. It's the same whether on wifi or entirely offline.

[Luke 42077]

On 9/14/2025 at 12:57 PM, SirKelsaLot said:

This is a persistent issue for me on Windows 10 as well. I'm on a train now and no matter how many times I open, close, or restart my PC it never loads. defeats the whole purpose of having downloaded movies for offline viewing since the app doesn't start at all. It's the same whether on wifi or entirely offline.

hi @SirKelsaLotdoes this only happen for you when the emby server is offline?

[softworkz 5065]

On 9/14/2025 at 6:57 PM, SirKelsaLot said:

This is a persistent issue for me on Windows 10 as well. I'm on a train now and no matter how many times I open, close, or restart my PC it never loads. defeats the whole purpose of having downloaded movies for offline viewing since the app doesn't start at all. It's the same whether on wifi or entirely offline.

Have you read the whole conversation?

Did you update your graphics drivers to the latest?

Does it never launch or only takes just a second attempt (like for the others)?

Did it ever launch, actually?

[SirKelsaLot 5]

On 9/26/2025 at 1:52 AM, Luke said:

hi @SirKelsaLotdoes this only happen for you when the emby server is offline?

In that scenario, I was technically on wifi so it would have been online, but likely slow since it was public wifi on the train. I closed/open the app dozens of times, restarted the laptop, etc, but it was never able to move past the loading screen. In that case, even when I fully disconnected from wifi/airplane mode, I closed/reopened and would have expected the "offline" landing page where I could select to at least see my Downloads folder within Emby, but that never came either. Result was that I was unable to open Emby at all over that 6+ hour trip.

Last week, I noticed that my laptop ran out of disk space when downloading something unrelated and outside of Emby. Upon looking at disk usage, I noticed the local Emby Windows media directory was way too large given what I had synced/downloaded within Emby. Upon drilling into the subfolders below:

C:\Users\[Profile]\AppData\Local\Packages\EmbyMedia.EmbyTheater_svmepx4c03f7m\LocalState\data\syncItems

I noticed many old video files which I had downloaded/sync over past months that did not show themselves within the Emby app. Meaning, I had downloaded, watched, and deleted them within Emby but they were still on the disk itself. I don't know that that is at all related, but I manually deleted all the synced files there. Sometime after this when I was back on my home network, it began opening fine. I don't think I did anything special to make it work again, I just tried again later on a different connection.

For the "2nd attempt" scenario, yes, that is how it normally behaved for me when I'm on my home wifi. However, on this trip, no amount of attempts worked.

Regarding video drivers, this is technically a work computer (not on a domain), so I don't have the access to update the drivers myself. Only that which I receive via Windows Update. It does show the Intel driver version 32.0.101.6881 from June 2025.