From d98c24186d9b73065bbb4ac8be56aec478fabf4f Mon Sep 17 00:00:00 2001 From: Derrick Stolee Date: Tue, 2 Jun 2020 19:50:16 -0400 Subject: [PATCH] troubleshooting.md: include description of Checking for GVFS upgrades...- Checking for GVFS upgrades...\ Checking for GVFS upgrades...\ Checking for GVFS upgrades...| Checking for GVFS upgrades...| Checking for GVFS upgrades...Succeeded New version 1.0.19346.2 is available. Upgrade will unmount and remount gvfs repos, ensure you are at a stopping point. When ready, run `gvfs upgrade --confirm` from an elevated command prompt. bug Signed-off-by: Derrick Stolee --- docs/troubleshooting.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 9ac05d59..d43bcd51 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -22,6 +22,18 @@ will prompt you for upgrade using a notification. To check manually, run `gvfs upgrade` to see if an upgrade is available. Run `gvfs upgrade --confirm` to actually perform the upgrade, if you wish. +### Upgrade fails with + +**Symptom:** `gvfs upgrade` fails with the following error: + +> ERROR: Could not launch upgrade tool. File copy error - The specified path, file name, or both are too long" + +**Fix:** There is a known issue with VFS for Git v1.0.20112.1 where the +`gvfs upgrade` command fails with a long-path error. The root cause is a +[recursive directory copy](https://github.com/microsoft/VFSForGit/pull/1672) +that loops the contents of that directory into the copy and it never ends. +The only fix is to [manually upgrade to version v1.0.20154.3](https://github.com/microsoft/VFSForGit/releases/tag/v1.0.20154.3). + Common Issues -------------