Visual Studion 2022 Version 17.6 Hangs on Build\Clean\Rebuild All

samer.alisaleh 101

Hi,

I have upgraded my Visual Studio 2022 to the latest version 17.6.1. Since then when I try to Run\Build project it hangs and I cant do anything to cancel the build except by ending VS from task manager. Please help. This is critical and I cant continue my development.

Thanks

Pihlveus Michael 40 Reputation points

2023-06-08T13:23:45.4133333+00:00

Same problem with VS 17.6.2. I have deleted the files. And the problem still persists. I have to restart computer every time-
William 76 Reputation points

2023-06-13T13:54:23.2766667+00:00

I have a similar problem going from version 17.5.4 to 17.6.2

New computer running windows 11, installed VS 2022 community version 17.6.2 and tried to run solution generated in VS2022 community version 17.5.4 on a windows 10 computer. In debug, error generated on windows 11 computer but not on windows 10 computer.

Error;

System.InvalidOperationException: 'Cross-thread operation not valid: Control 'StatueBox' accessed from a thread other than the thread it was created on.'

Any possible reasons for the problem?
Robert Cieloszczyk 0 Reputation points

2023-07-31T14:12:22.5433333+00:00

The same with 17.5.4

I noticed, that the main output (EXE) from the app is hold by the System process (PID 4 on my machine) and can't be released without the reboot.

There is no problem with other projects (DLL) in the solution.

Björn Bengtsson 0

I have the same problem with VS 17.6.5, but it started sometime this spring. Don't know the exact version or date, because it happens randomly. The only way to temporarily resolve the problem is to restart Windows. Killing VS/MSBuild/dotnet-processes makes no difference.

But it might not be only Visual Studio. I get the same problem when I try to build the project with dotnet. But at least dotnet is hinting that it is a file copying problem:

❯ dotnet build <redacted>.csproj
MSBuild version 17.7.0+5785ed5c2 for .NET
  Determining projects to restore...
  Restored <redacted>.csproj (in 1,55 sec).
  Restored <redacted>.csproj (in 1,55 sec).
C:\Program Files\dotnet\sdk\8.0.100-preview.6.23330.14\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(314,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [<redacted>.csproj]
Attempting to cancel the build...
C:\Program Files\dotnet\sdk\8.0.100-preview.6.23330.14\Microsoft.Common.CurrentVersion.targets(4703,5): warning MSB4220: Waiting for the currently executing task "Copy" to cancel. [<redacted>.csproj]

The last line keeps repeating forever.

(I had the same problem with .NET 7 before I installed .NET 8 preview.)

Wong Kaiqi 0 Reputation points

2023-08-11T03:12:59.7833333+00:00

I started to have this problem when I upgrade my visual studio from version 17.6 to 17.7.

The issue disappeared after I force to close the program, but somehow it still hangs after several clean/ rebuild actions.
Andrea Catrini 0 Reputation points

2023-08-31T14:12:05.1733333+00:00

Same issue for me
Andy Martin 0 Reputation points

2026-04-24T13:51:46.0866667+00:00

I had a similar problem with VS2015 and none of the solutions I found solved the problem.

When trying to run any code using the Start button inside VS, it would hang with the message "Microsoft Visual Studio is Waiting for an Operation to Complete". VS then had to be ended from task manager.

After much trial and error, I found that disabling the service "Visual Studio Standard Collector Service" fixed the issue.

I know this issue is old, but hopefully this gives people one more thing to try if nothing else has worked.

14 answers

Hamish 1 Reputation point

2025-03-29T01:44:48+00:00

I had this problem on a much later build. What solved it for me was deleting the global section out of the solution file. I figured this out after realizing VS was hanging at the IVsSolutionBuildManager5.FindActiveProjectCfgName(Guid, String) Method. This also explains why the build worked OK at command line; the solution was not being used by msbuild, only the root project. Maybe time to migrate to SLNX!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Mohammad Aldefrawy 0 Reputation points

2023-12-07T17:57:31.1866667+00:00

Only worked for me after deleting hidden folder .vs.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Coder Jax 0 Reputation points

2023-11-17T08:42:56.9566667+00:00

After logging into Windows and running VS, the first time I try to execute the build action I get the "Starting build..." message and then nothing, VS indicates it's "not responding", but if I leave it for a while (sometimes as long as 15 minutes), it actually does start building.

Subsequent builds proceed normally without the unresponsive interval, and the problem won't recur unless Windows (11) is restarted.

It's not ideal, but maybe try leaving VS for a bit longer before killing it via task manager until the issue is properly addressed.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Michael Mortensen 0 Reputation points

2023-09-12T19:43:22.48+00:00
This is very strange; all newer Visual Studio 2022 fails .. but from .NET SDK perspective, it is "only" version newer than 7.0.307 that fails with an infinite hang and 100% CPU usage.

I am very curious to what Microsoft have done to break this.

Tested versions (dotnet build):

global.json is not honored from Visual Studio - so unfortunately I cannot build my project from here.

If anybody wants to test it out, feel free to do a:
```
git clone https://github.com/gimlichael/Cuemon.git
```
It is enough to try and build the Cuemon.Core project. Again, using dotnet build, it works flawlessly with any version prior or equal to 7.0.307. From 7.0.400 and forward it fails.

Said mentioned project, Cuemon, will fail to build in any newer versions of Visual Studio (after June 30 this year).

I am empty for ideas on how to fix this - so any help would be much appreciated.

Thanks.

UPDATE 1:

If I use Resharper Build & Run, I can manually set the MSBuild to the one from .NET SDK within Visual Studio 2022. Just like dotnet build, this works with any version prior or equal to 7.0.307.

UPDATE 2:

Eureka! I have found the root cause; in Cuemon I have a class named Template (https://github.com/gimlichael/Cuemon/blob/development/src/Cuemon.Core/Template.cs).

This class supports up to 20 generic parameters (yeah, I know - who would really want to use that many - but that is beside the point).

After .NET SDK 7.0.307, Microsoft has made a change to MSBuild/dotnet that triggers the infinite build.

I will see if I can make a GitHub issue - though I am in doubt where.

My best guess would be .NET SDK if such exists - otherwise somewhere in the dotnet organization.

For those of you experiencing same issue; it MIGHT be because of extensive generic use - but who knows - there could be other compilation bugs introduced after said mentioned .NET SDK version.

Happy coding!

UPDATE 3:

Created an issue on GitHub: https://github.com/dotnet/sdk/issues/35365
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Visual Studion 2022 Version 17.6 Hangs on Build\Clean\Rebuild All

14 answers

Your answer