[FIXED | NUMEROUS CHANGES MADE] WACUP won't start

[Deacon]

I have this problem too, so I've gone back to normal winamp until it's sorted.
Just seems to occur randomly. Does open every now and then. Normally use the quicklaunch or desktop shortcut to open it.

[dro]

Deacon: what build were you using it was it any of the recent builds ?  If there was a way for me to quickly replicate the issue then I would fix it but as I'm honestly struggling to replicate this whilst it happens so consistently for others is really leaving me stumped as apart from the quirks I know off, there 's no reason when just doing a straight shortcut load without any additional parameters / files being passed for it to lock-up / not load. Unless there's something like the A/V present that's blocking the process loading.

-dro

[Deacon]

Deacon: what build were you using it was it any of the recent builds ?  If there was a way for me to quickly replicate the issue then I would fix it but as I'm honestly struggling to replicate this whilst it happens so consistently for others is really leaving me stumped as apart from the quirks I know off, there 's no reason when just doing a straight shortcut load without any additional parameters / files being passed for it to lock-up / not load. Unless there's something like the A/V present that's blocking the process loading.

-dro

I’ve been using various builds from November or so, and it’s been an issue with every build. Just grown a bit tired of it for now!
I’m using eset antivirus but I’ve never had any problems with it making problems with any other apps, and get no notifications.

[dro]

I really wish you'd have said something to me at the time unless I'm just not matching up the forum account to email / discord messages as I'd not been aware of consistent failure to start issues prior to putting out the public preview builds

I'll up my attempts to try & determine what's going wrong & even hopefully replicate the issue though so far none of my test setups show a loading failure

-dro

[Deacon]

I really wish you'd have said something to me at the time unless I'm just not matching up the forum account to email / discord messages as I'd not been aware of consistent failure to start issues prior to putting out the public preview builds

I'll up my attempts to try & determine what's going wrong & even hopefully replicate the issue though so far none of my test setups show a loading failure

-dro

Sorry about that. I was more assuming it was my computer or something, but done a fresh install and and still the same. I’ll have a faff about with it at the weekend myself and see if I can work out anything.

[pimento]

In my case I don't have any AV outside of what's built into windows 10. At this stage I can't think of any additional factors that might be affecting things, outside of perhaps being that it's more likely to happen if I don't open WACUP up until much later in the day.

[dro]

@Deacon: I've split your new posts into a thread that I've moved into the beta discussion forum due to some of the data that's been posted.

@pimento: that's interesting if it's better later in the day. though can you have a look in the system event viewer & see if there's any winamp/wacup reported errors (I've a feeling that what Deacon has posted before I split the posts might be the same sort of cause of issue).

-dro

[Deacon]

Cheers. Hopefully we can work this out!

[pimento]

@Deacon: I've split your new posts into a thread that I've moved into the beta discussion forum due to some of the data that's been posted.

@pimento: that's interesting if it's better later in the day. though can you have a look in the system event viewer & see if there's any winamp/wacup reported errors (I've a feeling that what Deacon has posted before I split the posts might be the same sort of cause of issue).

-dro

Sorry, I explained badly, it's more likely to not open later in the day. I just tried it now and it's failing to open, I had thought perhaps it was related to being docked but I'm on a work trip so no dock here. Anyway, the first time it started the two background tasks as usual and didn't load, I killed them and tried again, that time it didn't even load the tasks but I got two entries in the Application log (nothing in the system log) and then I tried again and it was back to the two background tasks and nothing else. I've attached the details from the two events here.

[Juanus]

Sorry if I missed this before.
But what version of windows are you using?
And if you are on Windows 10, which update are you on?

[pimento]

Windows 10 pro 64-bit 1809 on a Surface Pro 3.

[dro]

It's the same bad_module_info error that Deacon is experiencing. The temporary solution for that seems to be just running as an admin all the time (which really isn't ideal). I've got to make a debug build to try & work out where the loading failure then happens as it running under admin but not a normal user is somewhat baffling.

-dro

[pimento]

I'm happy to run a debug build for a time if you would like more data on it, just let me know! In the mean time I'll continue with launching it as admin when necessary.