Azure DevOps clone fails in Visual Studio: “Unable to start process. Unable to resume suspended process during process creation.

Question

Azure DevOps clone fails in Visual Studio: “Unable to start process. Unable to resume suspended process during process creation.

Kumar, Sonbir 0

When I attempt to clone an Azure DevOps Git repository through Visual Studio, Visual Studio displays an Azure DevOps Error dialog: Unable to start process. Unable to resume suspended process during process creation.

Git for Windows is installed and available from PowerShell: git version 2.55.0.windows.5 The issue occurs during the repository clone workflow in Visual Studio.

Steps to Reproduce Open Microsoft Visual Studio. Select Clone a repository. Enter or select an Azure DevOps Git repository URL. Choose a local destination folder. Select Clone. Observe the error dialog.

Actual Result Visual Studio displays the following error and does not complete the clone: Git Global config failed to set Unable to start process. Unable to resume suspended process during process creation.

Expected Result Visual Studio should start the Git process and clone the selected Azure DevOps repository to the specified local folder.

**Here are the steps taken so far:

image (32)

image (33)

0 comments

2 answers

Your answer

Answer 1

Brian Pham (WICLOUD CORPORATION) 650 Microsoft External Staff Moderator

Hi @Kumar, Sonbir

Thank you for the detailed information and screenshot.

Based on the error message:

Unable to start process. Unable to resume suspended process during process creation.

the issue appears to occur before Visual Studio starts the Git operation itself. This is typically related to Visual Studio being unable to launch the configured Git executable, rather than a problem with Azure DevOps or the repository.

Some common causes include:

Visual Studio cannot access or start the configured Git executable.
A corrupted or invalid Git configuration file (.gitconfig).
Endpoint security software (such as Microsoft Defender, CrowdStrike, SentinelOne, Carbon Black, etc.) preventing process creation.
A Visual Studio Git integration or configuration issue.

As an initial troubleshooting step, please try the following:

Verify Git works outside Visual Studio:

git --version git config --global --list

Confirm both commands complete successfully without errors.
In Visual Studio, navigate to: Tools > Options > Source Control > Git Global Settings and switch between Embedded Git and System Git (or manually point to git.exe), then restart Visual Studio.
Check whether the global Git configuration file is corrupted: Rename: %USERPROFILE%.gitconfig to: %USERPROFILE%.gitconfig.bak then restart Visual Studio and test again.
Test cloning the same repository from a command prompt:

git clone <repository-url>

If command-line Git succeeds while Visual Studio fails, the issue is likely within Visual Studio's Git integration or a local environment restriction.

If the issue persists after the above steps, please provide the following information so we can investigate further:

Whether Git clone succeeds from the command line.
Whether endpoint security software (Defender, CrowdStrike, SentinelOne, Carbon Black, etc.) is installed.
A Visual Studio activity log generated using: devenv /log The log can be found under: %APPDATA%\Microsoft\VisualStudio<version>\ActivityLog.xml

This information will help determine whether the failure is related to Visual Studio Git integration, Git configuration, or a security product preventing Visual Studio from launching Git processes.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.

Mr Sonbir 50 Reputation points

2026-10-16T04:18:22.61+00:00

Git command prompt is working appart from vs code git also working git bash also working only facing issue in visual studio app while processing git clone or update repo following security git program Data ide entire location is excluded but still same issue getting
Brian Pham (WICLOUD CORPORATION) 650 Reputation points Microsoft External Staff Moderator

2026-10-16T04:38:45.5633333+00:00
Hi @Mr Sonbir ,

Thank you for the update.

Since Git works successfully from Command Prompt, Git Bash, and VS Code, we can likely rule out a general Git installation issue. The evidence suggests the problem is isolated to Visual Studio's interaction with Git.

At this point, I would recommend the following Visual Studio-specific troubleshooting steps :

In Visual Studio, go to: Tools > Options > Source Control > Git Global Settings and switch between Embedded Git and System Git (if available), then restart Visual Studio and test the clone operation again.

Close Visual Studio and clear the Visual Studio cache: %LOCALAPPDATA%\Microsoft\VisualStudio In particular, remove the ComponentModelCache folder if present.

Start Visual Studio in Safe Mode to determine whether an extension is interfering with Git operations: devenv /safemode Then attempt the clone operation again.

Run a Visual Studio Repair using Visual Studio Installer and retest after the repair completes.

Because Git functions correctly outside Visual Studio, the issue appears to be specific to Visual Studio's Git integration or its ability to create Git-related processes.

If the issue persists after the above steps, could you please provide:

Whether the issue occurs with both Embedded Git and System Git.

The Visual Studio Activity Log generated

This information will help us determine whether the failure originates from a Visual Studio component, an extension, or a process-creation restriction affecting Visual Studio specifically.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.
Mr Sonbir 50 Reputation points

2026-10-16T04:45:50.34+00:00
@Brian Pham (WICLOUD CORPORATION) No this issue started sudden at 29 of October and the hole org user affect this issue and this is increasing day to day.

I have already did some troubleshooting for this details are below

Troubleshooting Summary – Visual Studio Azure DevOps Git Clone Failure

Issue Description

When attempting to clone an Azure DevOps Git repository through Visual Studio 2026 or older versions, the operation fails with the following error:

Error: “Git Global config failed to set”

Details: “Unable to start process. Unable to resume suspended process during process creation.”

Git for Windows is installed and accessible through PowerShell. The installed version is "2.55.0.windows.5". However, the repository clone workflow in Visual Studio continues to fail.

Troubleshooting Steps Performed

Windows OS Troubleshooting

Attempted to uninstall recently installed Windows security updates.

Attempted to roll back the Windows feature update from version 26 to version 25.

The issue persisted after these attempts.

Windows Security / Microsoft Defender Troubleshooting

Monitored Windows Security and Microsoft Defender.

Attempted to update Defender Security Intelligence and roll back to a previous version.

Paused the Defender for Endpoint sensor service through the Defender management options provided by the Security team.

The device was offboarded from Defender for Endpoint for testing. The sensor service was confirmed stopped after offboarding.

The issue persisted despite these actions.

Visual Studio Application Troubleshooting

Updated Visual Studio to the latest available version.

Completely uninstalled and reinstalled Visual Studio.

Tested with an older Visual Studio version.

The Azure DevOps Git clone failure remained unresolved.

Current Status

The issue persists despite Windows OS, security-related, and Visual Studio application troubleshooting. No confirmed root cause has been identified yet.

Next Step: Further investigation is required to identify what prevents Visual Studio from creating or resuming the Git process during repository cloning.

Note: Defender for Endpoint was offboarded as part of troubleshooting.
Brian Pham (WICLOUD CORPORATION) 650 Reputation points Microsoft External Staff Moderator

2026-10-16T06:50:55.6+00:00
Hi @Mr Sonbir ,

Thank you for providing such a detailed troubleshooting summary.

To help identify where the failure occurs, could you please collect the following from one affected machine?

Collect the Visual Studio Activity Log:

Close all Visual Studio instances.

Open Command Prompt as the affected user.

Run :devenv /log (If devenv is not recognized, open Developer Command Prompt for Visual Studio and run the same command.)

Visual Studio will launch.

Reproduce the Git clone/update failure.

Close Visual Studio.

Navigate to: %APPDATA%\Microsoft\VisualStudio

Locate and share: ActivityLog.xml

Verify Whether Any Organization-Wide Policy Changes Were Introduced: Since the issue:

Started suddenly around October 29,

Affects multiple users, and appears to be expanding to additional users,

Could you please check with the security or infrastructure team whether any of the following were deployed or modified around that period?

At this stage, the ActivityLog.xml should provide the most valuable evidence to determine why Visual Studio is unable to launch or resume the Git process while Git continues to function normally from other clients such as Command Prompt, Git Bash, and VS Code.

From the information available so far, an environment-level policy change affecting Visual Studio is currently one of the primary areas of investigation.

Additionally, could you please confirm whether affected users have local administrator permissions on their machines? I'm asking because, depending on what we find in the Visual Studio Activity Log, the next troubleshooting step may involve collecting a Process Monitor (ProcMon) trace, which often requires administrative privileges to capture the necessary process creation events.
Mr Sonbir 50 Reputation points

2026-10-16T09:05:22.4166667+00:00

@Brian Pham (WICLOUD CORPORATION) ActivityLog.xml Attached
Brian Pham (WICLOUD CORPORATION) 650 Reputation points Microsoft External Staff Moderator

2026-10-16T10:15:40.91+00:00
Hi @Mr Sonbir ,
Thank you for sharing the Activity Log.

I reviewed the log and noticed several Visual Studio component-loading errors; however, I was unable to find any entries directly related to the Git clone operation.

I also noticed the following component-loading errors:

Microsoft.VisualStudio.WSLInstaller.Shared

Microsoft.VisualStudio.LiveShare.WebEditors

PkgDefMgmt.dll

While these entries do not directly reference Git operations, I wanted to call them out as they may indicate additional Visual Studio component-loading issues. At this point, however, I cannot confirm whether they are related to the Git clone failure or are separate issues.

Could you confirm whether the Git clone failure was captured after launching Visual Studio with:

devenv /log

Specifically, the ideal sequence would be:

Close all Visual Studio instances.

Run devenv /log.

Wait for Visual Studio to open.

Open Clone a Repository.

Attempt to clone the same Azure DevOps repository.

Wait until the "Unable to start process. Unable to resume suspended process during process creation" error appears.

Close Visual Studio.

Collect the newly generated ActivityLog.xml.

I ask because the current log appears to contain startup and component-loading information, but it does not appear to capture a Git operation failure. If the clone error was reproduced after running devenv /log, I can continue investigating based on the updated log.

Additionally, could you please confirm whether affected users have local administrator permissions on their machines? Depending on the findings from the updated Activity Log, we may need to collect additional diagnostics in a later troubleshooting step.
Mr Sonbir 50 Reputation points

2026-10-16T10:26:29.49+00:00

@Brian Pham (WICLOUD CORPORATION) Yes, when I ran devenv /log, Visual Studio opened, and I followed the log activity in the same open application.
Git clone failure was captured after launching Visual Studio with

Attached new logs file hereActivityLog 1.xml
Brian Pham (WICLOUD CORPORATION) 650 Reputation points Microsoft External Staff Moderator

2026-10-16T10:45:33.8133333+00:00
Hi @Mr Sonbir ,

Thank you for confirming that the Git clone failure was reproduced after launching Visual Studio with devenv /log.

I reviewed the updated Activity Log and continue to see several Visual Studio component-loading errors; however, I still do not see any entries directly related to Git operations, git.exe, or the specific error:

Unable to start process. Unable to resume suspended process during process creation.

This suggests that the failure may be occurring before Visual Studio is able to log details about the Git process itself.

To investigate further, could you please confirm whether you have local administrator permissions on an affected machine? If administrative access is available, I'd like to collect a Process Monitor (ProcMon) trace while reproducing the issue.

ProcMon collection steps

Download Process Monitor (ProcMon) from Microsoft Sysinternals.

Launch ProcMon as Administrator.

Press Ctrl + X to clear any existing events.

Press Ctrl + E to stop capturing temporarily.

Select Filter > Filter...

Add the following filters: Process Name | is | devenv.exe | Include Process Name | is | git.exe | Include

Click Add for each filter and then click OK.

Press Ctrl + E to start capturing.

Open Visual Studio and perform the same Git clone operation until the error appears.

Return to ProcMon and press Ctrl + E again to stop the capture.

Select File > Save.

Choose All Events and save the trace as a .PML file.

Note: Since the capture is filtered to devenv.exe and git.exe, the resulting trace may remain reasonably sized. However, if the saved .PML file is too large to upload to this thread, please either:

Compress the file into a .ZIP archive, or

Share screenshots of any events involving devenv.exe or git.exe around the time the error occurs, especially entries showing:

ACCESS DENIED NAME NOT FOUND PATH NOT FOUND

or any failed Process Create operations.

Since the Activity Log is not capturing the Git process failure itself, the ProcMon trace should help determine whether Visual Studio is unable to launch git.exe or whether another component or policy is preventing the process from being created successfully.
Mr Sonbir 50 Reputation points

2026-10-16T11:32:06.06+00:00

@Brian Pham (WICLOUD CORPORATION) PFA logs collect with ProcMon collection wth ran devenv /log,
attached new logs file with process monitor ActivityLog.xml
yes NAME NOT FOUND found

process monitor log size is 5 gb unbale to upload here suggest

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Azure DevOps clone fails in Visual Studio: “Unable to start process. Unable to resume suspended process during process creation.

2 answers

ProcMon collection steps

Your answer