I'm running the Mediaportal 1.4.0 Pre-Release on a Windows 8 64-bit System. My issue is nothing at all to do with MePo; rather it's the TV Service and how it interacts with Win8. I've been getting this message in my Event Log, and I'm not sure what's causing it:
"The TVService service did not shut down properly after receiving a pre-shutdown control."
Windows 8 is telling the TV Service, "Hey, it's time to shut down, man," and the TV Service is like, "F*ck off, I'll shutdown when I want, not when you tell me!" It's causing a slight delay when the system shuts down.
- System
- Provider
[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager
- EventID 7043
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2013-05-30T10:58:12.952803600Z
EventRecordID 342730
Correlation
- Execution
[ ProcessID] 688
[ ThreadID] 5000
Channel System
Computer David-PC
Security
- EventData
param1 TVService
5400560053006500720076006900630065000000
Manually stopping the TV Service - rather than letting Win8 shut it down - seems to be a workaround for the issue.
"The TVService service did not shut down properly after receiving a pre-shutdown control."
Windows 8 is telling the TV Service, "Hey, it's time to shut down, man," and the TV Service is like, "F*ck off, I'll shutdown when I want, not when you tell me!" It's causing a slight delay when the system shuts down.
- System
- Provider
[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager
- EventID 7043
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2013-05-30T10:58:12.952803600Z
EventRecordID 342730
Correlation
- Execution
[ ProcessID] 688
[ ThreadID] 5000
Channel System
Computer David-PC
Security
- EventData
param1 TVService
5400560053006500720076006900630065000000
Manually stopping the TV Service - rather than letting Win8 shut it down - seems to be a workaround for the issue.
Last edited: