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

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:

1. Close all Visual Studio instances.
2. Run devenv /log.
3. Wait for Visual Studio to open.
4. Open Clone a Repository.
5. Attempt to clone the same Azure DevOps repository.
6. Wait until the "Unable to start process. Unable to resume suspended process during process creation" error appears.
7. Close Visual Studio.
8. 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.

@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

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

1. Download Process Monitor (ProcMon) from Microsoft Sysinternals.
2. Launch ProcMon as Administrator.
3. Press Ctrl + X to clear any existing events.
4. Press Ctrl + E to stop capturing temporarily.
5. Select Filter > Filter...
6. Add the following filters: Process Name | is | devenv.exe | Include Process Name | is | git.exe | Include
7. Click Add for each filter and then click OK.
8. Press Ctrl + E to start capturing.
9. Open Visual Studio and perform the same Git clone operation until the error appears.
10. Return to ProcMon and press Ctrl + E again to stop the capture.
11. Select File > Save.
12. 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.

@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

@Brian Pham (WICLOUD CORPORATION) any update on this Sir

Hi @Mr Sonbir ,

Thank you for the ProcMon screenshots.

The NAME NOT FOUND entries shown appear to be associated with Visual Studio registry lookups (RegQueryKey / RegQueryValue) rather than attempts to locate git.exe or another required executable. Visual Studio performs a large number of these registry checks during normal operation, so these particular entries do not immediately indicate the cause of the Git clone failure.

The screenshots also confirm that git.exe is being launched and is actively performing operations, so we can no longer assume that Visual Studio is completely unable to start Git.

At this point, rather than reviewing the entire 5 GB trace, could you identify the approximate timestamp when the Visual Studio error dialog appears and then review the ProcMon events immediately before and after that time?

In particular, any events involving devenv.exe or git.exe that show unusual results such as:

ACCESS DENIED

PATH NOT FOUND

Process Exit

Cause I'm trying to understand whether the failure occurs: before git.exe starts, immediately after git.exe starts, or while Visual Studio is communicating with the Git process.

If you find any such events near the error timestamp, please share screenshots of those specific entries.

@Brian Pham (WICLOUD CORPORATION) can we connect remote session for check

Hi @Mr Sonbir ,

Unfortunately, remote troubleshooting sessions cannot be arranged through the Microsoft Q&A platform due to the limit of this platform. This forum is designed for asynchronous support through posts, comments, screenshots, and log sharing, and contributors do not have the ability to establish remote access sessions.

If any of my previous instructions were unclear or if you encountered any difficulties while reviewing the ProcMon trace, please let me know. I'd be happy to clarify the steps or explain what specific information I'm looking for in the trace.

Okay, these are attached with the latest timestamp. Please let me know if you find any errors or solutions.

Hi @Mr Sonbir ,

Thank you for providing the additional diagnostic information and for your continued cooperation during the investigation.

Based on the information collected so far, one likely area to investigate is whether the endpoint security configuration is interfering with the Git executable bundled with Visual Studio. This could explain why Git works from PowerShell, Git Bash, and VS Code, while Git operations initiated specifically from Visual Studio continue to fail.

Although security exclusions were already tested, please ask your security team to verify specifically that exclusions are configured for the Visual Studio bundled Git directory applicable to the installed Visual Studio version and edition:

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin C:\Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin

Please note that excluding the separately installed Git for Windows directory, such as: C:\Program Files\Git does not necessarily cover the Git executable and related binaries bundled with Visual Studio.

The security team should verify that:

1. The exclusion applies to the exact Visual Studio edition and version installed on the affected machine.
2. The exclusion has been successfully delivered and applied to the affected device.
3. The exclusion covers the full mingw64\bin directory, rather than only a separate git.exe installation.
4. No other endpoint-security or application-control policy continues to inspect or restrict Git-related child processes launched from devenv.exe.

After the exclusions have been verified, please restart Visual Studio and test the following:

1. Open Git > Settings > Git Global Config and confirm whether the settings load successfully.
2. Select Clone a repository and try cloning the same Azure DevOps repository.
3. Test a pull or update operation in an existing repository.

During my investigation, I also found a similar issue reported in the Visual Studio Developer Community. The reported symptoms closely match the behavior in your environment.

In that case, the issue was resolved after the organization’s security team added exclusions for the Visual Studio bundled Git directories. Microsoft subsequently classified that specific report as a local security configuration issue rather than a Visual Studio product bug

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

Hi @Mr Sonbir ,

As I haven’t heard back from you for some time, I hope the information I shared helped with your issues.

If you still need assistance or have any additional questions, please feel free to reach out whenever it’s convenient for you. I’ll be happy to help.

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

@Brian Pham (WICLOUD CORPORATION) Not yet still getting same error

Hi @Mr Sonbir ,

Thank you for the update. To clarify, has your security team already added and verified the exclusion for the exact Visual Studio bundled Git directory on an affected machine?

For the Visual Studio Professional installation shown in the diagnostic information, please verify this path:

C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin

Regardless of whether the exclusion has already been applied, please test the exact Git executable bundled with Visual Studio from PowerShell:

$vsGit = "C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin\git.exe"

Test-Path $vsGit
& $vsGit --version
& $vsGit config --global --list

Please share the output of all three commands and confirm whether the security exclusion was already active when the commands were run.

The results will help us distinguish between the following scenarios:

• If the bundled Git commands fail before the exclusion but succeed afterward, the endpoint-security configuration is likely involved.
• If the bundled Git commands succeed but Visual Studio continues to fail, the issue may be specific to the way devenv.exe launches or communicates with Git.
• If the commands continue to fail after the exclusion is confirmed, the exclusion may not yet be effective, may not cover all required Git components, or the issue may have another cause.

A similar Visual Studio Developer Community report was resolved after the organization’s security team excluded the Visual Studio bundled Git directories. This does not confirm that the same configuration is the root cause in your environment, but it makes this comparison a relevant next diagnostic step.

@Brian Pham (WICLOUD CORPORATION) Error getting

Hi @Mr Sonbir ,

Thank you for providing the test results.

The results confirm that:

• The Visual Studio bundled git.exe exists.
• It can be started directly from PowerShell.
• It reports Git version 2.55.0.windows.5.

To bypass the pager and complete the configuration test, please run:

& $vsGit --no-pager config --global --list

Also, could you confirm whether the security team has already added and verified the exclusion for this exact directory on the affected machine?

C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin

@Brian Pham (WICLOUD CORPORATION) this alredy exclude in security

C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin

Yes the results confirm that:

• The Visual Studio bundled git.exe exists.
• It can be started directly from PowerShell.
• It reports Git version 2.55.0.windows.5.

Hi @Mr Sonbir ,

Based on the information collected so far, interference from endpoint-security or application-control software remains a possibility.

Since an exclusion for the mingw64\bin directory has already been attempted in your case, I recommend asking your IT/security team to verify whether the following executables are explicitly included in the security software's safe executable allowlist, or whether an equivalent policy is required:

• C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw64\bin\git.exe
• C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git.exe

If the issue remains after this verification, you can:

1. Submit a report on Developer Community with Visual Studio tag, so the Visual Studio engineering team can investigate the process-launch failure in greater depth.
2. If you or your organization have an eligible Visual Studio subscription, depending on your support entitlement, you can submit a support ticket for advanced assistance, such as a 1:1 consultation, remote support, or a Teams meeting with a support engineer. This is an effective way to resolve your concern.

I’m apologize that I have not been able to confirm the root cause or provide a specific solution through the diagnostics available on this forum and I sincerely appreciate your patience and all the effort you have put into the troubleshooting process.

If you have any questions about how to create the Developer Community report, please leave a comment here and I will be happy to provide further guidance.

Hi @Mr Sonbir ,

I'm just checking in to see if you were able to create the Developer Community report and whether there have been any updates on the issue. If you need any help with the steps to submit the report, please let me know and I’ll be happy to assist.

@Brian Pham (WICLOUD CORPORATION) Microsoft Support under Tracking ID # [Removed PII]

Hi @Mr Sonbir ,

Thank you for the update. I’m glad to know that a Microsoft Support case has been opened. Based on the latest information, the relevant Product Group has also joined the investigation, so please continue working with them.

If you found my guidance and assistance throughout this investigation helpful, you’re welcome to share your feedback by following this guidance. This is entirely optional and is greatly appreciated.

I hope the support team can identify the root cause. Please feel free to share the final outcome here, as it may also help others experiencing the same issue.

Have a nice day!

The issue has been resolved after updating Git and Visual Studio to the latest versions.

Required Actions:

1. Git: Install the latest Git release, version 2.56.0.3, available through the Company Portal.
2. Visual Studio: Update Visual Studio 2022  to version 18.11.2 directly through the Visual Studio Installer.
3. Restart: Once both updates are complete, please restart your system to ensure the changes take effect.

After completing these steps, please verify that you can clone Azure DevOps repositories successfully through Visual Studio