home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Running TVService as "NT Service\TVService" or "Local Service" not working anymore since Windows September 2025 updates
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Andy_2639" data-source="post: 1303846" data-attributes="member: 161048"><p>I used to run the TVService under the "NT Service\TVService" account to follow least privileges principal (not exposing my whole system in case there's a security bug in the tv server). That worked fine until I installed the 2025-09 Windows updates 2 weeks ago.</p><p></p><p>From that on, I need to run the TVService as "Local System" which means the tv server can just do everything. I also tried running it as "Local Service" but that doesn't work the same way "NT Service\TVService" doesn't work.</p><p></p><p>Running at "NT Service\TVService" or "Local Service", it looks like the tv server is unable to correctly talk with my TV card. It has an LED which shows activity. This LED just lights up a short time (so, some communication is happening) but then immediately turns out.</p><p>With "Local System", watching, recording TV and channel scan just works.</p><p></p><p>I verified this with my HTPC and PCTV 461e TV card. On this system, I also checked with a Digital Devices Cine S2 V7 Advanced.</p><p>I could reproduce it on a Laptop with the PCTV 461e TV card, too.</p><p>OS: Windows 11 Pro 24H2 x64 Build 26100.6584.</p><p></p><p>With the Digital Devices Cine S2 V7 Advanced, the DD Control Center didn't even show that the card is used. When the tuner is tuned, the control center normally shows some details like frequency and reception strength.</p><p></p><p>I attached the debug logs when running under "NT Service\TVService" and trying to watch a channel; IP addresses, names of recordings and computer names masked.</p><p></p><p>One think I think I noticed: When running the TVService as "Local System", watch a program and then stop the service and start it again running as "NT Service\TVService", it might work for some time - but definitely doesn't survive a reboot.</p></blockquote><p></p>
[QUOTE="Andy_2639, post: 1303846, member: 161048"] I used to run the TVService under the "NT Service\TVService" account to follow least privileges principal (not exposing my whole system in case there's a security bug in the tv server). That worked fine until I installed the 2025-09 Windows updates 2 weeks ago. From that on, I need to run the TVService as "Local System" which means the tv server can just do everything. I also tried running it as "Local Service" but that doesn't work the same way "NT Service\TVService" doesn't work. Running at "NT Service\TVService" or "Local Service", it looks like the tv server is unable to correctly talk with my TV card. It has an LED which shows activity. This LED just lights up a short time (so, some communication is happening) but then immediately turns out. With "Local System", watching, recording TV and channel scan just works. I verified this with my HTPC and PCTV 461e TV card. On this system, I also checked with a Digital Devices Cine S2 V7 Advanced. I could reproduce it on a Laptop with the PCTV 461e TV card, too. OS: Windows 11 Pro 24H2 x64 Build 26100.6584. With the Digital Devices Cine S2 V7 Advanced, the DD Control Center didn't even show that the card is used. When the tuner is tuned, the control center normally shows some details like frequency and reception strength. I attached the debug logs when running under "NT Service\TVService" and trying to watch a channel; IP addresses, names of recordings and computer names masked. One think I think I noticed: When running the TVService as "Local System", watch a program and then stop the service and start it again running as "NT Service\TVService", it might work for some time - but definitely doesn't survive a reboot. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Running TVService as "NT Service\TVService" or "Local Service" not working anymore since Windows September 2025 updates
Contact us
RSS
Top
Bottom