From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: James Gao <thehighmountain25@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Bug report: latest (2.50.1) x64 version of Git for Windows
Date: Tue, 22 Jul 2025 00:01:31 +0000 [thread overview]
Message-ID: <aH7U26rPYIqbtcwS@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <CA+=FFpNPLEYsajBZqhxhnD3-642t=qQribO+oNDF5-3hhuxDnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2776 bytes --]
On 2025-07-21 at 20:34:35, James Gao wrote:
> Hi!
>
> I just installed my system, and downloaded latest (2.50.1) x64 version
> of Git for Windows and installed it.
>
> I am on Windows 11 Pro, 10.0.22631.
> Git CLI is not getting permission to the folders.
> For example, I cannot run git init - error: couldn't set 'HEAD'
> I cannot git pull or clone or git add
>
> It returns me similar errors:
> error: unable to write file
> .git/objects/36/dd1796da4dcbb2f53005b64afeef698cfaf510: Permission
> denied
> error: src/helpers/schedule.ts: failed to insert into database
> error: unable to index file 'src/helpers/schedule.ts'
>
> I have tried every single help articles and blogs, nothing is working.
>
> I tried running git bash as Administrator, still not working.
>
> I am planning to download older versions, but it would be great to get
> it fixed for lts.
I don't see this behaviour on my Linux system, so I suspect this is
something specific to your system or to Windows. I would suggest trying
to report this on the Git for Windows issue tracker at
https://github.com/git-for-windows/git/issues.
A brief search shows that there are some issues there with this error
message. For instance, if you're operating on a CIFS/SMB share (that
is, those with the `\\share\` syntax), there's a known issue about that.
It's also known that you should not put your Git repositories in a
folder that's special to Windows, such as Documents, because Windows
imposes additional restrictions on those paths in ways that can break
Git (this is also true of macOS).
Similarly, you absolutely should not place repositories in a directory
managed by OneDrive, Dropbox, or a similar syncing service, since they
often don't work and even when they do, these services can cause
corruption to repositories. If it's not a regular folder on a regular
NTFS disk, you might try using a regular NTFS disk (such as C) to try to
see if it makes a difference.
If you do report it to the Git for Windows tracker, please search for
both open and closed issues and mention anything that is special about
your repositories and where you're storing them. Is it a network drive
or folder? What kind? Is it a drive other than C? What storage is it
on? What file system is it using? These kinds of answers will help the
maintainer determine the relevant difference about what's not working
and fix it. I feel very confident that the Git for Windows maintainer
would not have released totally broken software, since they are
thoughtful and diligent, so there's some specific reason it's not
working for you while it is working for others.
Best of luck in solving your issue.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-07-22 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 20:34 Bug report: latest (2.50.1) x64 version of Git for Windows James Gao
2025-07-22 0:01 ` brian m. carlson [this message]
2025-07-22 9:47 ` Johannes Schindelin
2025-07-22 16:38 ` James Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aH7U26rPYIqbtcwS@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=thehighmountain25@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox