Windows Client App slow to start

Plex Players Desktop Players
1

Server Version#: 1.41.2.9200
Player Version#:1.105.1.257-3bc35ab9

Over the last month I have experienced 20 second start up on the Windows Client from launch until the accounts are presented for signin. Using the Web CLient on the same PC, it comes up in a couple of seconds. I looked at PMS logs turned off and on and off debugging and verbose debgugging. The only error of note I saw was PMS looking for an MP3 file that really exist and I deleted that from the Plex client. I ran an clean bundles and optimize libraries without any impact. Seems if I run the client on the same system (WIndows) as PMS, it comes up really quick. That smells like some type of network issues - and yes, there have been network changes recently. PMS machine is wired to the network, this client is on Wifi, I tried the client on a wired Windows PC and that was actually worse. Looking for some clue as to where the network issues might be - I suspect it’s either a firewall issue or some other aggressive traffic analysis ?? The weirdness here is that the App eventually comes up… so is it looking for alternate paths? I did turn off the FW on both the clients and server and while I got each client to come up within seconds, it was haphazard. As I turned FWs back on and tried one side (client) or the other only (server) sometimes it worked, sometimes not. Then turned both sides off and - again, 20+ seconds to fire up… I’m exhausted.

2

I had this recently. Plex support told me to unmap any network drives that were/are currently unavailable.

Incidentally, it would open and be ready to use much quicker if opened as administrator.

3

thanks, removed mapped drive not available - that worked (though I need to have that mapping), but I think I have seen that “run as administrator” behavior, so i may try one of those admin/UAC workarounds.

4

The other thing that was suggested was to create a shortcut on the desktop to the unmapped drive for when it’s in use. Hang on, let me find the thread…

Here you go:

5

thanks I’ll give that a try… tried the techniqiue to bypass the UAC warning using a shortcut to a task scheduled… doesn’t seem to work as well as removing the mapped drive… so this shortcut might help.

6

The “Open as Admin”-technique might only work because the Admin account on the user’s machine doesn’t have those invalid drive letters linked, while the regular user account has them.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.