Old and new Windows client problems.

[pwhodges 1797]

PROBLEM 1:

I had not taken note of the new Windows client for some reason, so I have been continuing to use the excellent Electron-based Theatre client.  Today I discovered that this client is the cause of an apparently unrelated problem - after I start the Electron-based client, the \ and ` keys on my Perixx keyboard get swapped, and the PrtSc triggers my SCP client.  Perixx support are unaware of any way in which this can happen, and the only way to get the keys right again is a full OS restart (or just living with the keys swapped...).  (I suspect this is something to do with Electron itself rather than Emby.)

-------

PROBLEM 2:

Having discovered this, I decided to try the new Windows Store client.  After downloading it, I found that it was already installed, because the old Windows Store client which I tried in the past had automatically been updated.  When I started it, it found my server, but required a login, so I logged in, ticking the remember me box, of course.  I then checked that the keyboard keys had not been swapped by it (they hadn't).  Finally, I closed the left-hand menu, which I don't like, and then closed the client.  So far so good...

I then tried to enter the client again, and it hung on the Emby logo.  This behaviour has persisted through a system restart. Resetting or Repairing the app in Settings has no effect.  After uninstalling and reinstalling, it works just once and then fails to work on subsequent calls.

Any idea how to get out of this jam?

In the log, the only actions after the server restart were a successful run after reinstalling with a couple of library browses, then over several minutes additional attempts to run the client, which appear to generate no entries in the server log file.

Paul

embyserver.txt

[pwhodges 1797]

I am getting the same some similar behaviour on a completely different Windows setup (Laptop vs Desktop, Win10 vs Win11, etc), so I guess it's something about my server that it doesn't like.  Installed - ran OK.  Next run - hung at logo.  Then ran previously installed Emby Theatre - OK, as usual. Now new Emby runs as expected every time... (on that machine only, of course).

Paul

@softworkz

[pwhodges 1797]

I tried installing in two different users.  The installation failed on the first call in one case and the second call in the other, which maybe indicates that it is not the re-installation that fixes the issue temporarily, but the preceding un-installation (which in this case there wasn't).

Other notes - all users tried are domain users, and the behaviour is the same for unprivileged users and administrators.

Paul

Edited February 1 by pwhodges

[Mahinepua 58]

If its hanging at the animated logo it cant find your server.

Firewall issue maybe?

 

[pwhodges 1797]

It finds it first time after uninstallation and reinstallation.  Then one minute later after being closed and reopened it fails - what changed?

The problem has to be in the client, because it is consistently changing its behaviour between the first and second runs when nothing else changes; it may be sensitive to some specific system configuration, but whatever is causing it is not affecting any other Emby client, only this one.

Paul

[softworkz 4456]

On 1/31/2025 at 1:36 PM, pwhodges said:

PROBLEM 1:

I had not taken note of the new Windows client for some reason, so I have been continuing to use the excellent Electron-based Theatre client.  Today I discovered that this client is the cause of an apparently unrelated problem - after I start the Electron-based client, the \ and ` keys on my Perixx keyboard get swapped, and the PrtSc triggers my SCP client.  Perixx support are unaware of any way in which this can happen, and the only way to get the keys right again is a full OS restart (or just living with the keys swapped...).  (I suspect this is something to do with Electron itself rather than Emby.)

You are saying the keys get swapped not only while using the Electron app but at the OS-level, even when the app is stopped?

 Have you gone through Windows language options? I have multiple keyboard layouts installed, and there are some key combinations which automatically switch it.
There's also the option to switch keyboard layout per app, maybe that's configured and it doesn't switch back?

 

[softworkz 4456]

On 1/31/2025 at 1:36 PM, pwhodges said:

PROBLEM 2:

Having discovered this, I decided to try the new Windows Store client.  After downloading it, I found that it was already installed, because the old Windows Store client which I tried in the past had automatically been updated.  When I started it, it found my server, but required a login, so I logged in, ticking the remember me box, of course.  I then checked that the keyboard keys had not been swapped by it (they hadn't).  Finally, I closed the left-hand menu, which I don't like, and then closed the client.  So far so good...

I then tried to enter the client again, and it hung on the Emby logo.  This behaviour has persisted through a system restart. Resetting or Repairing the app in Settings has no effect.  After uninstalling and reinstalling, it works just once and then fails to work on subsequent calls.

Any idea how to get out of this jam?

In the log, the only actions after the server restart were a successful run after reinstalling with a couple of library browses, then over several minutes additional attempts to run the client, which appear to generate no entries in the server log file.

Could you please post the client logs (not server)?

1. From the first time it starts

2. From the second start where it hangs

 

 

[pwhodges 1797]

1: Nothing to do with OS options - the changes are too bizarre; and yes, once changed, it remains until the next hardware reset (reboot).  But don't worry - I'll not run the electron version again (I uninstalled it as a test, and now can't download it anyway).

2: Where are the logs for this client?

Paul

[softworkz 4456]

7 minutes ago, pwhodges said:

2: Where are the logs for this client?

When you run it, go to "Settings >> About", there it shows the specific log path on your machine.

[softworkz 4456]

Oops, forgot to say: please switch debug logging on..

[pwhodges 1797]

Hmm; I can't now get it to work without hanging! (even tried uninstall, reboot, reinstall sequence)

I'm late for bed, so I'll try some more tomorrow.

Can you indicate whereabouts the log should be in a normal Windows install?

Paul

[davidb7170 11]

The irony in trying to find the path in the "Settings >> About" assumes you have a working app interface to get to the "Settings >> About" page... The point is we cannot get to that to find the path to the logs....

[Neminem 763]

%USERPROFILE%\AppData\Local\Packages\EmbyMedia.13848C33ED80B_svmepx4c03f7m\LocalCache\logs

This part of the path might differ EmbyMedia.13848C33ED80B_svmepx4c03f7m

Ups that the Beta path

Edited February 2 by Neminem
Ups

[Neminem 763]

Stabil release.

%USERPROFILE%\AppData\Local\Packages\EmbyMedia.EmbyTheater_svmepx4c03f7m\LocalCache\logs
 

[pwhodges 1797]

Found it now, thanks - the part I didn't anticipate was the "Packages" within AppData\Local.

Unfortunately uninstalling removed the old logs which would have included a successful run, and without debug set, the log of the failures is clearly entirely useless.

But I have something else to investigate, as since I started this Handbrake is failing with a permissions error, and I need to see if it's actually related.

Paul

[softworkz 4456]

One other thought: Have you ever waited more than 30s? That's the connection timeout. In case it would try a different way (e.g. ip address) on a subsequent start, it might take that long until you see something.

[pwhodges 1797]

I've certainly left it for multiple minutes.

Currently thinking about things which have happened on the same day:
New Intel A380 driver
Handbrake issue
Emby client issue
RDP display delays (when I connect to a server, there is a 15 sec delay before the screen is shown).

(No errors in Event log)

I could try swapping in an NVidia card for the Intel, I guess...

Paul

[pwhodges 1797]

I didn't even put in the NVidia - I removed the A380 and reverted to the onboard (Intel) video, and the Emby client seems to be working fine.  Without reinstalling since the last failure it has now worked correctly several times.  And the RDP issue is gone as well (the Handbrake one is irrelevant, as it was set to use the A380 for AV1 encoding, so there's no direct comparison to be made).  Intel driver strikes again, perhaps!

I guess the next job is to try again with the A380 but using an previous driver.  I may come back to that, but just now I have some other things to do.

Paul

Edited February 2 by pwhodges

[Neminem 763]

@pwhodgesIt seams like yet another Intel driver issue, this might help fine the right driver. 

 

[softworkz 4456]

3 hours ago, pwhodges said:

I didn't even put in the NVidia - I removed the A380 and reverted to the onboard (Intel) video, and the Emby client seems to be working fine.  Without reinstalling since the last failure it has now worked correctly several times.  And the RDP issue is gone as well (the Handbrake one is irrelevant, as it was set to use the A380 for AV1 encoding, so there's no direct comparison to be made).  Intel driver strikes again, perhaps!

I guess the next job is to try again with the A380 but using an previous driver.  I may come back to that, but just now I have some other things to do.

For most of the time during development I had Onboard-Intel + Nivdia Quadro RTX + Intel A380. This worked fine at least until Sep/Oct 24 and the drivers were recent at that time (max 1/2 months old).

One thing you can try is this registry change (with the latest Intel drivers): DisableRdpHwRendering.reg

[pwhodges 1797]

I've installed 31.0.101.5382, and after a cup of tea I'll try putting the card back in.

If the new client then works with the card in and the old driver, I'll try the new driver again with your suggestion.  It's interesting that the latest driver introduced an RDP issue, and your suggestion seems to relate to that...

Paul

[pwhodges 1797]

OK, so even with the old driver, replacing the card still breaks both Emby client and RDP; the registry entry also does not make the RDP behave any better.

It may be that installing the old driver over the latest has left some detritus which is causing the problem, but right now I'm not going to rebuild my system from scratch (it takes me about a week) to try a version that's not been "corrupted" by the new driver.  I'll remove the card again and live without it (maybe actually put the nvidia in), and maybe try with a newer driver in a month or two.

Paul

[softworkz 4456]

19 minutes ago, pwhodges said:

OK, so even with the old driver, replacing the card still breaks both Emby client and RDP; the registry entry also does not make the RDP behave any better.

It may be that installing the old driver over the latest has left some detritus which is causing the problem, but right now I'm not going to rebuild my system from scratch (it takes me about a week) to try a version that's not been "corrupted" by the new driver.  I'll remove the card again and live without it (maybe actually put the nvidia in), and maybe try with a newer driver in a month or two.

Did you download the drivers from the Intel website directly?
These are installing and replacing older versions cleanly.

Regarding RDP, you can make a more radical test by disabling the "Remote Desktop Services" service and restart.

Other hints:

• Latest Mainboard Bios?
• ResizableBar enabled in Bios?
• Thunderbolt enabled? (try disabling)
• Max memory assigned for onboard graphics? (instead of auto)
• How is your monitor connected? Onboard or A380?
• Which is the primary graphics adapter?
  • A: In the bios? (= the one where you see boot process on the monitor)
  • B: On Windows? (under display settigns: "Make this my main display")
• Which CPU generation du you have? Is it supported by the same driver`as the A380?

 

 

[pwhodges 1797]

I couldn't find the driver I wanted (I found a version dropdown, but it didn't go back that far), so I downloaded from softpedia.  The install behaved as I expected, noting that it was older than the existing, and asking if I wanted to force the installation.

The BIOS is 2 years old - there are a dozen more recent, but mostly adding support for new processors (the manufacturer recommends not updating without a specific reason).  The mobo is ASRock H670PG Riptide, with BIOS 11.05.

Resizable bar is enabled.  Thunderbolt no idea.  Memory assignment no idea.  

For tests monitor was on A380, set as primary in BIOS (not auto).  No dummy plug or anything plugged into the onboard.  Only one display.

Cpu i5-12600 - presumably supported by the same driver...

As for RDP, I'm wondering what can affect both that and Emby...

Paul

[Clackdor 82]

22 minutes ago, pwhodges said:

I couldn't find the driver I wanted (I found a version dropdown, but it didn't go back that far), so I downloaded from softpedia.  The install behaved as I expected, noting that it was older than the existing, and asking if I wanted to force the installation.

I had to use the wayback machine to get the driver version I wanted from the Intel site. Just figured I would mention this as some people may not be comfortable getting drivers from other sources.