This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have read issues around Windows 11 24H2 which cause disruption /conflicts with GPU (eg NVidia) and iGPU (eg Intel Graphics)
I use both GPU's for Video and Photography processing for the Apps I have.
My iGPU is Enabled in BIOS and should not be disabled which it seems can happen with Windows 11 24H2. This is a step into the dark ages.
From evidence I see Windows 11 24H2 kills the iGPU
Has anyone else found this and what is Microsoft doing to fix it?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
MS is full of BS sometimes. Unless you pay them 1000$ a year for developer resources (which I do), you can't download older versions of Windows for which you have a license too. Apple I can download any version of macOS I want. This kind of business model needs to back fire as its totally anti-consumer and pro E-Waist for other reasons. MS should honestly be sued for this IMO.
24H2. January 28, 2025—KB5050094 (OS Build 26100.3037) Preview
Might be related... ? Hope they're starting to fix this buggy mess of 24H2...
Agree. . .
Windows should allow a roll back to 23H2 for those having problems. But they locked us out after upgrade to 24H2.
Having similar issues with ASUS ROG SCAR 18 (2023) with i9-13980HX + 4090 laptop.
Since I updated to Win11 24H2 in December I noticed crashes related to Intel iGPU drivers and NVidia drivers I NEVER experienced before with 23H2. Typical random login (silent) crash, logged by Reliability Monitor and Event Viewer, related to iGPU as emerged by WinDbg on the dump file:
I also sent an NVidia survey form reporting strange issues with Advanced Optimus MUX switch iGPU --> dGPU, sometimes failing and being stuck with freezed iGPU screen (instead of switching to the dGPU virtual display as it should), related to random dwm.exe crashes when this happens. Again, never happened with 23H2, before I updated to 24H2 in December.
In this case, one solution I found ATM seems to be to completely uninstall NVidia App.
NVidia recently informed me they've been able to reproduce this issue.... So we can confirm this 24H2 has serious problems with iGPU and dGPU video drivers.
Honestly 24H2 should have NEVER been released to the public since wasn't beta-tested enough and was still full of major bugs, causing conflicts with programs/games and drivers that were working perfectly fine up to 23H2.
Looks like Windows 11 24H2 has really messed up iGPU Quick Sync. Adobe still 'Investigating' with Intel on this issue - but I think there are two issues at play for Adobe customers (can't say for Resolve editors.
I have stuck with Win 11 23H2 and as mentioned above iGPU still OK for H265 but NOT H264. This is on Premiere Pro 25.1.
Version 25.0 is OK
Members of Adobe community reprt similar issues to your yourself that Win 11 24H2 adds another dimension to the mess - H265 not working either on Quick Sync
As you correctly report - we have total silence from Microsoft on this.
Intel appear to be a little bit more proactive but have not nailed any apparent issues on their drivers - so assume Intel are clean on this one.
I'm using xxx .6449 driver on my iGPU with Win 11 23H2 and it is OK for H265 and H264 on Premiere Pro 25.0
25.1 messes up H264.
I've raised a request on Microsoft (via their Feedback mechanism ) that when they introduce a new major release like Win 11 24H2 that they DO NOT remove the ability for a user to download thye previous version eg Win 11 23H2 from their website (Media Creator)
They remove it straight away which is a ridiculous thing to do until the new version is proved to be stable in the field for at least 6 months.
