mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 23:55:57 +03:00
[GH-ISSUE #1299] [Bug] Could not find file 'C:\WINDOWS\SysWOW64\gifski.dll'. #952
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#952
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 @allrobot on GitHub (Mar 29, 2024).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1299
Originally assigned to: @NickeManarin on GitHub.
Describe the bug

To Reproduce

Actually, it's already in this folder:
This is what happened after the update.I don't understand why the updated software has arbitrarily changed the address of the DLL files. Previously, the software used DLL files located in the ScreenToGif path, not in the SysWOW64 path.
@pawlos commented on GitHub (Mar 29, 2024):
@allrobot looking at the code, it seems that it still uses the configuration value to check where the DLL is located. It seems like it was like that for a very long time. Is your Gifski location setting in Extras points to some other directory?
@allrobot commented on GitHub (Mar 30, 2024):
Perhaps without. The entire computer only has the "gifski.dll" stored in the "ScreenToGif" directory. Although I resolved the issue by copying this DLL to the "C:\WINDOWS\SysWOW64" directory.
If copying the DLL to that directory is considered a resolution, you can close with the comment "Resolved by copying the DLL to the specified directory."
@pawlos commented on GitHub (Mar 30, 2024):
I have no option to close the ticket. Still I'm surprised about that issue. As a solution I would just change the location in the settings to point to the file and not copy the file to SysWOW64 directory
@allrobot commented on GitHub (Mar 30, 2024):
Perhaps a few years ago, I had set the specified directory for the DLL in the software settings? My memory is not very good, so it's possible that it was my mistake.