26H update for AMD computers

Do not update your computer until February to end of March 2027

Disable -Switch to off and move the date as well and keep checking every three weeks at least to be sure. Get latest updates —OFF and keep moving pause update regularly.

Too may bugs and It Is not safe.. It can affect Focusrite sound interfaces as well.

Also make system Image of the whole computer

No headaches If you wait until Microsoft iron out all the bugs

I created topic and accidentally hit the wrong edit button called delete!! lol!!

I was just about to update next week, but I´ll wait for awhile. Thanks for the heads up.
Anything specific, what´s wrong with the update and does it cover all AMD processors?

Work all due respect, if you’re going to recommend users hold off on 4-5 month’s worth of updates, including security updates, then you really should provide at least links to some reasons for why we shouldn’t update.

It’s like the bare minimum.

@JohnS

What’s this about? Are you talking about Windows 11 26H2?

What specific issues are you seeing? What version of Windows did you upgrade from?

Pete
Microsoft

I just updated two AMD systems to 26H2 and they’re both working just fine.

System Specs:
AMD Ryzen 7 8745HS 32GB RAM w/ Radeon 780M Graphics
RME UCX audio interface
Windows 11 Pro | version 26H2
Cubase 14.0.31

Now I´m even more confused.. Maybe the OP could shed some light on this topic, otherwise I´m gonna bite the bullet and update.

I updated my AMD PC, no issues at all.

We all know windows can mess with AMD computers

Just google should i update to 26H yet for music composition and it saysa hold off to be safe until at least March . The are USB problems , Focusrite problems

Holding off on upgrading to Windows 11 version 26H2 is highly recommended for music production right now due to widespread, documented audio infrastructure bugs introduced in this code branch. [1, 2]

While the update introduces great quality-of-life adjustments like a customizable taskbar and better idle RAM management, it currently poses a significant risk to your Digital Audio Workstation (DAW) and hardware stability. [1, 2]

1. Breaking Legacy USB Audio Devices (Code 10 Errors)

The 26H2 branch introduced a critical bug that causes USB Audio Class 1.0 devices to fail entirely. [1, 2]

  • The Impact: If you rely on older or budget audio interfaces, USB microphones, or class-compliant MIDI hardware, Windows may fail to recognize them.
  • Symptoms: Volume sliders freezing at zero, unresponsive device manager panels, or your hardware throwing a "This device cannot start (Code 10)" error.
  • Note: Microsoft issued an out-of-band emergency patch (KB5129195) to address part of this, but many users with specific audio gear still report crackling and recognition issues. [1, 2, 3, 4]

2. The AC-3 Audio Decoder App Crashing Bug

A major issue shared across the 24H2, 25H2, and 26H2 code branches directly breaks Windows’ built-in Dolby Digital AC-3 audio decoding. [1, 2]

  • The Impact: When an application or plugin tries to initialize, decode AC-3 audio, or adjust volume via native Windows handlers, the application will crash abruptly or fail to launch entirely.
  • While most modern DAWs (like Ableton, Reaper, or Cubase) use proprietary audio engines or ASIO drivers rather than Windows’ stock decoder, any legacy tools, video editors, media players, or stock utilities in your studio workflow can trigger immediate system instability. [1, 2, 3]

3. Strict New Driver Security Rules

Version 26H2 implements much stricter driver trust and security enforcement. Windows will now block drivers that aren’t strictly validated through the Windows Hardware Compatibility Program (WHCP). For music producers using older, discontinued, or boutique audio interfaces and MIDI controllers that rely on legacy or community-patched drivers, the OS may completely block your hardware’s software from loading. [1, 2, 3]

4. Background “AI Fabric” Ram Consumption

The 26H2 update silently integrates the Windows AI Foundation Fabric Service (WSAI). By default, this service background-caches AI processes and can automatically eat up to 8GB of RAM unless manually disabled via the registry or system services. In large orchestrations or heavy sample-based projects (Kontakt, Omnisphere), losing 8GB of short-term memory to background OS bloat can severely bottleneck your DAW performance. [1]


What should you do?

If your current Windows machine is stable, pause updates immediately. 26H2 allows you to extend the update pause indefinitely. [1, 2]

If you want to check if your system is ready for a future update, I can help you look into:

  • Whether your specific audio interface model has 26H2-compatible ASIO drivers available.

  • The steps to permanently disable the heavy background AI processes if you do decide to update.

  • How to run LatencyMon to see if your current setup is suffering from audio drops. [1, 2, 3, 4]

IT IS BEST TO HOLD OFF BUT IF YOU RISK IT MAKE SURE YOU HAVE SYSTEM IMAGE TO FALL BACK ON>

Google It ,The AI will tell you. I am only trying to help as I do know what headaches you can get when things go tips up .Sorry for the spelling . I should have put a T in there

No harm In holding off to be 100%

I don’t know if I’ll update yet, but maybe we should wait for Pete to chime in on those before making sweeping statements like that.

Is that copied text from an AI reply?

Edit:

I guess it is AI.

I know this is going to sound confrontational, but please cut it out. AI is wrong so much of the time when it comes to technical issues that trusting it blindly is just dumb.

Here, I’ll spell it out for you:

You (AI?) write that “Holding off on upgrading to Windows 11 version 26H2 is highly recommended for music production right now due to widespread, documented audio infrastructure bugs introduced in this code branch. [1, 2]”

Ok, it specifically says “for music production” and “introduced in this code branch”.

Let’s click on the first link. What does it say? It says first of all that “The [glitch](Windows 11, version 26H2 known issues and notifications | Microsoft Learn) also affects Windows 11 25H2 and 24H2, which share the same code branch. It relates to decoding AC-3 (Dolby Digital) audio and can cause the application using the decoder to crash abruptly or fail to start at all.”

Who here uses Windows native AC-3 decoding *for music production"?

Then it says “To be clear, the AC-3 malfunction is not specific to Windows 11 26H2; the update preceded the release of the operating system’s latest version by a week.” So it was literally not “introduced in this code branch”. A straight up falsehood.

On top of that the article is about a month old and it’s been fixed according to what we can find when “googling” it.

Why should I bother reading anything more?

If you’re going to post AI crap then at least verify it first before posting.

@JohnS

  1. was an issue in Windows 11 24h2, 25h2, and above for devices with, as I recall, more than 5 audio endpoints on them, and using the USB Audio Class 1 driver. It doesn’t impact UAC2 devices, or any devices which use their own driver.

  2. was resolved earlier this month in KB5127648. “Please note that many modern applications do not use Windows for this type of encoding and therefore will not encounter this issue. The code component involved in this issue is most commonly used in legacy applications that still rely on Windows built-in audio decoding. Many modern applications using this legacy codec frequently include their own audio decoding components.”

  3. was introduced to Windows 11 24h2, 25h2, and above in April of this year. It’s not new to 26h2, and, and not specific to AMD. It blocks a signing from the Windows XP era that was only ever supposed to be temporary. Some companies never updated their drivers. It’s a big security hole, but if you want to go back to the way things were before, including that security hole, the FAQ for that rollout explains exactly what you need to do.

FWIW, I’ve found Google’s AI to be particularly negative when it comes to Windows. I’m not suggesting conspiracy there, but there does appear to be bias.

I appreciate you trying to help, but I would suggest checking with a second source before proclaiming on the forums.

Pete
Microsoft

I know what Microsoft updates can do In the early stages

Oh well, let the guinea pigs find out.

People have had trouble with focusrite drivers and Usb problems.

Ai helped me with air spikes In a mix .

I will of course give scan computers where i purchased my amd7600x a call to see if They had problems. I learnt from the last major update. Win updates can mess with amd

In what source does it say anything about “AMD”?

I have not seen a single problem with 26h2 on my AMD Ryzen 7 and 9 systems related to Cubase and audio or anything else for that matter

Did the update a few weeks ago everything is fine

26H2 has been working quite well for me, well minus the latest Nvidia driver update. Rolling back to the September driver solved some issues I was experiencing in Cubase. A lot of nice improvements in the recent releases, and utilizing CTT’s WinUtil to remove some things I don’t use has helped me clean up the things I don’t want.

Not to put too fine a point on it, but based on what exactly? I keep seeing a lot of “I believe it so it’s true” in here.

Folks in the forums keep blaming Windows updates, and while once in a while it actually is an update issue, time after time I’ve helped folks and found it was everything from some other software installed to bad USB cables to one device where the USB cable didn’t actually plug all the way in. Sometimes, people are honest and realize it wasn’t that. More often than not, they disappear afterwards (happens on Reddit all the time).

I appreciate you trying to help others, but throwing Windows under the bus without any real evidence helps no one. And, like I said, several of the things you brought up were existing changes, some going on 6 months now, in previous versions of the OS.

FWIW, AMD writes their own CPU and chipset drivers that we ship with Windows, just like Intel does, just like Qualcomm does.

Pete
Microsoft

“Never attribute to malice that which is adequately explained by stupidity.”
I think Gemini in many cases is just plain bad and the AI results in Google Search really need to be taken with a big grain of salt.

Yeah, but it seems it’s not just in here. Quite a significant amount of human beings on planet Earth seem to be operating this way. How else can you explain flat earthers for example? There are, of course, much bigger examples but I don’t want to drift into politics.