Summary
So far, we think the issue is a combination of Windows not having paths longer than 260 characters enabled by default, but is possible to fix on Windows 10. On Windows 10, after doing the registry fix (and now also the Group Policy Editor preference) (and rebooting?), you must enable core.longpaths in Git for Windows and possibly other Git clients you may be using.
Error
Solution
Step 1: Run Registry Modifier
Download and run this script to apply the fix –> Remove 260 Character Path Limit.reg
Reverting
If you need to go back for some reason, run this file:
Restore 260 Character Path Limit (Default).reg
* Solution source: https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
Step 2: Set "Enable Win32 longs paths" to Enabled
Hit Windows key. Type "Edit Group Policy", hit Enter.
Under Computer Configuration > Administrative Templates > System > Filesystem
Right click Enable Win32 long paths, Edit, set to Enabled.
In a terminal launched with Administrator mode.
* Solution source: https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows
More Info
https://github.com/msysgit/msysgit/wiki/Git-cannot-create-a-file-or-directory-with-a-long-path