BEWARE Latest Nvidia GTX 591.44 Drivers

me_again wrote on 12/5/2025, 7:09 AM

Greetings All,

Installed the Nvidia graphics driver 591.44 (591.44-desktop-win10-win11-64bit-international-dch-whql) earlier today. Just tried to export a video and MS 2025 says "please update to latest graphics driver" (or words to that effect) and there was NO hardware encoding.

Tried several times with different projects, the same result.

\re-installed the drivers (didn't uninstall the new ones first), the same result.

Over wrote the new drivers with the previous version 581.80 and hardware encoding is available and useable.

Not tried the Studio Driver 591.44 version.

AndyW

Comments

Manfred-von-Erlangen wrote on 12/5/2025, 8:16 AM

Hi @all,

I just successfully exported a 25-minute clip in AV1 with ProX17 using the active hardware encoding and the installed Nvidia graphics driver 591.44 Studio on my Windows 11 PC. Therefore, I think this driver should be fine, and the blanket warning in the title of this thread doesn't seem entirely accurate.

Just my 2 cents,
Manfred

johnebaker wrote on 12/5/2025, 8:52 AM

@me_again

Hi Andy

Which export format/preset are you exporting to/with?

John EB

me_again wrote on 12/5/2025, 9:06 AM

@Manfred-von-Erlangen

I haven't tried the Studio driver version. It works for you but I'm not going to risk it. I did mention in the original post I'd not tried the studio drivers.

@johnebaker

HEVC, H264, AV1 various presets for each.

There is a lot of adverse comments on the Nvidia forum regarding the game version of 591.44 with games being slower and black screens etc. It appears from @Manfred-von-Erlangen's comment that the studio drivers work in Pro X17.

All I know is it doesn't work in my MS 2025, hence the topic title starting with the word BEWARE and is therefore accurate.

I'm not saying don't use it.

AndyW

me_again wrote on 12/5/2025, 10:10 AM

@Manfred-von-Erlangen

When your 25 minute was encoding, did the window actually say hardware encoding?

Driver 591.44 encodes OK but the window does not mention hardware encoding just the "please update driver..."

Incidentally, I tried the Srudio Drivers in my MS 2025 and still no hardware encoding with my RTX 4060. Reverted back to 581.80 and all is well.

AndyW

Marc-Goder wrote on 12/5/2025, 11:51 AM

@me_again

Deine Warnung ist voll gerechtfertigt.

https://www.magix.info/de/forum/vpx-problem-mit-nvidia-studio-treiber-591-44-vom-4-12-25--1350833/

me_again wrote on 12/5/2025, 1:22 PM

@Marc-Goder

Thank you for confirming

AnsyW

CubeAce wrote on 12/5/2025, 3:52 PM

@me_again @Marc-Goder @johnebaker @Manfred-von-Erlangen

I don't know about the latest driver but the one before kept crashing my photo editing package and had to roll back to the previous one before that. Still on that one.

Ray.

me_again wrote on 12/7/2025, 9:24 AM

NVIDIA Issues with driver version 591.44 ...

"NVIDIA released a new driver version on December 4th 2025 (591.44) which breaks hardware encoding on all NVIDIA cards. We recommend downgrading to version 581.80 or older. While going through the NVIDIA driver page, expand the 'View More Versions' list at the bottom rather than selecting the latest driver."

AndyW

johnebaker wrote on 12/7/2025, 12:00 PM

@me_again, @Manfred-von-Erlangen, @CubeAce

Andy thanks for the confirmation, luckily I was 2 versions behind.

Was a good one from Nvidia, with all GeForce cards affected, the issue is with HEVC/h.265 and AVC/h.264 encoding only, AV1 is unaffected by this problem.

John EB

vdl-user-v19 wrote on 12/7/2025, 12:45 PM

Don't you think the problem is an implementation issue at Magix? Perhaps no adjustments were made there?

Other video editing programs, Vegas Pro 23, and FFmpeg-based converters work with the new Nvidia driver.

Magix's Video Pro X, Video deluxe, Photostory and Vegas Pro up to version 22 appear to be affected...

https://us.download.nvidia.com/Windows/591.44/591.44-win10-win11-nsd-release-notes.pdf

2.6 Discontinued Support

Applications compiled using older presets and older rate control modes are supported by the drivers up until now. R580 will be the last driver branch to have this support.

Starting with the R590 branch, driver support for these older NVENC presets and rate control modes will be removed. Therefore, all applications compiled with older presets and rate control modes will stop working if upgraded to R590 branch drivers (59x.xx). Users need to upgrade to Video Codec SDK version 10.0 or above and use the new presets and rate control modes. Users can refer to the migration guide present in Video Codec SDK for migrating to newer presets and rate control modes.

Release 470 was the last driver branch to support Quadro desktop GPUs based on the Kepler architecture.

NvIFR OpenGL support.

Release 470 was the last driver branch to support this functionality. NvIFR header files, samples and documentation have been removed from the NVIDIA Capture SDK 7.1.9 release. Future drivers will remove NvIFR.dll and any other reference to NvIFR. For details, see the NVIDIA Video Codec SDK page.

https://developer.nvidia.com/video-codec-sdk

https://docs.nvidia.com/video-technologies/video-codec-sdk/12.1/nvenc-preset-migration-guide/index.html

Manfred-von-Erlangen wrote on 12/7/2025, 4:29 PM

@Manfred-von-Erlangen

When your 25 minute was encoding, did the window actually say hardware encoding?

Driver 591.44 encodes OK but the window does not mention hardware encoding just the "please update driver..."

Incidentally, I tried the Srudio Drivers in my MS 2025 and still no hardware encoding with my RTX 4060. Reverted back to 581.80 and all is well.

AndyW

Just started another test using AV1, please see screenshots:

Manfred-von-Erlangen wrote on 12/7/2025, 4:53 PM

Export AV1 successfully finished. 👍

Just started another test using HEVC, please see screenshots:

So I can confirm that hardware encoding works well with AV1, but does not work with HEVC.

Manfred-von-Erlangen wrote on 12/7/2025, 5:54 PM

Just started and meanwhile successfully finished another test using HEVC after changing from 591.44 Studio to former 581.80 Game Ready, please see screenshots:

I can now confirm the original post by @me_again and observations already made by several users. The latest version 591.44 (Studio in my case) does not work 100% with HEVC, although it can handle AV1 without any problems. Both codecs can be handled without any issues while using the former driver 581.80 (Game Ready).

CubeAce wrote on 12/8/2025, 12:41 AM

@Marc-Goder @johnebaker @vdl-user-v19 @me_again

I wonder if this has anything to do with Nvidia not liking HEVC charging fees while AV1 is a free alternative / replacement?

me_again wrote on 12/8/2025, 12:59 AM

@CubeAce

Greetings Ray,

I don't think so. I couldnt even get AV1 to hardware encode in MS2025.

There are many example of hardware encoding being broken with 591.44, mostly from gamers I must admit.

An example from the Adobe Community - https://community.adobe.com/t5/after-effects-bugs/my-hardware-encoding-has-been-disabled/idi-p/15621268

Interestingly, while the driver 591.44 was still installed, some web pages (and documents) scrolled with what I can only describe as tearing.

After reinstalling driver 581.80 (both as overwriting and clean install) this didn't disappear completely so I did a complete system restore (I try to remember to set a restore point before most major drive changes) and the tearing has gone.

AndyW

johnebaker wrote on 12/8/2025, 2:20 AM

@vdl-user-v19, @CubeAce, @me_again

I agree with Andy this is more than just an issue with Magix software, there a reports of different video editors also being affected in different ways, and simple video playback issues where the player is set to use hardware acceleration.

This appears to be a 'something broke' driver vs hardware issue rather than presets and licensing.

John EB

CubeAce wrote on 12/8/2025, 3:50 AM

@me_again @johnebaker @Marc-Goder @Manfred-von-Erlangen @vdl-user-v19

Hi Andy.

In my photo editing app, the last two drivers crash the program whenever AI masks are used that use hardware acceleration but nothing else had been affected. The developers had asked users to roll back at least two drivers and that was before the latest driver came out.

I'm not capable of following all of the pdf posted above but it looks to me like program developers are also going to have to do some work.

Ray.

vdl-user-v19 wrote on 12/8/2025, 7:17 AM

This appears to be a 'something broke' driver vs hardware issue rather than presets and licensing.

Well, it's possible.
Here's an excerpt from a corresponding videodeluxe.log file.
This also reinforced my assumption that it might have something to do with the presets or encoder parameters.

2025/12/07 21:24:23 [INFO]    [_Common]: Export Segments:
                                  1:    00:00:00 to 01:30:00 len=01:30:00 mode=VidStream
2025/12/07 21:24:23 [FATAL]   [MPEGIntel]: VideoEncoderBase::Initialize: CreateEncoder failed with DP4 errno=0x0410057C: Error 1404: error init encoder parameters(fall back to SW encoding)
2025/12/07 21:24:23 [FATAL]   [MPEGIntel]: VideoEncoderBase::Initialize: CreateEncoder failed with DP4 errno=0x0410057C: Error 1404: error init encoder parameters(fall back to SW encoding)
2025/12/07 21:24:23 [INFO]    [_Common]: Export with ImportDevice("NVIDIA GeForce RTX 2060"); EngineDevice("NVIDIA GeForce RTX 2060"); and ExportDevice("CPU" - fallback for "NVIDIA GeForce RTX 2060") rendering to C:\Users\-\Desktop\2025-12-07.mp4 started (MxMpeg4Intel|1920x1080p|1.77778|25 FPS|22000 kbit/s||2 CHN|48000 Hz|160 kbit/s)
2025/12/07 21:24:23 [INFO]    [_Common]: Export with ImportDevice("NVIDIA GeForce RTX 2060"); EngineDevice("NVIDIA GeForce RTX 2060"); and ExportDevice("CPU" - fallback for "NVIDIA GeForce RTX 2060") rendering to C:\Users\-\Desktop\2025-12-07.mp4 started (MxMpeg4Intel|1920x1080p|1.77778|25 FPS|22000 kbit/s||2 CHN|48000 Hz|160 kbit/s)
2025/12/07 21:24:39 [FATAL]   [Export - Engine]: Bounce: GetLastError(122): Der an einen Systemaufruf übergebene Datenbereich ist zu klein.