Premiere Pro 25.1 - iGPU stopped decoding my footage

[AndrewTheGreat]

Ok, just updated to v 25.1 opened my projects in progress to find that none of them uses my iGPU to decode.

Went on checking it with different formats that are decoded (h264 8-bit 4:2:0, h265 8-bit 4:2:0, h265 10-bit 4:2:0, h265 10-bit 4:2:2) by the iGPU - all of them show 0% load.

What is going on, guys? Why is it "new version - new bugs" thing every time? My CPU immediately started being loaded more, like by 60% all the time, even though my GPU does the decoding, whereas on the previous versions the average CPU load was 20-30% with the iGPU doing all the decoding job.

Yes, I tried reinstalling both Premiere Pro (as well as resetting its cache, preferences and plugins via the start+shift menu) and all the drivers. 

Steps to reproduce? Open a p;roject or create one, import a knowingly decoded video, put it on your timeline, press Play. Watch the the Windows Task manager - Performance graphs.

i7 14700K, RTX 4080, 64 Gb ram, SSDs, Win 11 24h2

[AndrewTheGreat]

Hi, @mayjain

Today I installed Windows 11 23h2 and I could see the decode graph perfectly working with Premiere Pro 24.6.4

Didn't have time to check it with 25.1 or other versions, but this is quite obvious there's some problems between these Premiere Pro and the new Windows. At the same time my colleague sent me a screenshot of Premiere Pro 25.1 with the decode graph working in 24h2 today. So I don't know where else to dig, I'm out of ideas, so I just really hope Adobe is dealing with this issue...

By the way this is a list Intel CPUs are currently capable of decoding. Will Premiere Pro by chance ever decode these formats too?

[JonesVid]

Nothing on Microsoft support site about this?.

Windows 11, version 24H2 known issues and notifications | Microsoft Learn

Some more people on Microsoft Community reporting same issues on iGPU being ignored on Win 11 24H2.

[Jazzborn]

I don't know if my problem is directly related to iGPU or anything, upon updated to 25.1 my H265 encoding is entirely nerfed. It was all good until 25.0 and I had to roll back. I didn't do any windows update recently (I usually pause windows updates until there's something critical) and I use W10 x64

Nothing fancy on my timeline either, 80p footage with some overlays etc. - anything that is fancy I pre-render them.

Usually, when I do a h265 export, my computer utilizes both CPU and GPU at maximum capacity and it takes ~20 minutes to render a 40m timeline. after 25.1 it went up to 3 hours. both CPU and GPU not very utilized at all even fans went back to casual speeds.

I checked hardware acceleration both in project settings and in media encoder, it looks normal.

I hope we can have a hotfix soon.

[AndrewTheGreat]

This may be related. This whole case looks like some crucial processes have been disrupted with both Windows and Premiere Pro Updates. May be the drivers are also involved. I've never seen so many coplaints about Premiere Pro from people here, on Reddit, in my communities like it is now since v. 25 was introduced. Like something cracked and it's now a snowball. 

[RjL190365]

For those people running Windows 11 24H2, we will have to wait until the January Cumulative update at the earliest in order to determine if this behavior is fixed. The December cumulative update has no new fixes — only security patches.

We will also have to wait until the next point release of Premiere Pro in order to find out whether the broken auto-hardware-decoder-detection in the current version 25.1 and/or the broken multi-simultaneous-decoder support since at least version 25.0 is fixed.

[AndrewTheGreat]

Hope, they'll introduce at least some fixes in the January update. Due to the specifics of my company's workflow we all have to be as up to date as possible, so I'm going to suffer. At least till January.

[JonesVid]

I don't know if this is significant @AndrewTheGreat  for the Windows 24/H2 iGPU problem - but I just noticed your iGPU driver is 31.0.101.4953 dated 7/11/2023.

Ive just updated iNTEL 770 iGPU on my machine to the latest driver from Intel Support site - 32.0.101.6314 dated 26/11/24.

I overwrote the ASUS OEM driver months ago as it was way out of date.

Running an encode on my recent project encoding a timeline with H265 media and Previews on ProRes 422 - I was producing a master ProRes 422 export using ProRes422 previews already rendered.

You can see the Intel 770  iGPU hammering away on Windows 11 23/H2 (H265 decode) as well as NVidia 4080 Super doing the encode. I assume this is the ProRes422 encode process, although not sure the split is that simple.

I can't use Win 11 24/H2 yet as I am avoiding it until we all get clear answers !!

Intel site for updates : https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html

Anyway - just a thought... it maybe worth trying for you. I know you said you had updated drivers so I was a bit puzzled by that.

[AndrewTheGreat]

@JonesVid 

I underlined in a couple of messages above that I had tried out different iGPU drivers. I do have Intel's driver assistant and was updating everything related to Intel the moment it was out. I actually had thought the driver could be an issue so I went to my motherbord manufacturer's site, which is MSI, and even tried the svga driver available there too, which happened to be this 2023 version driver and to my surprise the only one that bumped up my iGPU graph by like 80% with the footage my current up to date windows, drivers and Premiere Pro show 0%. So the old driver performed even better than the newest available. I also tried different flavours of h264 and h265 - all of them capable of being decoded - and somehow some showed the 3d graph activity and some didn't. None of them showed anything in the decode graph. Also some of them that are decoded by the 4080 would show the decode activity and some only the 3d one. I especially repeat this - all the videofiles I tested can be decoded either by the iGPU only or the iGPU and the dGPU. Have no idea why it all started to look and act like that. Every component in my 2 year-old system is fine, no errors in tests, the ultimate bios firmware, not a single glitch or problem in other software or games. But the decoding engines in my cpu just don't want to decode anything, leaving this task for 4080. And at the same time my system gets 14600 points in PugetBench Premiere Pro test ehich is even higher than Apple M4, almost all the AMDs and even some 14900k and 285k builds. So this makes it that my iGPU works in some way... I have no ideas

[JonesVid]

Ok thanks for feedback. I can now understand why you went back to the older driver from MSI.

[mayjain]

Hi All,

I wanted to share a quick update. I upgraded one of my Windows laptops to Windows 11 24H2 and noticed that the iGPU is working just fine with Premiere 25.1. Please find the screenshots attached below for reference:-

I’ll continue monitoring this and will discuss it further with my team. Sorry for the trouble. 

Thanks,
Mayjain

[AndrewTheGreat]

Hi, @mayjain 

Can you share this exact footage you tested it with? (in PM maybe). Also I can see your Windows is Enterprise, mine is Pro.

BTW today I even tried reverting the previous bios update with which my iGPU did work. And it's the same, flat in the decode graph...

[mayjain]

Hi@AndrewTheGreat @JonesVid ,

Here’s the link to the footage I was working on: https://f.io/IHptfope. 
Let me know if you have any questions. I will continue investigating this and discussing it with my team.

Thanks,
Mayjain

[AndrewTheGreat]

That's funny. But this is what I'm having with NVidia Renderer and hardware acceleration also ON with Intel beside. I suppose you are having the decode graph bumping up with this footage because your config is Intel iGPU only

[AndrewTheGreat]

And at the same time Intel's Utility shows the media engine load

[JonesVid]

Yes we need to see tests on Windows 11 pro please. Also the intel graphics chip may be important as Asus have told me. 
our desktop motherboards use intel 770 graphics chip. I think @AndrewTheGreat msi motherboard is using that too.

anyway thanks for keeping looking at this .

[AndrewTheGreat]

Yet another update. A strange one. Below are 4 screenshots:

1) Premiere Pro 25.1 with OpenCL renderer ON and NVidia decoding turned OFF in Premiere Pro Media Preferences, MOV H.264 4:2:0, Windows 11 24h2 with the UI in a non-english language, the one I'm using it in now:

See the graph - it shows the 3D load. See the Importer.MP4 data in Premiere Pro console -  it shows Hardware decoding frame count and UHD: 1 (one).

2) This is the same Premiere Pro settings and the footage used, but the UI is set to English:

See the graphs - Video Decode has appeared apart from 3D. See the Importer.MP4 data in Premiere Pro console -  it shows Hardware decoding frame count and UHD: 2 (TWO!).

Now I turn ON the CUDA renderer in File > Project Settings, and activate the NVIDIA hardware decode in Preferences > Media. This is the non-english Windows UI:

The iGPU graphs are flat. The Console shows ZERO UHD though there's the hardware decoding frame count. So the whole decoding of this file is done solely by the dGPU which is RTX 4080. In all the previous versions the decoding was done mostly by the iGPU with the dGPU as a helping hand. 

4) And here's the same Premiere Pro preferences and file rolling, but the Windows UI is set back to English:

See what changed?

[RjL190365]

Another update on my system:

When I ran Puget Systems' decoding test, I discovered that with Premiere Pro 25.1 running on Windows 11 24H2 on my main Intel i9-14900K system with an Nvidia GeForce RTX 4070 Ti, the hardware H.264 (AVC) decoding defaulted to the Nvidia GPU while H.265 (HEVC) decoding defaulted to the Intel iGPU. (This was with the Premiere Pro hardware decoding set to the default of both Intel and Nvidia enabled.) The other GPU, in either instance, showed zero usage.

As for the 24H2 feature update to Windows 11 disabling or wiping out the iGPU selection in the BIOS, it turned out that neither of my two systems had that problem. In other words, some - but not all - Windows 11 24H2 systems suffer from that problem.

[AndrewTheGreat]

Looks like - either because of some changes in Premiere Pro or in Windows or even the drivers - the system is forced to use the dGPU istead of the iGPU in all cases. I only saw the Encode graph of the iGPU loaded, obviously when exporting,  but the Decode graph does not show any load at all unless you turn off NVidia in Premiere's preferences. 

You can also try and install Shutter Encoder and run transcoding to ProRes

- this way the iGPU is forced and in my case I always get this error:

 

[JonesVid]

I was wondering what Intel chipset your motherboards are using ? @RjL190365 

I contacted ASUS and they claim the problem is only affecting some users of their motherboards with a 'certain' chipset with Win 11 24/H2.

They did not say which chipset they are referring to in their email update - but I have asked them to be more specific.

Their current workaround of disabling the iGPU is hardly a solution, but it would seem they are in communication with Microsoft on this issue.

Intel 770 seems to be a common one used.

[RjL190365]

My Intel system's motherboard is equipped with a Z690 chipset (in particular, the motherboard is an Asus TUF Gaming Z690-PLUS WiFi (DDR5)). However, I have updated the motherboard's BIOS twice since I updated to 24H2.

[R Neil Haugen]

The newest Win11 update has turned off iGPU use for several users. Who had to go into the BIOS to turn them back on. That may be an issue here.

[AndrewTheGreat]

Hi, @R Neil Haugen 

I went to Bios and it was on. I turned it off and on again and it didn't help.

[R Neil Haugen]

Then it's something flipping else on your rig. Dang.

[AndrewTheGreat]

If it was only my rig... Another case like this from my friend I got just yesterday - on 13600k. 

[JonesVid]

@R Neil Haugenall evidence is pointing to Microsoft W11 24H2 !

Another person on Microsoft Community said they have same issue of iGPU not working alongside their discrete GPU.

No news whatsoever from Microsoft on this problem, but we know ASUS are in contact with them on it.

I've not got much information out of them however. No surprise there.