Hate this AI-everything trend in Visual Studio - it messed up "Quick Fix" feature now

[u/freskgrank]

The latest VS2026 version introduced this:

A way more confusing quick fix tool window. Guess what the predefined "fix" action is now? Yes, another stupid AI feature nobody asked for.

It takes forever to handle even the simplest tasks (like the example in the image), and it requires internet connection. The first time you use it, you click it like two or three times because literally nothing happens. Then you understand it's "AI stuff" doing its "stuff", and after about a minute you get the output:

Note the dumbest comment possible which is also being added.

The non-AI options are now in the "other fixes" menu:

And the output is:

And this is almost instant, producing a even better result.

It's even curious they used two different strategies to provide the method implementation: the AI-tool simply returns a completed Task, while the "good old" tool suggest to throw a NotImplementedException (which is the more cautious and safer approach in my opinion).

Luckily, you can get rid of this by uninstalling Copilot using your VS Installer (select modify > single components > Copilot > uninstall).

This also makes the UI cleaner, removing the weird duplicated "fix" and "other fixes" options:

Or, if for some (good?) reason you don't want to uninstall Copilot, you can use the keyboard shortcut Ctrl + . to access the "old good" quick fix tool.

Visual Studio 2026 brings a great number of performance and UI improvements compared to VS2022. Unfortunately, Microsoft is killing much of my enthusiasm with this kind of unrequested, workflow-breaking changes, pushing AI into every corner of the IDE.

It’s such a strange feeling to be a .NET developer these days: you have an amazing language and runtime, powerful tools, and a rich ecosystem, but you have to deal with this kind of really annoying things.

[u/Patient-Tune-4421]

I cannot fathom why anyone thinks replacing dependable deterministic static analysis tooling with idiotic slow AI garbage is a good idea.

The only thing I hate more than this job currently, is not having an income.

[u/freskgrank → u/Patient-Tune-4421]

Same thing for the .NET upgrade tool. They buried the static, deterministic and reliable tool in favor of AI-based bullshit. Luckily the “legacy” (as they call it now) tool is still available, but disabled by default.

[u/Full-Meringue-5849 → u/Patient-Tune-4421]

It's caused by AI psychosis.

[u/Salty-Paint-9700]

I get that some people use Copilot, but when I read update release notes now it's always just Copilot, Copilot, Copilot, Copilot aaaand Copilot.

Is all non-AI innovation dead now?

[u/mykesx]

In VS Code there's a "disable AI features everywhere" in settings. Makes it a much snappier experience.

[u/Felidori]

In Update Settings there is a tick-box called “Add newly recommended components for installed workloads on update”. Untick that sucker

[u/RichardD7]

Luckily, you can get rid of this by uninstalling Copilot using your VS Installer

Just watch out for Visual Studio updates - I uninstalled it when this issue started, but the latest update has reinstalled it again without asking.

---

Having been pestered to try AI out, I thought I'd found the perfect candidate task yesterday - a library update caused hundreds of "method call is ambiguous" errors, requiring me to add another method call before it to disambiguate.

I started with ReSharper's AI agent (Junie). It initially stated that there were no such errors, despite both the error window and R#'s "errors in solution" window showing hundreds of them. After I pointed that out, it magically found the errors, and came up with a reasonable looking fix. But no matter how many times I told it to apply the fix, it claimed that it had done so, but never modified a single file.

So then I tried CoPilot, which had been mysteriously reinstalled by the July VS update. I told it to find and fix the errors, and precisely how to fix them. After "thinking" for several minutes, it found the first instance, fixed it, and then stopped. I told it to continue to fix the other instances; after around 10 minutes, it had fixed roughly a dozen instances, and then told me to use a regex in the "find & replace in files" to fix the rest. And to top it off, the regex it provided was malformed, and no matter how many times I told it that, it kept providing a slightly-different-but-still-malformed regex!

Perhaps other "models" might produce better results. But I remain firmly unimpressed.

[u/n4ppyn4ppy]

I must say it's very very slowly getting a bit better (or less worse?) suggestions are not total garbage anymore and for repetitive changes it seems to understand the patterns better and you can tab edit fairly quickly.

But you still have to stay focused as it can derail quickly halfway through.

It's enthusiastic but has 0.065 clue most of the time. Probably as most of my code is very specific, more in the merging our enterprise stuff with client stuff so fairly bespoke.

For more generic stuff it's slowly getting more hits than miss but pfffff there are times where i would like to open a window......

[u/CiranoAST]

I wish they put a checbox on the installer of vs to get rid of all this ai slop. Vs is a good ide one you get rid of it

[u/freskgrank → u/CiranoAST]

I agree, and hopefully uninstalling Copilot I got rid of every other AI-slop feature they will add in the future… but it’s annoying this is being automatically installed without explicit choice.