I just cloned it on my own W10 x64 PC without any issue
D:\git>git version
git version 2.23.0.windows.1
D:\git>git clone https://github.com/microsoft/c9-python-getting-started/
Cloning into 'c9-python-getting-started'...
remote: Enumerating objects: 166, done.
remote: Counting objects: 100% (166/166), done.
remote: Compressing objects: 100% (136/136), done.
Receiving objects: 100% (166/166), 3.11 MiB | 1.36 MiB/s, done.
Resolving deltas: 100% (30/30), done.
Try and unzip PortableGit-2.23.0-64-bit.7z.exe
anywhere you want, and see if setting a simplified PATH (just for testing, in a CMD session) helps:
set GIT_HOME=C:\Path\to\Git
set PATH=%GIT_HOME%;%GIT_HOME%\bin;%GIT_HOME%\usr\bin;%GIT_HOME%\mingw64\bin;%PATH
git clone https://github.com/microsoft/c9-python-getting-started/
Of course, you might have the alternative: clone with the SSH URL
git clone git@github.com:microsoft/c9-python-getting-started.git
But it is more interesting to first understand why HTTPS fails.
phd suggests in the comments a proxy issue, as one illustrated in curl/curl
issue 1433.
I mention in "Unknown SSL protocol error in connection" various way to debug flaky connections, including the Q3 2015 Git 2.6 http.sslVersion
setting, to force sslv3
.