[GH-ISSUE #1299] [Bug] Could not find file 'C:\WINDOWS\SysWOW64\gifski.dll'. #952

Closed
opened 2026-02-26 09:33:08 +03:00 by kerem · 4 comments
Owner

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
image

To Reproduce
Actually, it's already in this folder:
image

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.

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** ![image](https://github.com/NickeManarin/ScreenToGif/assets/43485379/41aca099-fc5f-41ed-9380-ce55d3a53ea5) **To Reproduce** Actually, it's already in this folder: ![image](https://github.com/NickeManarin/ScreenToGif/assets/43485379/b9d73234-d0ea-4d44-8f18-1385eb6352bb) 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.
kerem 2026-02-26 09:33:08 +03:00
Author
Owner

@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?

<!-- gh-comment-id:2027401452 --> @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?
Author
Owner

@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."

<!-- gh-comment-id:2027897093 --> @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."
Author
Owner

@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

image

<!-- gh-comment-id:2028022038 --> @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 ![image](https://github.com/NickeManarin/ScreenToGif/assets/1296768/46930932-644a-4025-bb46-53c2b49e4c26)
Author
Owner

@allrobot 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

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.

<!-- gh-comment-id:2028031853 --> @allrobot 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 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#952
No description provided.