# Another QuickSync Issue

**URL:** <https://forums.plex.tv/t/another-quicksync-issue/695594>\
**Category:** Plex Media Server\
**Tags:** server-windows\
**Created:** [February 28, 2021, 2:53pm UTC](https://forums.plex.tv/t/another-quicksync-issue/695594 "2021-02-28T14:53:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![themurpys](https://avatars.discourse-cdn.com/v4/letter/t/e99b99/32.png) [@themurpys](https://forums.plex.tv/u/themurpys)\
**Post date:** [February 28, 2021, 2:53pm UTC](https://forums.plex.tv/t/another-quicksync-issue/695594/1 "2021-02-28T14:53:47Z")

</div>

Server Version#: 1.21.4.4079 (Running as a service with the PlexService app)  
Player Version#: any player

So I have a new Windows 2019 server and was looking forward to using Quick Sync for transcodes with a 10700, but it doesn’t work. I can use QSV just fine in Handbrake however, so it’s something with Plex. It’s not a headless display, there is a monitor connected through the HDMI slot.

I have updated to the latest Intel video drivers as well, and the behavior varies from Plex crashing to just not using the hardware to encode or decode.

I had a really old server previous so it’s kind of heartbreaking not to be able to use the new one properly! On the bright side the CPU alone can do a 4k transcode when necessary but it gets pegged, something I’d like to avoid.

It’s not detecting it apparently:  
Feb 28, 2021 09:33:17.173 [1516] DEBUG - [Transcode] Streaming Resource: Determining preferred transcode encoders through transcode only decision.  
Feb 28, 2021 09:33:17.173 [1516] DEBUG - [Transcode] Codecs: testing h264\_qsv (encoder)  
Feb 28, 2021 09:33:17.174 [1516] DEBUG - [Transcode] Codecs: hardware transcoding: testing API qsv  
Feb 28, 2021 09:33:17.175 [1516] ERROR - [Transcode] [FFMPEG] - Failed to create Direct3D device

Thanks for any help on this topic.

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [February 28, 2021, 8:16pm UTC](https://forums.plex.tv/t/another-quicksync-issue/695594/2 "2021-02-28T20:16:37Z")

</div>

> [@themurpys](#):
>
> (Running as a service with the PlexService app)

System services don’t get access to the hardware drivers. Which are necessary for hardware encoding. This is a Windows limitation.

---

<div class="post-metadata">

**Author:** ![themurpys](https://avatars.discourse-cdn.com/v4/letter/t/e99b99/32.png) [@themurpys](https://forums.plex.tv/u/themurpys)\
**Post date:** [March 1, 2021, 1:22am UTC](https://forums.plex.tv/t/another-quicksync-issue/695594/3 "2021-03-01T01:22:07Z")

</div>

Yeah I figured that out after posting this and doing more research. Really stinks to be honest, because the whole point of a server is to have it being a service and forgetting about it. HW acceleration isn’t optional with 4k streams though, so I guess I’ll look into the task scheduler method and hope for the best. Thanks for the reply!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [May 30, 2021, 1:22am UTC](https://forums.plex.tv/t/another-quicksync-issue/695594/4 "2021-05-30T01:22:32Z")

</div>

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