Error List does not store/save Error information from the recently closed files in newer versions of Visual Studio.

#84807Openvsfeedback 创建于 14 天前

_This issue has been moved from [a ticket on Developer Community](https://developercommunity.visualstudio.com/t/Error-List-does-not-storesave-Error-inf/11105221)._ --- [severity:I'm unable to use this version] [regression] [worked-in:2022 17.6.0] Extreme regression of Error List in modern versions of Visual Studio. Hi, I've been a long time user of visual studio community, I am an indie game developer working on multiple projects, the project sizes are large in size and contain multiple systems that were not written by me, they come from the Asset Store. Recently, I had upgraded to Visual Studio Community 2026, and I found an extreme regression of the way the Error List behaves. I've tried quite literally everything to troubleshoot with what I could find online. I even consulted Copilot, and was gaslit for 3 days with the same solutions over and over again. I've dug through the web, and it seems like I am the only person with this issue, somehow. I hope that whoever has the same problem will discover this thread and maybe if it gets resolved they'll be able to resolve it as well. I've tried removing the cache, re-attaching the project to the Unity project, regenerating the solution multiple times, reinstalling unity, reinstalling visual studio, and the same problem keeps happening over and over again. But it doesn't happen on the old version of Visual Studio, which is not even available to be downloaded normally anymore. In any case, here's the problem: On older versions (That I had to dig up, because the latest version of 2022 is also broken!) it functions as expected, you open a file. If you make an error in a file and close it, it remembers it, and throws an error. In current versions, it doesn't behave this way. If you close the file, the error disappears completely, not memorized by Visual Studio, and only re-appears after doing code error analysis in the FULL SOLUTION. **As you can guess, this takes 30 seconds each time you make an error, or need a global change.** Like, let's say you changed a variable name, and another script tries to reference it. But it doesn't throw you an error, so you can't even go to it quickly until you wait like 30 seconds every single time. I am extremely frustrated, I don't know what to do anymore. All I can do is use that old version because otherwise I literally can't code it as it makes finding errors and bugs very difficult without tabbing in and out of Unity editor to grab errors from there. Please let me know if there's some unusual hidden settings or whatever that I can adjust. Thanks. **I've attached the video of the behavior I am talking about below.** This is from 2022. (Instant!) [2022.mp4](https://aka.ms/dc/file?name=B9753a0584efe46298df46303ebf49828639167118254770609_2022.mp4&tid=9753a0584efe46298df46303ebf49828639167118254770609) This is current version 2026. [2026_EXTREME_Regression.mp4](https://aka.ms/dc/file?name=Ba0773d78325b47dd80f62051217e1693639167118331785280_2026_EXTREME_Regression.mp4&tid=a0773d78325b47dd80f62051217e1693639167118331785280) Additional notes from the suggested AI Feedback: - Version where it functioned correctly - 2022 17.6.0 - Version where it does NOT function correctly - 2026 18.7.0 - This happens across ANY solution I run/use on every Unity version I run. - It is 100% reproducible on my end every time. - Video Recording of the issue was attached here via the uploads. --- ### Original Comments #### Feedback Bot on 6/10/2026, 11:54 PM: Based on similar issues resolved with Microsoft in the last 6 months, the following can help resolve this issue faster. <h2>If not already included, please provide:</h2> Detected: Product: vs-xsetup.4.7.25.22189, category: dotnet; Customer reports Visual Studio 2026 / 2022 regression in Error List behavior with Unity solutions, where closed-file diagnostics disappear until full-solution analysis runs. Please provide: <ul> <li>The exact Visual Studio version/build (Help > About) for both the working older version and the broken 2026/2022 version.</li> <li>Whether this happens with one specific Unity solution or multiple Unity solutions, and whether it reproduces in a brand-new simple solution.</li> <li>The exact repro steps from opening the solution to closing the file and observing Error List behavior.</li> <li>Whether the issue happens every time or only intermittently.</li> <li>A short Visual Studio Feedback Tool recording (~30 seconds) while reproducing the issue, since no diagnostic trace/dump was attached.</li> </ul> #### Kirill G on 6/11/2026, 00:07 AM: Hello bot, The following information was already provided in the ticket. Just in case, I will duplicate it so the ticket wont be automatically closed. -Version where it functioned correctly - 2022 17.6.0 -Version where it does NOT function correctly - 2026 18.7.0 -This happens across ANY solution I run/use on every Unity version I run. -It is 100% reproducible on my end every time. -Video Recording of the issue was attached here via the uploads. <a target='_blank' href="https://aka.ms/dc/file?name=B8504478ac06b4236b8f6a0bed39b8b1e639167132231126461_2022.mp4&tid=8504478ac06b4236b8f6a0bed39b8b1e639167132231126461">2022.mp4</a> <a target='_blank' href="https://aka.ms/dc/file?name=Bf622f8fc7d1a446f912523c136e818c3639167132396477219_2026_EXTREME_Regression.mp4&tid=f622f8fc7d1a446f912523c136e818c3639167132396477219">2026_EXTREME_Regression.mp4</a> Reproduction steps: Open a large project with multiple .csproj files, and this happens. In case you might assume my computer is slow, it is not. Ryzen 3900xt, 64gb of RAM, the project and visual studio are installed on NVME SSD. Thanks again. #### Feedback Bot on 6/24/2026, 07:32 AM: We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps. #### Sebastien Lebreton [MSFT] on 6/24/2026, 06:28 PM: Hello, From my understanding, this is a matter of how your workspace analysis is setup. Go to <code>Tools/Options</code>. Then to the <code>All Settings/Languages/C#/Advanced</code> section. Click on the <code>Advanced</code> link. Have a look at <code>Run background code analysis</code> and <code>Show compiler errors and warnings</code> settings. I guess it was <code>Open documents</code> for 2026, and <code>Entire solution</code> for 2022. Could you confirm settings used for both? Switching to <code>Entire solution</code> should solve your issue. Regards #### Kirill G on 6/24/2026, 09:56 PM: Hello Sebastien, I believe I’ve described my issue well, and I did mention what you just described, as I did try this solution before creating this ticket. As I mentioned before, I was looking for every possible solution I could for 3 days before deciding to create a ticket as literally none of the solutions provided worked. I’d like to quote my own post, **In current versions, it doesn’t behave this way. If you close the file, the error disappears completely, not memorized by Visual Studio, and only re-appears after doing code error analysis in the FULL SOLUTION. As you can guess, this takes 30 seconds each time you make an error, or need a global change.** I’d like to specify here, it takes 30 seconds because it tries to re-cache the entire thing, it happens very quickly on small projects/solutions, yes. But on a big one, this happens every single time. The setting you mentioned is is enabled in 2022 and it behaves very differently to 2026. Please see a screenshot from 2022.: <img src="https://aka.ms/dc/image?name=B3a08be0b59274ca1988610c5dbf19e8d639179152343915247_devenv_DYjY594yy7.png&tid=3a08be0b59274ca1988610c5dbf19e8d639179152343915247" alt="devenv_DYjY594yy7.png"> And screenshot from 2026: <img src="https://aka.ms/dc/image?name=B49bc37be9c81407eb7556fed43402ace639179152443171627_devenv_A0oZr6WBPf.png&tid=49bc37be9c81407eb7556fed43402ace639179152443171627" alt="devenv_A0oZr6WBPf.png"> In 2022 (not the latest version, the version i’ve described in the ticket.), if you open a file, make an error, save it and close it, the error list will keep an error. In 2026 or the latest versions of 2022, if you do the same and close the file, the errors disappear and it tries to recache the entire solution. This seemingly seems to happen every time a file is closed. I think there must have been some sort of change to the way the caching behaved in the latest versions. Perhaps it is trying to cache the entire solution instead of just parts of the .csproj? Logically it would make sense, in Unity projects you usually have your own csproj of your entire game, and then you could have multiple other csproj via assembly definitions, as a lot of asset store plugins tend to do instead of baking all of their code into a .dll. I don’t know, all I know the settings are the same, and on the latest versions it behaves this way… Waiting 30 seconds for it to recache the whole thing is an incredible waste of time, and that’s a shame because it really did work great before. #### Sebastien Lebreton [MSFT] on 6/25/2026, 08:26 PM: This ticket was routed to the Visual Studio for Unity team (given you are using Unity projects), but I’m not sure this is really linked to the Unity scenario. Could you try to remove the Managed Game/Unity workload from your VS installation, and check if you are able to reproduce ? In the affirmative, I will reroute to the proper team. I also spotted a similar issue here: <a target='_blank' href="https://developercommunity.visualstudio.com/t/Visual-Studio-2026-Only-Displays-Errors-/11019156">https://developercommunity.visualstudio.com/t/Visual-Studio-2026-Only-Displays-Errors-/11019156</a> Routing to: <a target='_blank' href="https://github.com/dotnet/roslyn/issues/81926">https://github.com/dotnet/roslyn/issues/81926</a> #### Kirill G on 6/26/2026, 10:18 AM: Hi again, I’ve downloaded a random project from github as I don’t have any other projects outside of Unity. For example, I git cloned <a target='_blank' href="https://github.com/SciSharp/LLamaSharp">https://github.com/SciSharp/LLamaSharp</a> into a folder, opened it with Visual Studio 2026. Did the same steps as I reported in the ticket, Make an error > Close file > It disappears and needs a few seconds to be found again by the project. Unlike it remaining in the Error List in the old version of Visual Studio. Granted here it doesn’t take as long to find it because it’s a small-scale project compared to the bloated Unity solution, so I do believe that project size does matter in this case. I believe that might confirm that this is not a Unity Tools specific issue but a problem in Visual Studio itself. #### Sebastien Lebreton [MSFT] on 6/26/2026, 07:57 PM: I agree, I’m routing to the proper team. Thank you for confirming. Regards #### Feedback Bot on 6/26/2026, 07:57 PM: We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps. #### Muhammad Nabil Fikri Adenan (Centific Technologies Inc) [MSFT] on 7/16/2026, 08:32 AM: Thanks for your sharing the detail steps, I can reproduce this issue through your shared steps and this issue has been escalated for further investigation, if there is any process, I will inform you immediately.

1 条评论