Latest Update brings Github error on pull, push, or sync

Question

In Visual Studio 2019, we have been using the GitHub extension successfully since before release. Now, all of the sudden, when we push, pull, or sync, we receive the following in the Output window:

Warning: 'C:\ProgramData/Git/config' has a dubious owner: '(unknown)'.
For security reasons, it is therefore ignored.
To fix this, please transfer ownership to an admininstrator.

Solution 1

You should check if 'C:\ProgramData/Git/config' actually exists. If it doesn't you can just create it and paste the following into the file:

[core]
    symlinks = false
    autocrlf = true
    fscache = true
[color]
    diff = auto
    status = auto
    branch = auto
    interactive = true
[help]
    format = html
[rebase]
    autosquash = true

This worked for me.

Solution 2

• Select "Tools" in Visual studio
• Select "Get_tools_and_features"-->It will open the visual studio installer
• Click on the "Individual_components" tab in visual studio installer
• Go to "Code_tools" and check "GitforWindows" and "GitextensionforVisualStudio"
• Install these two to resolve this issue.

99% sure that above steps will fix the error.

Solution 3

I fixed it by going to Visual Studio Installer, choosing individual component and searching for "Git". In my case the "Git for Windows" and "GitHub Extension for Visual Studio" was now unchecked/not installed for some reason..

These are the extensions I needed: Visual Studio Installer Git

Installing those create the ProgramData\Git\config file and the error was gone.

Solution 4

We ran into this exact issue after upgrading Git to version 2.23.0.windows.1 on our build agents.

The fix that worked for us was to change the owner of C:\ProgramData/Git/config to Administrators. Note that this is different to the Administrator user!

To do this, right-click on C:\ProgramData/Git/config and select Properties then the Security tab.

And click Advanced...

Use the Change link to set the owner to Administrators.

Solution 5

Delete or rename the existing file at that location is also an option. It looks like it's parts of some lower level windows (or MSYS2/Cygwin) security that's brought in via libgit.lib.

Why the created file has the wrong owner is not yet known.

Who/what is the owner for that existing file? What language is in use?

It's been noted as an issue at https://github.com/git-for-windows/git/issues/2304 but isn't resolved yet.

View more solutions