Invalid API response from NVIDIA #42
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
help wanted
invalid
low priority
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fyr77/EnvyUpdate#42
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?
The program doesn't work on my end. It opens a gray square and this error prompt shows up.
I'm using the v3.3 downloaded 5 minutes ago from the Releases tab, Windows 11 v22H2 (Build 22621.2283) and my GPU is a GT 1030 manufactured by GIGABYTE.
Tbh, I don't have the intention of updating my drivers just yet since I already did it a few days ago, I just wanted to check if the program was working at all.
Weird, EnvyUpdate seems to detect your GPU as a GeForce GTX 295 - something seems to be wrong with my detection. Does it immediately show this when starting up?
If it is possible, enable logging to file in the options and attach it here. Otherwise, create a file called
envyupdate.log
next to the EnvyUpdate.exe file, this also enables logging.Yup.
Here you go: envyupdate.log
I just released 3.4, which should fix your issue. Please try with that.
Thanks for reporting it, I am surprised no one noticed that until now.
Well, there's certainly a difference between v3.3 and v3.4.
Now on v3.4 the program opens (still as a gray block), something seems to be happening in the background, and then the program just closes abruptly after a few seconds.
https://github.com/fyr77/EnvyUpdate/assets/4485172/6446c4c6-7491-47b1-94e1-cca44926bed9
Here's a log: envyupdate.log
@LOuroboros Interesting, it seems to crash when attempting to show the notification... Could you try running this debug build? Extract all files in the zip please.
EnvyUpdate-Debug-3.4.zip
@LOuroboros I have added an exception handler around the notification code. Please try this build instead if possible.
I tried this version directly, and at a glance, it seems to work 🥳
https://github.com/fyr77/EnvyUpdate/assets/4485172/48758697-e813-4e3b-b725-8032798b1260
I doubt it's needed, but here's the log I generated preemptively when I ran the program just in case: envyupdate.log
Interesting, according to the Log "The notification platform is unavailable." - I did not know this was possible. Have you disable Windows notifications in some manner? @LOuroboros
I'll push this error handler in the next update in a few minutes.
Yes. I tend to disable components and features that I know I will not make use of at all 😅
That's fair. Thanks for the info and the bug report, I find it surprising that no one reported that so far since it must have been there for quite a while. Closing this issue :)