Windows 10下的Git Bash不执行Vagrant版本

发布于 2025-01-21 11:33:01 字数 447 浏览 0 评论 0原文

安装了GIT版本2.35.1.Windows.2 Windows 10下方。从Git Bash，Run：Vagrant版本。打开DOS窗口，执行并关闭。因此，我无法使用这些类型的命令，例如Vagrant版本。 100％可重复。

如果我运行git bash升高，那么我可以看到命令按预期完成。

Windows 10机器的预期行为，GIT运行未升高：

vagrant version
Installed Version: 2.2.19
Latest Version: 2.2.19

这两台机器都是按预期运行的机器，而失败的机器是GIT安装为常规用户，GIT安装在下面： c：\ users＆lt; username＆gt; \ appdata \ local \ program \ git \ git \ git-bash.exe - cd-to-to-to-to-to-to

原文

Installed git version 2.35.1.windows.2 under Windows 10.
From git bash, run: vagrant version. Opens up a dos window, executes, and closes.
So I cannot use these types of commands, like vagrant version.
100% repeatable.

If I run git bash elevated, then I can see the command completes as expected.

Expected behavior from a Windows 10 machine that works, with git running not elevated:

vagrant version
Installed Version: 2.2.19
Latest Version: 2.2.19

Both machines, the one that works as expected and the one that fails, git was installed as regular user, with git being installing under:
C:\Users<username>\AppData\Local\Programs\Git\git-bash.exe --cd-to-home

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

他不在意 2025-01-28 11:33:01

尝试使用有问题的PC使用简化的路径并查看是否有效：

打开一个CMD和类型：

set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\
set "GH=%LOCALAPPDATA%\Programs\Git"
set "PATH=%GH%\bin;%GH%\cmd;%GH%\usr\bin;%GH%\mingw64\bin;%GH%\mingw64\libexec\git-core;%PATH%"
set "PATH=C:\path\to\vagrant.exe;%PATH%"

替换c：\ path \ to \ vagrant.exe by parent vagrant.exe 的em>文件夹，在％path％中不包括vagrant.exe本身。

测试问题是否存在，然后在该CMD会话中。

bash
vagrant version

Try, with the problematic PC, to use a simplified PATH and see if that works:

Open a CMD and type:

set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\
set "GH=%LOCALAPPDATA%\Programs\Git"
set "PATH=%GH%\bin;%GH%\cmd;%GH%\usr\bin;%GH%\mingw64\bin;%GH%\mingw64\libexec\git-core;%PATH%"
set "PATH=C:\path\to\vagrant.exe;%PATH%"

Replace C:\path\to\vagrant.exe by the parent folder of vagrant.exe, do not include vagrant.exe itself in the %PATH%.

Test if the issue persists then in that CMD session.