mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #234] Error message when accessing Editor! #194
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#194
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 @slava-uxd on GitHub (Jan 12, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/234
Originally assigned to: @NickeManarin on GitHub.
A few days ago everything worked fine. But after recent Windows Update ScreenToGif 2.11 does not allow me to enter Editor. It crashes with an error message.
ScreenToGif Raw Error.txt
Windows 7 x64
@NickeManarin commented on GitHub (Jan 12, 2018):
Can you send me the full log? It should be inside a folder structure like "ScreenToGif/Logs" on the same folder where the app is located or inside the documents folder.
If you don't find that folder and the logs, can you press the button "Open Inner Exception" and copy-paste it here?
@slava-uxd commented on GitHub (Jan 12, 2018):
Ofcourse. All the info I can find:
Parent error window looks like this:

"Open Inner Exception" gives this:

Paste:
The log from "ScreenToGif/Logs"
18_01_12.txt
Both portable and installed version have this. Deleting settings file and letting ScreenToGif generate a clean one does not help.
@NickeManarin commented on GitHub (Jan 12, 2018):
Oh, thank you for the fast reply. :)
I was reading the messages that were sent by the feedback tool and I noticed that I've already got a report about this same issue.
So, this is basically an issue with the latest update of .Net Framework (January 2018, KB4074906).
The only way to fix it is by uninstalling that faulty update.
You can read more about this issue on this page:
https://github.com/dotnet/announcements/issues/53
@slava-uxd commented on GitHub (Jan 12, 2018):
@NickeManarin Thanks for the find!