Hi David, On Fri, 21 Dec 2018, David Brown wrote: > Unfortunately I have hit refresh many times in previous attempts. > > Notwithstanding, the dialog maintains the error condition claiming pid 10128 > must be closed prior to install. That must mean that there *is* a process with that ID. Have you tried `wmic process list`? Ciao, Johannes > > I'm a big fan of Git but not a Windows fan in the least. > > I have downloaded the latest Windows git and killing as many apps and pids > possible after Windows restart the installation goes south nonetheless. > > Please advise. > > > On 2018-12-21 09:55, Johannes Schindelin wrote: > > Hi, > > > > On Thu, 20 Dec 2018, David Brown wrote: > > > > > - [ ] I was not able to find an > > > [open](https://github.com/git-for-windows/git/issues?q=is%3Aopen) or > > > [closed](https://github.com/git-for-windows/git/issues?q=is%3Aclosed) > > > issue > > > matching what I'm seeing > > > > That's a new one. I saw many bug reporters simply deleting the issue > > reporting template at https://github.com/git-for-windows/git/issues/new > > (and usually then filing only very little information, definitely not > > enough to make sense of the bug report), but I never saw this bug > > reporting template being used to report a Git for Windows bug to the Git > > mailing list yet ;-) > > > > > ### Setup > > > > > > - Which version of Git for Windows are you using? Is it 32-bit or 64-bit? > > > > > > $ git --version --build-options > > > > > > git version 2.20.0.windows.1 cpu: x86_64 built from commit: > > > 95155834166f64fe9666f2c0a4909f076080893a > > > sizeof-long: 4 > > > sizeof-size_t: 8 ** > > > > > > - Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit > > > or > > > 64-bit? > > > > > > $ cmd.exe /c ver > > > > > > ** Microsoft Windows [Version 6.1.7601] ** > > > > > > - What options did you set as part of the installation? Or did you choose > > > the > > > defaults? > > > > > > # One of the following: > > > > > > $ cat /etc/install-options.txt Editor Option: VIM Custom Editor Path: > > > Path Option: BashOnly > > > SSH Option: OpenSSH > > > CURL Option: WinSSL > > > CRLF Option: CRLFAlways > > > Bash Terminal Option: MinTTY > > > Performance Tweaks > > > FSCache: Enabled > > > Use Credential Manager: Enabled > > > Enable Symlinks: Disabled > > > > > > - Any other interesting things about your environment that might be > > > related > > > to the issue you're seeing? > > > > > > ** A so-called VDI running on a Dell WYSE ** > > > > > > ### Details > > > > > > - Which terminal/shell are you running Git from? e.g > > > Bash/CMD/PowerShell/other > > > > > > ** Bash ** > > > > > > - What commands did you run to trigger this issue? If you can provide a > > > [Minimal, Complete, and Verifiable > > > example](http://stackoverflow.com/help/mcve) > > > this will help us understand the issue. > > > > > > ** Windows git upgrade dialog ** > > > > > > - What did you expect to occur after running these commands? > > > > > > ** latest version of git installed ** > > > > > > - What actually happened instead? > > > > > > ** No such pid 10128 to close therefore cancel install ** > > > > This typically means that that process existed *at the time the installer > > checked*. If it was a short-lived process, you can check again by clicking > > that "Refresh" button on the lower left. > > > > Ciao, > > Johannes > > > > > > > > - If the probleminsert URL herey, can you provide the > > > URL to that repository to help us with testing? > > > > > > ** Internal company url. Windows git install dialog is issue ** > > > > >
