You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to git-for-windows
Previously been using Git for windows with no problems....but have recently been unable to excute any bash commands?
e.g. touch test.txt
touch: cannot touch 'test.txt': no such file or directory
everything looks, ok , cmd added to path etc
Running git for windows 2.21 and windows build 1809
Any suggestions?
luke maggs
unread,
Apr 17, 2019, 12:27:30 PM4/17/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to git-for-windows
UPDATE:
Weirdly this seemed related to the new Windows 10 feature around securing folders/files from Ransomware
Once enabled this seemed to break all git bash commands in windows but as soon as I disabled this setting (after much PATH investigation, uninstalling, reinstalling, diving through the forums haha!) everything seemed fine again
Just posting in case it helps anyone else
Luke
Philip Oakley
unread,
Apr 17, 2019, 5:58:36 PM4/17/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to luke maggs, git-for-windows
Hi Luke,
Thanks for the notification. Is there a particular 'name' (given by
Microsoft) for this 'feature'.
Was there a specific location for switching it off (a specific control
panel), or was it via a registry setting, or something else.
The problem sounds like it could hit a lot of people.
Also, do you have the build number / version that you are currently running.
Didn't follow it further at this moment (too much other 'real life' to
deal with..)
I searched on Luke's exact phrase "new Windows 10 feature around
securing folders/files from Ransomware", always a useful trick...
Not sure of how it got turned on for Luke in the first place (some AV
(anti-virus) update or network policy change?) but good that the cause
and (local) fix has been found.