mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #638] [extras] not possible to download SharpDx #520
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#520
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Apr 15, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/638
issue does not exhibit with downloads of FFmpeg | Gifski
@NickeManarin commented on GitHub (Apr 15, 2020):
Strange, you can download manually from here:
https://github.com/NickeManarin/ScreenToGif/wiki/Help-▪-FAQ-▪-Unable-to-download-SharpDx
But if you are able to download Gifski, the download of SharpDx should work too.
@ghost commented on GitHub (Apr 15, 2020):
The manual download worked.
Seeing the app error it might be caused by a node's GroupPolicy -> ECC curve order (policy setting determines the priority order of ECC curves used with ECDHE cipher suites.) and only the following curves are permitted in this order:
The node has also TLS1.3 enabled which is not by default via this registry tree:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client@NickeManarin commented on GitHub (Aug 29, 2020):
@n8v8R Can I do anything within ScreenToGif to fix it? Or is it something that you configure it in your OS?
@ghost commented on GitHub (Aug 29, 2020):
Did not re-test since the manual download but now have, meanwhile the node's OS upgraded to v2004 b19041.450 and STG 2.26.1, and the issue does not exhibit.