WACUP
Preview Build Discussion => Preview Build Discussion => Resolved Issues => Topic started by: pimento on October 07, 2019, 06:40:02 AM
-
Twice now I've had issues when auto-updating WACUP, the first time I just uninstalled it and did a fresh install of the new build, now it's happening again. It's worked fine on one PC, but on this one not so much. I'm a local admin (and the only user) on both machines and they're both running Windows 10 at the same patch level.
Basically it says that there's an access error trying to write to winamp.exe. Last time I renamed it and it went further, but complained about a couple of other files instead. It's installed in the default installation folder.
-
I just launched it again and it generated a crash log that I've sent off.
-
Have you restarted your computer?
It seems as though a dead process (that's somehow still active) seems to be locking access to them
-
It gets restarted every day, not sure what process would affect it.
-
I don't know why it happens other than the OS / antivirus software messing up as seems to be the case from the others who've seen jt. There's nothing special I do to the files nor would intentionally locking them from update make any sense to do. I'll have a look at the crash report shortly.
-dro
-
I've had a look at the crash report from the older build 4264 & something is blocking it from loading some of the core supporting dlls needed which causes the crash.
-dro
-
Well, I've no idea what was locking it - the only AV on there was the windows default one and there wasn't any other file access type watchdog on there, but that machine died last week, so... let's see how it goes on the new one.
-
*fingers crossed*
-dro
-
I've a hunch that this was related to the previous issue I had where WACUP wouldn't load sometimes - I can report that that issue has gone away since the device replacement, and given than I'm confident that the updating issues will be resolved as well. Seems like there was something crappy going on in the old machine - I should have tried that windows reset thing but hey, it died anyway so oh well.
-
Well its not good about h/w failing but at least you're in a better position now :)
-dro