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

Mtga Tool not working #70

Open
AndreaMTG opened this issue Nov 25, 2023 · 4 comments
Open

Mtga Tool not working #70

AndreaMTG opened this issue Nov 25, 2023 · 4 comments

Comments

@AndreaMTG
Copy link

Latest update stopped mtga tool working on my pc, while it was running without any problem with the previous release.
The issue is that it doesn't start at all and windows gives me an error message talking about Virtual Discard Memory with kernel.dll
Hope you'll fix this soon. Thank you to all the devs and goodbye.

@riQQ
Copy link
Contributor

riQQ commented Dec 4, 2023

Which version was the last one working for you? 6.4.1 updated electron from version 13.0.0 to version 27.1.0 (#67). Maybe this is not compatible anymore to Windows 7 anymore as you mentioned using Windows 7 in one of the linked issues.

Electron will end support of Windows 7, Windows 8 and Windows 8.1 beginning in Electron 23.

Source: https://www.electronjs.org/blog/windows-7-to-8-1-deprecation-notice.

@AndreaMTG
Copy link
Author

6.4.1 and 6.4.2 worked fine
6.4.4 started to give this error : "the procedure entry point discard virtual memory could not be located in the dynamic link library kernel32.dll."

@riQQ
Copy link
Contributor

riQQ commented Dec 4, 2023

Looks like your memory about when the error started might be wrong, as the error message is exactly the one caused by Electron dropping support for Windows 7 / 8 etc:

https://stackoverflow.com/questions/77160321/electron-error-the-procedure-entry-point-discardvirtualmemory-could-not-be-loct

@AndreaMTG
Copy link
Author

AndreaMTG commented Dec 4, 2023

Just read what I wrote in the past message. It sounds strange.
Yes, the link explains that, but for a matter of time it's impossible because I sent the message related to the issue the day after I had the problem and 1 week ago 6.4.4 was released as I can see in the release timeline. The next post had "no solution with 6.4.5 patch" title just because it came with 6.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants