-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCM Core failing on push - needs .NET 4.7.2 on Windows 10 #540
Comments
Older Windows versions are not supported by newer .NET versions. What Windows version are you on? |
i facing exact same issue, not found solution yet |
Why won't anybody here answer the question which Windows version they use? |
Closing due to lack of response and Windows version information. |
I'm using Windows 10 and facing the same problem |
Not quite... Your Windows version does support that .NET version. |
In installing, it said "The .NET Framework is not supported on this operating system." |
@navetacandra, @SyyedAbdullah, @sunil-dhakad, @Hussainbabatunde - have you tried a manual install of .NET Framework 4.7.2? Additionally, have you ensured you have installed the latest available Windows 10 updates? |
Nearly the same situation; installation failed due to lack of .NET Framework 4.7.2. I have a working .NET 5 SDK & Runtime installed since I do some devs on .NET 5, so I guess that's not the issue. The problem is, why does GCM say it is built on .NET but it still depends on .NET Framework? Upgrading Windows is unlikely an option for me because of the hardware constraints. SystemWindows version: Windows 10 1511, OS Version 10586.1176 Installed .NET Runtimes:
|
@CSharperMantle - have you attempted a manual install of .NET Framework 4.7.2 as I called out in my previous comment? See discussion on this issue for reasons we still target .NET Framework. |
@ldennington, sad to say that does not work. In fact, the installation of .NET Framework 4.7.2 failed due to an 'unsupported Windows version'. I guess this is because those Microsoft guys have dropped their support for my ancient Windows 10 version, which is a hard restriction. Is there a workaround for this? |
@CSharperMantle - would you mind providing some details on your blockers for upgrading Windows? |
You do have a few options under the upgrade constraints:
I would suggest option 2, given the other two are unsupported and thus carry a fair amount of risk. |
Thanks, @ldennington! 1. For the Windows question: whether I try to use a new installation DVD or 'Windows 10 Upgrade Assistant' the installation just stuck, those circling white dots frozen. 2. For your advice: I would give your Method 2 a try and post the results here as soon as possible. Many thanks again for your quick and helpful suggestions. |
Closing in light of the workarounds listed above for those running older versions of Windows. GCM requires .NET Framework 4.7.2, and the best solution is to upgrade your OS if possible. |
Which version of GCM Core are you using?
From a terminal, run
git credential-manager-core --version
and paste the output.Which Git host provider are you trying to connect to?
Can you access the remote repository directly in the browser using the remote URL?
From a terminal, run
git remote -v
to see your remote URL.[Azure DevOps only] What format is your remote URL?
{org}
@dev.azure.com/{org}
/...{org}
.visualstudio.com/...[Azure DevOps only] If the account picker shows more than one identity as you authenticate, check that you selected the same one that has access on the web.
Expected behavior
I am authenticated and my Git operation completes successfully.
Actual behavior
i tried pushing a project on github but i am getting a git-credential-manager-core.exe error. it is saying i need to install .NET framework, version=v4.7.2. But my system doesnt support that version. i have installed .NET framework runtime version 4.6.2 but the error still persists. I am using windows 10
Logs
Set the environment variables
GCM_TRACE=1
andGIT_TRACE=1
and re-run your Git command. Review and redact any private information and attach the log.The text was updated successfully, but these errors were encountered: