However, I only have one user that signs into my Plex server so this isn’t a problem. OS: Windows 11 Professional (64-Bit) CPU: 3.4GHz Intel i7-12700T 12-Core processor Turbo Boost Speed: 4.7 GHz Cache: 25 MB GPU: Intel UHD 770 Graphics RAM: 32GB RAM Slots: 2x SO-DIMM 3200 MHz DDR4 Maximum RAM Capacity: 64GB Storage: 2TB M.2 NVMe PCIe Backup Storage: N/A USB Ports: 5x USB 3. It also means that if you signed in a different user before the reboot it will load that user instead, so this method won’t work. This is great because it means that if Windows decides to force an automatic update and reboot your Plex server it will start the Plex service after it’s finished rebooting. This PC is mainly a server, but I do use it lightly for other various things daily, so I went ahead and upgraded. There is a predefined group policy that you can enable that will automatically sign in the last interactive user. I didn’t feel like trying it, so I found a simple workaround on Windows. However, this isn’t officially supported by Plex, and involves making some configuration changes. There is a project someone developed to solve this issue: This is a problem if you’re not at home to sign back in but need to access your Plex media. This means that if you reboot your computer the Plex service will not run until you log back in with the user Plex runs under. Has an automatic Windows update ever broken your connection to your Plex server? For some reason Plex runs under a standard user account and not under a service user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |