Update loop with 560.70 #49
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#49
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?
Seems to be update looping on Windows 11 Pro 23H2 22631.3880 when trying to install driver 560.70. I downloaded and hit install, and when it returned to EnvyUpdate, I was immediately notified about the same update. The old driver is still the one installed. Seems like the driver install is crashing and EnvyUpdate doesn't notice? I was able to run the 560.70 driver installer manually and it installed successfully.
Oh, maybe they actually changed the format now. I am not home for the next few days, but I will investigate asap.
Some more info, fwiw:
Oh, weird. I did just check on my laptop - the driver structure looks normal to me. Did you use EnvyUpdate successfully before on the W11 machines? @jathek
Yes, the previous driver was installed fine with EnvyUpdate. I will keep an eye out the next time a driver is pushed. Maybe it was a Windows fluke?
Unfortunately I was unable to replicate the issue on my machine... Did it work for you after the second attempt or is it "stuck"? @jathek
It was stuck and didn't work. I installed the driver manually by running the downloaded exe, and afterwards EnvyUpdate detected that the new driver was installed. I will see if it happens again when the next driver update happens.
Following up on this. Driver version 560.81 released recently, and I was able to update to it with EnvyUpdate on a W10 machine (bare metal) and two different W11 machines (VMs). So I think it was some odd crash or bug specific to 560.70. Going to close this as a fluke, for now.