DasBoeseC

Hi everyone, the support ticket I opened regarding this issue was closed with the following reply by Line 6: Which to me does not sound as if Line 6 are actively working on a solution...they are instead "monitoring the issue". I think I'll try to get rid of any Line 6 stuff on my machine then...

I have a feeling that 60/70% of all drivers might be a tad exaggerated (remember there is a TON of drivers required just to make your machine boot up in the first place ;-) ), but again...I see where you are coming from and of course the smaller the manufacturer (or more exotic the hardware) the harder it is to play constant catch-up with changes that are required. (What surprises me is that there are drivers for Windows 11 released for the hardware you use at all...) The only thing that I disagree with is the constant and almost automatic "Microsoft-bashing" that I see so often...not to say they don't deserve it at times, but as I work in IT I often come across people that are used to simply blame Microsoft for anything. ...and as I previously wrote...I am myself pretty relaxed regarding this specific situation as the only thing that happened for most of us is that a "deficiency" of the driver, that always was there, has now been flagged and made visual. The biggest issue might be that Microsoft will probably make CIMI mandatory at some point and it looks like they are starting to force the issue as it seems you cannot simply deactivate CIMI on newer Surfaces anymore. @MarcalLooking at this thread it may help to directly get in touch with Microsoft: Can't disable Core Isolation Memory Integrity - Microsoft Community

Well, I see where you are coming from, but I would disagree...I know that Microsoft isn't always great and did lots, and lots of weird things in the past, but that does not mean it's always at fault. Just because a legacy driver was not flagged as incompliant for some time, does not mean it does not become incompliant when the grace period has expired. Core isolation has been around for quite some time and is a security feature that absolutely makes sense. If Line 6 decided that a machine running their software cannot have core isolation activated, because the software needs direct access to hardware resources or the performance impact is too big, it's their job to clearly state this so the users are aware (...it will also cause issue with newer machines that have CIMI turned on by default). At least on my machine the only drivers that are NOT compatible with Core Isolation Memory Integrity are the ones from Line 6...is that different for you? ...so, at least from my point of view, the responsibility to solve this issue lies with Line 6.

Hi everyone :) thanks for the exchange...I found it to be very helpful. To sum it up there actually is (let's say) "room for improvement" on Line 6's side regarding their drivers and that just became visible by this Windows 11 update. Besides that nothing bad happened and this is neither a reason to hold back on Windows 11 - as the "room for improvement" is the same on Windows 10...it's just not visible - nor to get uptight about Line 6 - as they are already working on the issue and will themselves be interested in solving it. Always remember...every software has bugs...always ;) CU Sebastian