# 26H update for AMD computers

**URL:** <https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772>\
**Category:** Cubase\
**Tags:** cubase-15\
**Created:** [November 1, 2026, 7:31pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772 "2026-11-01T19:31:26Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Googly\_Croft](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/googly_croft/32/409531_2.png) [@Googly\_Croft](https://forums.steinberg.net/u/Googly_Croft)\
**Post date:** [November 2, 2026, 11:42am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/21 "2026-11-02T11:42:52Z")

</div>

> [@Johnny\_Moneto](#):
>
> flat earth

Hey, if the Earth wasn’t flat we’d all slide off into that big ocean where there be dragons!  
😜  
More to the point, the “errors” listed above all seem to be “niche” kinds of errors, not the sort that many users would encounter anyways.

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://forums.steinberg.net/u/JohnS)\
**Post date:** [November 2, 2026, 3:02pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/22 "2026-11-02T15:02:48Z")

</div>

Oh well just tried to help .

Just for luck i rang Scan computers uk tech suport and they have heard of a few issues and advised me to hold off for a while yet, so it is not rumours. As I said let the Guinea pigs go first

---

<div class="post-metadata">

**Author:** ![JuergenP](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/juergenp/32/137487_2.png) [@JuergenP](https://forums.steinberg.net/u/JuergenP)\
**Post date:** [November 2, 2026, 4:37pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/23 "2026-11-02T16:37:30Z")

</div>

> [@JohnS](#):
>
> Just for luck i rang Scan computers uk tech suport and they have heard of a few issues and advised me to hold off for a while yet, so it is not rumours.

Sorry to say, but exactly this is just rumors. If they say “they have heard something” it has not a single piece of evidence in it. That’s what you’d simply call hearsay.

You started your initial posting directly with “Do Not Update”, instead simply post some experience here and lets discuss it with others.

Directly and unequivocally discouraging others doesn’t help anyone.

---

<div class="post-metadata">

**Author:** ![T-Cup](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/t-cup/32/415431_2.png) [@T-Cup](https://forums.steinberg.net/u/T-Cup)\
**Post date:** [November 2, 2026, 4:49pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/24 "2026-11-02T16:49:03Z")

</div>

My PC is an audio production one (Not even a year old) from Scan UK and so far no issues with regards to the update with what I have. 🤞

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://forums.steinberg.net/u/JohnS)\
**Post date:** [November 2, 2026, 7:10pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/25 "2026-11-02T19:10:58Z")

</div>

Have It your own way then , I’m out

From what I’m told from computer makers Hang fire

---

<div class="post-metadata">

**Author:** ![T-Cup](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/t-cup/32/415431_2.png) [@T-Cup](https://forums.steinberg.net/u/T-Cup)\
**Post date:** [November 2, 2026, 8:15pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/26 "2026-11-02T20:15:19Z")

</div>

> [@Googly\_Croft](#):
>
> Hey, if the Earth wasn’t flat we’d all slide off into that big ocean where there be dragons!

A couple of years ago I passed by a camper van with something like “Flat Earth Society” written on the side with info etc all over it. I thought it was a joke until I foolishly got talking to the owner. I had no idea people actually believed it 😱

---

<div class="post-metadata">

**Author:** ![Realist](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/realist/32/224_2.png) [@Realist](https://forums.steinberg.net/u/Realist)\
**Post date:** [November 2, 2026, 8:31pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/27 "2026-11-02T20:31:48Z")

</div>

No problems here with two AMD systems.  
It’s sad that users are now getting so unsettled by AI.  
It’s true, though, that there are occasional issues with Focusrite. But that’s Focusrite’s fault, not Windows 11’s.  
I had a short experience with the Focusrite Scarlett 18i20, but then I decided to spend a little more money and switched back to RME.  
RME’s drivers are simply rock solid.  
So I’m willing to pay a little extra money for that.

---

<div class="post-metadata">

**Author:** ![BrunoDSL](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/brunodsl/32/116134_2.png) [@BrunoDSL](https://forums.steinberg.net/u/BrunoDSL)\
**Post date:** [November 2, 2026, 8:40pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/28 "2026-11-02T20:40:38Z")

</div>

> [@MattiasNYC](#):
>
> In what source does it say _anything_ about “AMD”?

I believe this comes from when Windows had scheduling and affinity issues with high core count cpus like the AMD Threadripper 2990WX, which was the first consumer CPU with 32 cores/64 threads.

---

<div class="post-metadata">

**Author:** ![T-Cup](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/t-cup/32/415431_2.png) [@T-Cup](https://forums.steinberg.net/u/T-Cup)\
**Post date:** [November 2, 2026, 8:48pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/29 "2026-11-02T20:48:26Z")

</div>

> [@Realist](#):
>
> It’s true, though, that there are occasional issues with Focusrite. But that’s Focusrite’s fault, not Windows 11’s.

Agree. Had a Scarlett originally to be main audio device on a previous PC. The drivers kept messing up (Audio spikes etc) so had to buy a different device (and brand) and it’s never had trouble since. Worked fine on windows 10 and 11. The Focusrite wouldn’t save the control software settings either.

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://forums.steinberg.net/u/JohnS)\
**Post date:** [November 2, 2026, 10:35pm UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/30 "2026-11-02T22:35:28Z")

</div>

Focusrite 4i4 100% rock solid

---

<div class="post-metadata">

**Author:** ![MattiasNYC](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/mattiasnyc/32/83_2.png) [@MattiasNYC](https://forums.steinberg.net/u/MattiasNYC)\
**Post date:** [November 3, 2026, 12:08am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/31 "2026-11-03T00:08:11Z")

</div>

> [@BrunoDSL](#):
>
> I believe this comes from when Windows had scheduling and affinity issues with high core count cpus like the AMD Threadripper 2990WX, which was the first consumer CPU with 32 cores/64 threads.

The OP is stuck back in 2018?

---

<div class="post-metadata">

**Author:** ![Brian\_Roland](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@Brian\_Roland](https://forums.steinberg.net/u/Brian_Roland)\
**Post date:** [November 3, 2026, 12:19am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/32 "2026-11-03T00:19:16Z")

</div>

> [@JohnS](#):
>
> 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](https://learn.microsoft.com/en-us/windows/whats-new/whats-new-windows-11-version-26h2), [2](https://medium.com/@12264447666.williamashley/windows-11-25h2-what-music-makers-should-know-5695d74a34a0), [3](https://www.youtube.com/watch?v=Pz09hQdLTcI)]

Really?

This is what I’m running…

 ![image](https://europe1.discourse-cdn.com/steinberg/original/4X/0/6/4/064a26b794aa1b7d51b3a7f150e017196a24440c.png)

I have some unsigned drivers in play here, and they’re still working. I haven’t tried to install such drivers in a long time, but since taking updates they’re still working.  
 ![image](https://europe1.discourse-cdn.com/steinberg/original/4X/d/7/2/d7258674f68ce2c1ba58ca21527b699367278d5b.png)

 ![image](https://europe1.discourse-cdn.com/steinberg/original/4X/5/0/1/501380f6f19379f0d9a8b68ca0c3549e50d70496.png)

The main driver itself was signed once upon a time (only the highlighted RdCi1045.dll shows as unsigned), I believe, but I had to edit some of the files to get it to install from Windows 8 forward and that broke the ‘signing’ thinggy.

> [@Psychlist1972](#):
>
> I keep seeing a lot of “I believe it so it’s true” in here.

Is this true about unsigned drivers? I still need a few unsigned drivers. The devices do NOT seem to work with standard USB\<\>MIDI drivers. In my experience thus far it still works, better than ever. Just curious if there really are plans to totally block out unsigned drivers.

---

<div class="post-metadata">

**Author:** ![BrunoDSL](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/brunodsl/32/116134_2.png) [@BrunoDSL](https://forums.steinberg.net/u/BrunoDSL)\
**Post date:** [November 3, 2026, 12:31am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/33 "2026-11-03T00:31:33Z")

</div>

Out of curiosity, I’ve checked mine and I’m also running 26H2 pretty much since it was released and I had no issues with either my AMD CPU or AMD graphics card.

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/psychlist1972/32/236372_2.png) [@Psychlist1972](https://forums.steinberg.net/u/Psychlist1972)\
**Post date:** [November 3, 2026, 12:40am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/34 "2026-11-03T00:40:28Z")

</div>

> [@BrunoDSL](#):
>
> I believe this comes from when Windows had scheduling and affinity issues with high core count cpus like the AMD Threadripper 2990WX, which was the first consumer CPU with 32 cores/64 threads.

It always surprised me that AMD didn’t run across that in their testing prior to release.

It was not the core count, but the 4-NUMA node layout and it wasn’t handled as expected in Windows 10. This was like 8-9 years ago.

Windows 11’s core scheduler was updated to better handle processors with that kind of layout.

NUMA: [Non-uniform memory access - Wikipedia](https://en.wikipedia.org/wiki/Non-uniform_memory_access)

Pete  
Microsoft

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/psychlist1972/32/236372_2.png) [@Psychlist1972](https://forums.steinberg.net/u/Psychlist1972)\
**Post date:** [November 3, 2026, 12:47am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/35 "2026-11-03T00:47:02Z")

</div>

> [@Brian\_Roland](#):
>
> Is this true about unsigned drivers? I still need a few unsigned drivers. The devices do NOT seem to work with standard USB\<\>MIDI drivers. In my experience thus far it still works, better than ever. Just curious if there really are plans to totally block out unsigned drivers.

Unsigned kernel drivers always required you to boot into special mode in Windows to be able to run them. Same in Windows 10, 8, and 7 as I recall.

The issue likely being referred to is the switching off of allowing cross-signed drivers. That rolled out to all supported Windows 11 releases back in April via a EUFI boot policy. Cross-signing was a temporary signing mode to, as I recall, bridge between XP and Vista or maybe Vista and 7. It was never supposed to become permanent. After 2020, no new drivers could be submitted using that. As of 2026, most drivers using that, of which there aren’t all that many, no longer load.

It’s nothing about the driver, it’s the signing method which cannot be verified. We can’t know that a signing cert was kept safely by the driver author and wasn’t stolen or leaked and then used to sign malware. If you are a kernel driver, you can do just about anything, so trusted signing is incredibly important.

You can remove the policy and move back to the same policy as with Windows 10. It does open you up to the same possible exploits as those operating systems, however. Instructions for how to do so are in the FAQ for the policy, but you must remember to remove bitlocker from all your drives first. If you do not, and you use a local account and don’t have your recovery key, you end up with a brick. There is no way to restore from that. If you use a Microsoft Account, you can go online with your phone or another PC and get your bitlocker recovery code.

> **[The Windows Driver Policy | Microsoft Support](https://support.microsoft.com/en-us/windows/hardware/drivers/the-windows-driver-policy)**
>
> The Windows Driver Policy

Pete  
Microsoft

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/psychlist1972/32/236372_2.png) [@Psychlist1972](https://forums.steinberg.net/u/Psychlist1972)\
**Post date:** [November 3, 2026, 12:52am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/36 "2026-11-03T00:52:06Z")

</div>

Moving forward, we are heading to a place where no unsigned apps or drivers will, by default, run. You’ll have to jump through some hoops for that. It’s part of Baseline Security Mode for Windows.

But that’s also not specific to 26h2 or AMD.

> **[Strengthening Windows trust and security through User Transparency and Consent](https://blogs.windows.com/windowsexperience/2026/02/09/strengthening-windows-trust-and-security-through-user-transparency-and-consent/)**
>
> Today, Windows 11 powers over a billion devices and supports millions of apps across business, creativity, education, gaming and productivity. For decades, our commitment to openness and compatibility, in partnership with our global community of deve

You’ll also start seeing consent dialogs for Camera and Microphone\*, even for older Win32 apps.

\* any audio input, really, but security folks haven’t been interested in my pedantry there.

> With Windows Baseline Security Mode, Windows will move toward operating with runtime integrity safeguards enabled by default. These safeguards ensure that only properly signed apps, services and drivers are allowed to run, helping to protect the system from tampering or unauthorized changes. Users and IT administrators will still have the flexibility to override these safeguards for specific apps when needed. Developers can also check whether these protections are active and whether any exceptions have been granted — giving them insight and control over the conditions under which their apps run.

Pete  
Microsoft

---

<div class="post-metadata">

**Author:** ![Brian\_Roland](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@Brian\_Roland](https://forums.steinberg.net/u/Brian_Roland)\
**Post date:** [November 3, 2026, 12:53am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/37 "2026-11-03T00:53:50Z")

</div>

> [@Psychlist1972](#):
>
> You can remove the policy and move back to the same policy as with Windows 10.

Seems like in the past I disabled the policy long enough to get that USB driver up and running, then reenabled it. The device worked from then on. Looks like a single dll shows as unsigned, but all the .sys files that go with it show as signed.

I don’t use bit locker, and I believe I’m set up to run through a MS account. So I’m safe unless I wish to use bit locker?

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/psychlist1972/32/236372_2.png) [@Psychlist1972](https://forums.steinberg.net/u/Psychlist1972)\
**Post date:** [November 3, 2026, 1:00am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/38 "2026-11-03T01:00:16Z")

</div>

> [@Brian\_Roland](#):
>
> I don’t use bit locker, and I believe I’m set up to run through a MS account. So I’m safe unless I wish to use bit locker?

The note about bitlocker is only because you have to turn off secure boot long enough to remove the policy.

But this has nothing to do with unsigned drivers. It’s cross-signed only.

If your PC doesn’t load up with a red bar across the top and an unlocked padlock, then you’re not running with unsigned drivers enabled, and your Fantom DLL is likely some user mode driver component (I’m guessing) so I wouldn’t recommend changing anything.

You can’t just enable unsigned drivers once and have unsigned kernel drivers work from that point forward. It has to be set for every boot. I have a test PC with that on it.

(Aside: On the Taskkill.exe link on your desktop: in Windows Settings \> System \> Advanced you can just add “end task” to your taskbar jumplists)

 ![image](https://europe1.discourse-cdn.com/steinberg/original/4X/e/c/6/ec68f0cad0481b1ed23d3f6e57854662be70a7ef.jpeg)

Pete  
Microsoft

---

<div class="post-metadata">

**Author:** ![Brian\_Roland](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@Brian\_Roland](https://forums.steinberg.net/u/Brian_Roland)\
**Post date:** [November 3, 2026, 1:10am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/39 "2026-11-03T01:10:05Z")

</div>

> [@Psychlist1972](#):
>
> (Aside: On the Taskkill.exe link on your desktop: in Windows Settings \> System \> Advanced you can just add “end task” to your taskbar jumplists)

Thanks for the tip…

Yes, that was a short cut with a command line I built for something.  
C:\Windows\System32\taskkill.exe /f /fi “status eq not responding"

I’ve forgotten now what I’d made it for. Seems like it was to clean up after some app that’s since been fixed as to not need it anymore.

I think it was Band In A Box a few releases back. It’d leave stuff running after exiting the app (GUI and windows gone, but for whatever reasons it didn’t close itself out properly) that was just sitting there stealing memory. Double tap that and it’d clean up a bunch of lingering tasks in one go.

---

<div class="post-metadata">

**Author:** ![BrunoDSL](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/brunodsl/32/116134_2.png) [@BrunoDSL](https://forums.steinberg.net/u/BrunoDSL)\
**Post date:** [November 3, 2026, 1:16am UTC](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772/40 "2026-11-03T01:16:43Z")

</div>

> [@Psychlist1972](#):
>
> It always surprised me that AMD didn’t run across that in their testing prior to release.

At least in the videos AMD showed on YouTube at that time, the test rig was always some PC or laptop running Ubuntu.

[Previous page](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772.md?page=1)

[Next page](https://forums.steinberg.net/t/26h-update-for-amd-computers/1044772.md?page=3)
