Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GIT Windows 64-bit installer download link is broken #1813

Closed
VladimirBudovsky opened this issue Nov 7, 2023 · 13 comments
Closed

GIT Windows 64-bit installer download link is broken #1813

VladimirBudovsky opened this issue Nov 7, 2023 · 13 comments
Labels

Comments

@VladimirBudovsky
Copy link

Which download is failing?

GIT Windows 64-bit installer

Problem

It downloads the file named 255edd25-cca0-4294-909c-b46bced63e3f.
To run an installer, one must add ".exe" extension.

Operating system and browser

Windows, Chrome and Edge

Steps to reproduce

Try download the installer and see wrong file name

Other details

No response

@pedrorijo91
Copy link
Member

hey @VladimirBudovsky ,

going to https://git-scm.com/download/win, and trying to download, i see normal filenames, e.g., Git-2.42.0.2-64-bit.exe

@VladimirBudovsky
Copy link
Author

VladimirBudovsky commented Nov 8, 2023 via email

@Christophecab
Copy link

Christophecab commented Nov 21, 2023

Hi. Still have a bad name on downloaded file from https://github.com/git-for-windows/git/releases/download/v2.43.0.windows.1/Git-2.43.0-64-bit.exe

The downloaded file is called "a93c7233-5099-4ce1-8597-efb65113b310" without extension. It seems to have the correct size.

But, it occurs only with MS Edge on my desktop. It works perfect ( correct name) when using Chrome... so weird !

@luiey-coretekno
Copy link

Failed to download file as exe. Tried on chrome and edge. Still downloading as a93c7233-5099-4ce1-8597-efb65113b310. The other options are using PowerShell based on site download page instructions alternative.
winget install --id Git.Git -e --source winget and it will successfully be installed.

If I paste URL from PowerShell downloading path directly in browser also will be saved as a93c7233-5099-4ce1-8597-efb65113b310.
https://github.com/git-for-windows/git/releases/download/v2.43.0.windows.1/Git-2.43.0-64-bit.exe

@pedrorijo91
Copy link
Member

I recall having downloads with such strange names when they get stuck. if you try to download a big file, and you look at the destiny folder midway, you will usually see a file with random name, which will later be replaced by the final file with the correct filename. could this be the case?

@SalmonBasilCheese
Copy link

I could opened it by just adding ' .exe ' to the last of file name.
ex) rename to "a93c7233-5099-4ce1-8597-efb65113b310.exe", and double-click the file.

@grubbauer
Copy link

Same issue, but I managed to run it. I just put .exe at the end, so it was a93c7233-5099-4ce1-8597-efb65113b310.exe.

@KyleChenpopo
Copy link

@SalmonBasilCheese @grubbauer Thank you! You both save my time! It worked.

@zarlin
Copy link

zarlin commented Dec 13, 2023

Encountered the same issue. Appending the .exe extension works, but is not ideal.

  • OS: Windows 10 x64
  • Browser: Vivaldi 6.4.3160.47 (Stable channel) (64-bit)

@dscho
Copy link
Member

dscho commented Sep 11, 2024

This looks like the same issue as git-for-windows/git#4675 and the root cause is either with Chrome or with GitHub releases, and unfortunately nothing that Git for Windows or git-scm.com can fix.

I did vaguely remember that those problems were addressed, but I did not find any link :-(

In any case, is this still happening? If not, we can close the ticket. If it does, we need to find a better address for this report, and close this here ticket.

@zarlin
Copy link

zarlin commented Sep 11, 2024

I just tested again using Vivaldi (Chromium) on Windows 10 x64, and the download works as expected (normal filename and extension).

I tested with different download links from both https://gitforwindows.org and https://git-scm.com/download/win .

So for my setup it's fixed!

@VladimirBudovsky
Copy link
Author

VladimirBudovsky commented Sep 12, 2024 via email

@dscho
Copy link
Member

dscho commented Sep 12, 2024

Okay, good! Thank y'all for confirming.

For the record, I vaguely remember that some people talked about S3 buckets where the files are stored using UUIDs as names, but that the Content-Disposition header was used to relate the actual file name, and that either a VPN or Chrome or something misinterpreted those headers.

But as it seems to be fixed, let's close this here ticket.

@dscho dscho closed this as completed Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants