Not remembering source control plug-in (Git)

Brad Knode 70

Since the last release, Visual Studio 2022 is not remembering the source control selection. Every time a project is opened, I must open the options dialog, go to Source Control, and select Git from the "current source control plug-in."

Once I do this, it automatically loads my global settings (username, email, etc.) and the appropriate repo. From there, I can interact with Git as normal.

But if I unload the project or restart Visual Studio, the source control is gone again and I have to repeat the steps above.

Brad Knode 70 Reputation points

2023-10-10T18:31:37.5333333+00:00

Still an issue in 17.7.5
Doug Clutter 15 Reputation points

2023-10-13T20:41:36.53+00:00

This appears to be fixed in 17.8.0 Preview 3...so I guess we'll see this in a month.
Tim Sheehan 0 Reputation points

2023-10-24T04:45:20.3266667+00:00

Also occurring here, reset to git on every project load
Garry Lowther 21 Reputation points

2024-05-13T16:15:51.6833333+00:00

I am on the latest Visual Studio 2022 and this is STILL a bug i.e. forgetting the current source control plug-in
Adrian Stanley 0 Reputation points

2024-05-15T15:56:01.7733333+00:00

I get something similar, using the latest VS 2022 17.9.7 and earlier. My solutions have used TFVC until recently, when I tried out GIT. I am now back using TFVC, and have the source control Plug-in Selection set to Visual Studio Team Foundation Server in the VS options. But every time I open one of my existing solutions in TFVC, I get this error "The active solution is controlled by a different source control plug-in than the one you have selected. If you change the control plugin the active solution or project will be closed. Do you want to continue?" If I choose Yes, it changes the source control plug-in to Git and the solution won't open. If I choose No, the plug-in stays as TFVC and the solution works OK.

I assume the error occurs because VS thinks I have chosen Git as the plug-in, and I am opening a solution controlled by TFVC, but I have Visual Studio Team Foundation Server in the VS options set in the VS options before I try to open the solution. This setting successfully persists after restarting VS. Something somewhere thinks I am using Git.

13 answers

Doug Clutter 15 Reputation points

2023-09-21T16:23:47.3233333+00:00

This is still an issue with 17.7.4, and /ResetSettings doesn't fix it.
Please sign in to rate this answer.

3 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Leonard, Francis 10 Reputation points

2024-02-28T20:22:35.9766667+00:00

This worked for the Developers on our staff who had the same issue, hopefully it will work for you. This assumes you have Git for Windows installed:
Add this environment variable by right clicking your computer icon on the desktop --> properties --> Advanced system settings --> Environment Variables; Add to User variables section --> HOME=%USERPROFILE% Restart Visual Studio.
Please sign in to rate this answer.

2 people found this answer helpful.
Jose Araujo 0 Reputation points

2024-03-08T16:31:44.3766667+00:00

This solved it for me. Thanks!!!! now when I open VS, Git is selected.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
R&D Microstudio 5 Reputation points

2025-06-19T06:40:58.16+00:00

Up to today, Version 17.14.6 (June 2025), it still does not work.

I have both Git and Helix scc extensions.

My project was previously on Helix and now it is on Git.

I opened from git correctly until once I clicked the wrong extension (bottom right corner add to source control) and it connected to Helix.

I reverted back to Git inside the Tools-Options menu and it works, but now every time I reopen VS I get prompted by the "You are currently working on a Solution that is controlled by a different source code control plug-in" message and to stay in Git I need always to click No.

It works but it is unconfortable, expecially if I do a mistake and press yes.

How can I get rid of the message and stay automatically in Git without removing or disabling Helix? (I need it for other projects)
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2023-09-07T09:05:56.3066667+00:00

Hello @Brad Knode ,

Welcome to Microsoft Q&A forum.

I tested in VS 2022 17.7.3 but it seems that the issue didn’t occur, the Git option was selected whenever I unloaded the project or restarted VS.

In case some cache causes this issue after updating, would you mind trying to reset VS settings by running devenv /ResetSettings command in VS developer Command Prompt?

Best Regards,

Tianyu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Brad Knode 70 Reputation points

2023-09-07T14:39:37.7566667+00:00

Thanks. I tried this, but unfortunately it didn't help. I also tried removing the local caches as outlined here: https://learn.microsoft.com/en-us/answers/questions/1221136/visual-studio-2022-clear-local-caches. No luck with that one either.

Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2023-09-08T07:57:12.9766667+00:00

Hi @Brad Knode ,

If you try to run VS as administrator, will the selection be remembered? Is there any permission limitation on your machine? Do you use any extension? This issue also appears on a newly created project, right?

Jason Thompson 0 Reputation points

2023-09-08T20:58:53.95+00:00

I noticed a similar problem with 17.7.3, and it doesn't matter if I Run Elevated (IT controlled admin) or under reduced privileges. I launch VS 2022, set the source control plug-in to Git, and exit. When I open VS again, it has changed back to None. Really obnoxious. Reset settings and removing local caches did nothing.

Once I set the plug-in, I can close the solution and open another without any problems. I have to set the source control plug-in every time I start VS 2022.

EDIT: Setting it to "Visual Studio Team Foundation Server" does not save either.

Jason Thompson 0 Reputation points

2023-09-08T21:04:39.7933333+00:00

Where can we manually edit the setting that VS 2022 loads?

Brad Knode 70 Reputation points

2023-09-11T16:26:46.21+00:00

Same results here - running elevated doesn't help.

Something I noticed is that even after selecting "Git" as the current source my git settings aren't being loaded until I click on the "Git Global Settings". A second after I click that tab, my username, email, and repo locations are loaded and the correct repo along with the active branch are displayed.

Jason Thompson 0 Reputation points

2023-09-13T15:43:43.12+00:00

I see the same "Git Global Settings" behavior you mention.

Jason Thompson 0 Reputation points

2023-09-14T15:43:52.8766667+00:00

Problem persists in 7.7.4 despite the newer Git version

Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2023-09-15T07:59:36.1866667+00:00

Hi @Jason Thompson,

May I know if Tools > Options > Source Control > Git Global Settings > "Automatically load the solution when opening a Git repository" option is checked on your side?

If it isn’t checked, please try to check that option and click OK button. If it is checked, please try to uncheck it, restart VS and check it again.

Brad Knode 70 Reputation points

2023-09-15T15:25:58.85+00:00

Yes, the "automatically load..." option is checked.

Jason Thompson 0 Reputation points

2023-09-18T13:59:07.79+00:00

@Tianyu Sun-MSFT That didn't make any difference.

Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2023-09-20T09:02:18.14+00:00

Hi @Jason Thompson @Brad Knode ,

Thanks for your confirmation, could you please kindly submit a ticket on our Developer Community for further investigate? If you do submit the ticket, please share the ticket link here for better tracking.

Kind Regards,

Tianyu

Brad Knode 70 Reputation points

2023-09-20T15:22:53.2266667+00:00

I have created a ticket with the same information as above.
https://developercommunity.visualstudio.com/t/Not-remembering-source-control-plug-in-/10471229

Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2023-09-21T07:13:32.8966667+00:00

Thanks @Brad Knode , thanks for sharing the ticket link here.

Please kindly follow up that ticket and wait for the latest information.

Regards,

Tianyu

Kenneth Hanscom 0 Reputation points

2023-10-23T13:45:39.7+00:00

17.7.5 - still doesn't remember setting.

In my case it's the opposite, I use TFS and have to switch from GIT to TFS every time I restart.
Sign in to comment

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

2023-09-11T17:27:58.8533333+00:00

Where may, the configuration that VS 2022 loads be manually changed?
Please sign in to rate this answer.
Garry Lowther 21 Reputation points

2024-05-13T16:18:46.32+00:00

I agree that we ought to be able to find which file these settings are loaded from, but even ChatGPT does not know this information. My settings are held here I think:

C:\Users\Administrator\AppData\Local\Microsoft\VisualStudio\17.0_ae0c01eb

but buried in .dat binary files
Sign in to comment

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

Share via

Not remembering source control plug-in (Git)

13 answers

Your answer