Windows 11 ,.. are we ready IRL ?

[HM]

Just got a new Acer 8-Core laptop

MS own test-software is claiming it "ready", but I am not yet invited for an default upgrade

Would like to either start up on a fresh W11 ,.. or just continue on W10 longest possible

No "in betweens" I am not fund of making images and set op roll-backs and such


My 3 main-programs ,.. S1, Affinity, and Resolve,.. already Resolve is known to have issues

Hundreds of harware and software ,.. but already IK seems to not support W11 officially

(I bought heavy into all IK under the big sale ,.. and would like to use all)

Tons of other stuff as well ,.. dont even have the time to investigate all

I can wait max 2-3 weeks

1. Do I wait ?

2. Or just start up and continue with W10 long as possible ?

[pljones]

Maybe we need a sticky "Is Windows 11 ready for Audio?" covering various use cases, such as clean install, upgrade, production and recording use, real-time tuning, performance... My one PC that's capable has been offered the update but I refused it for now, as I've no idea if it's going ... distress ... my current install.

[Keith99]

I got it and had awful spikes in Cubase until I updated my Babyface drivers and ticked a box on the driver panel, oh and reenabled the steinberg power scheme - now all is well apart from Sonarworks plugin that is not yuet Windows 11 ready (they say it will be by February).

[Jafo]

Bleeding edge is for hobbyists and maniacs -- people who either have the time to experiment, or who are being paid to experiment or fix. An OS that won't let you use software you just bought sounds like a bad idea.

[HM]

Thanks for the answers ,..

I guess they pretty much sums up that we are maybe like 6 mounths to early at least

And I am sure that not only Resolve and IK might course me pain ,..

There is 100's more vendors and plugs that needs to be OK ,.. hardware drivers as well

Even plugs that claim to be W11 compatible might show out to be flakey IRL

Guess I will have to drop W11 ,..

At least W10 should be officially supported until 2025 and likely usable a few years more

[kritikon]

I thought (could be wrong) that Cubase12 was all about being Win11 compatible? In which case I'm def not going for Win11 until my DAW will definitely work with it (Steinberg specifically said that Cubase currently is not Win11 compatible IIRC). My laptop is apparently compatible, the home desktop not. Either way, if it's going to screw Cubase, then I won't get it. Eventually of course...we all will at some point.

[HM]

Yes, and like said:

Have to take into account also that some things might be claimed ready, but show out not to be

Just from 5 minuttes look I see both a main program, and a main plug vendor lacking

But my list is long:

Presonus, Steinberg, Davinci, Waves, UAD, NI, IK, D16, TC, PSP, SSL, AAS, Eventide, Nomad, P&M,
Softube, Emu, Novation, Roland, Lexicon, Relab, UVI, Arturia, McDSP, Digital Sound Factory,
Tokyo Dawn, Kush, FabFilter, Melda, Audio Thing, United Plugin, Apulsoft, Brainworx, Maag, DS,
Knif, Magix, Rob Papen, East West, Audiority, Overloud, Audio Damage, Izotope, Sonivox, AIR,...

Just to mention what I remember right now ,.. many of them the hole collections

Most likely at least a dusin of plugs might show up to be useless ,.. some of them maybe for good

[chk071]

Bleeding edge is for hobbyists and maniacs

Tell that to all the people always whining for M1 native plugins.

Regarding the topic: Windows 11 was audio ready from day one, just like any other Windows. Windows 11 is basically a Windows 10 with a facelift anyway. If there are issues with certain plugins or software, it's a matter of the developers of that software to make it Windows 11 compatible. Although I really wonder why it would fail to be. Guess it's trifles.

[HM]

Sure

I am fully aware that, lets say, f.eks 80 pct will likely work OK

But even vendors like UAD, that got a hole team to correct things, did fail several W-upgrades AFAIR

So potential problems will remain in the the last 20 pct

There is no way, today and tomorrow, in a reasonable amount of time, to get a hold on even if some
of you essential plugs will fail, and to consider if you will run the russian roulette in general

I just sit here with my new laptop ,.. and need to get started ,.. damm

But guess decision is made by now, contiuing with W10 is not that much of a problem anyway

Thanks for all contributions

[pljones]

Regarding the topic: Windows 11 was audio ready from day one, just like any other Windows. Windows 11 is basically a Windows 10 with a facelift anyway. If there are issues with certain plugins or software, it's a matter of the developers of that software to make it Windows 11 compatible. Although I really wonder why it would fail to be. Guess it's trifles.

As HM and others point out, it's not that easy. Developers all over are telling us they're not ready for Windows 11. So what do they mean? If your existing set up does break, you're 100% out of luck and stuck once you've upgraded. Getting back to a working Windows 10 after a Windows 11 upgrade is likely to be ... not a lot of fun.

[starflakeprj]

As HM and others point out, it's not that easy. Developers all over are telling us they're not ready for Windows 11. So what do they mean? If your existing set up does break, you're 100% out of luck and stuck once you've upgraded. Getting back to a working Windows 10 after a Windows 11 upgrade is likely to be ... not a lot of fun.

The developers are just saying "they are not ready" because they haven't tested their plugins thoroughly, but I have close to a thousand plugins, and I have yet to find a plugin that doesn't work with Windows 11.

[pljones]

The developers are just saying "they are not ready" because they haven't tested their plugins thoroughly, but I have close to a thousand plugins, and I have yet to find a plugin that doesn't work with Windows 11.

Good that you're in a position to test. Would you have a table of those tests?

[chk071]

As HM and others point out, it's not that easy. Developers all over are telling us they're not ready for Windows 11. So what do they mean? If your existing set up does break, you're 100% out of luck and stuck once you've upgraded. Getting back to a working Windows 10 after a Windows 11 upgrade is likely to be ... not a lot of fun.

The developers are just saying "they are not ready" because they haven't tested their plugins thoroughly, but I have close to a thousand plugins, and I have yet to find a plugin that doesn't work with Windows 11.

That's what I thought. Thanks for confirmation.

[starflakeprj]

The developers are just saying "they are not ready" because they haven't tested their plugins thoroughly, but I have close to a thousand plugins, and I have yet to find a plugin that doesn't work with Windows 11.

Good that you're in a position to test. Would you have a table of those tests?

No, sorry, I don't see any reason why I should spend time creating such a "test protocol". As chk071 mentioned, Windows 11 is more or less just Windows 10 with a facelift. I had one problem when updating from Windows 10 to Windows 11, and it was with Steinberg's eLicenser, and even the eLicenser debug tool identified Windows 11 as Windows 10. The problem I had I would probably have gotten with with a half year Windows 10 update too, as it seemed like my computer was just identified as a new computer. An uninstallation and a reinstallation helped my problem, while Steinberg support refused to help me because I had Windows 11 installed, and they did not support Windows 11 officially yet (not enough testing from their side).

[pljones]

I had one problem when updating from Windows 10 to Windows 11, and it was with Steinberg's eLicenser, ...

Thanks - it's details like this that will help others make informed decisions.