Jump to content
LaunchBox Community Forums

Can no longer start Launchbox or revert to previous update


Taamo

Recommended Posts

After trying to update to the new beta version of Launchbox, I got an error saying it cannot remove the "Accessibility.dll". It repeats this for every dll file in the Core folder it seems. I cancelled the installation because of this, it said it rolled back, however I can no longer launch Launchbox now. It does the startup loading bar then instantly closes, Launchbox never actually starts. I tried going into the update folder to rollback to the last beta, however the exact same issue happened, unable to remove/replace the dll files. I've never had this issue before. Any idea what could be causing this and how to fix it? I will provide a picture of the error pop up tomorrow if needed.

Link to comment
Share on other sites

39 minutes ago, Taamo said:

After trying to update to the new beta version of Launchbox, I got an error saying it cannot remove the "Accessibility.dll". It repeats this for every dll file in the Core folder it seems. I cancelled the installation because of this, it said it rolled back, however I can no longer launch Launchbox now. It does the startup loading bar then instantly closes, Launchbox never actually starts. I tried going into the update folder to rollback to the last beta, however the exact same issue happened, unable to remove/replace the dll files. I've never had this issue before. Any idea what could be causing this and how to fix it? I will provide a picture of the error pop up tomorrow if needed.

So after several more attempts, several times restarting my PC, and still trying to rollback to a previous update, it finally worked and my launchbox is opening again, I rolled back to Update 13.2 successfully this time, for some reason. That said, no idea what caused this still or why it suddenly worked now, so if anyone has any ideas I would love to know to avoid that kind of thing in the future. Thank you!

Link to comment
Share on other sites

8 hours ago, livemoonkey said:

Why is no one answering this??? It's happening too often than talked about.

Answer what? The users was able to get up and running. Might not have been a LB issue. Could have been something specific to his pc. 

Link to comment
Share on other sites

  • 4 weeks later...
On 4/11/2024 at 6:23 AM, Retro808 said:

Answer what? The users was able to get up and running. Might not have been a LB issue. Could have been something specific to his pc. 

This happened to me again during trying to install the newest beta, so while it may be a PC issue, it may also be an issue worth looking into. Once again the dlls in the Core folder it could not seem to replace, forcing me to cancel the installation of the new version, and just like last time, I can no longer open Launchbox. I successfully updated to the newer version with the last update, yet this one did the same thing as version 3. Any ideas what could be happening here?

Link to comment
Share on other sites

10 hours ago, Taamo said:

This happened to me again during trying to install the newest beta, so while it may be a PC issue, it may also be an issue worth looking into. Once again the dlls in the Core folder it could not seem to replace, forcing me to cancel the installation of the new version, and just like last time, I can no longer open Launchbox. I successfully updated to the newer version with the last update, yet this one did the same thing as version 3. Any ideas what could be happening here?

Fyi, this was once again fixed by restarting my PC a couple times and eventually it worked.
I did some testing into this and it appears to be related to the automatic closing process of an update. It is not properly closing Launchbox or something of that nature, despite not being in the system tray or running, there will still be a singular launchbox buried deep in my Task Manager that isn't using any resources, for some reason. The installer doesn't seem to actually fully close Launchbox essentially, resulting in errors. This is my guess, anyway, as doing a fresh restart of my computer where launchbox is never opened first is the only way I've fixed the issue before and now. Maybe some useful info to give to the dev team for recreating the issue?

Link to comment
Share on other sites

On 4/11/2024 at 3:23 AM, Retro808 said:

Answer what? The users was able to get up and running. Might not have been a LB issue. Could have been something specific to his pc. 

This is an on-going issue LaunchBox is not fixing (answering to).  It is NOT an isolated issue. If you spend a little bit of time searching, you'd know that.  No, not everyone has this issue. But As I said, it's happening too much to ignore. Because one person rebooted their pc and temporarily fixed it is not an answer.  I've "fixed" it as well.  Then days or weeks later, it randomly happens again and it doesn't fix unless I fully reinstall LB and all of it's dependencies.  WE SHOULD NOT BE HAVING TO DO THIS. 

Link to comment
Share on other sites

3 hours ago, livemoonkey said:

This is an on-going issue LaunchBox is not fixing (answering to).  It is NOT an isolated issue. If you spend a little bit of time searching, you'd know that.  No, not everyone has this issue. But As I said, it's happening too much to ignore. Because one person rebooted their pc and temporarily fixed it is not an answer.  I've "fixed" it as well.  Then days or weeks later, it randomly happens again and it doesn't fix unless I fully reinstall LB and all of it's dependencies.  WE SHOULD NOT BE HAVING TO DO THIS. 

My response to that post in no way, shape, or form insinuated no one else has had this issue. It was quite frankly a direct response to a direct question stating it might have been in this user's case a unique build issue since at the time of my post the user only advised after several reboots it worked. We have seen many ways the install or even a reinstall has been a LB build issue and an issue unique to a user's pc. Even seen overzealous antivirus cause this issue.  

3 hours ago, livemoonkey said:

 If you spend a little bit of time searching, you'd know that.   

How about you spend a little less time assuming you know what I do and how much time I spend on this forum researching. That type of attitude is not needed nor welcomed. 

Now if you want to provide more details to this issue that you are experiencing it can be relayed to the team. You state you have "fixed it as well" so what did you do to fix it. It might lead to the devs understanding why it is affecting sporadic users. 

Link to comment
Share on other sites

2 hours ago, Retro808 said:

My response to that post in no way, shape, or form insinuated no one else has had this issue. It was quite frankly a direct response to a direct question stating it might have been in this user's case a unique build issue since at the time of my post the user only advised after several reboots it worked. We have seen many ways the install or even a reinstall has been a LB build issue and an issue unique to a user's pc. Even seen overzealous antivirus cause this issue.  

How about you spend a little less time assuming you know what I do and how much time I spend on this forum researching. That type of attitude is not needed nor welcomed. 

Now if you want to provide more details to this issue that you are experiencing it can be relayed to the team. You state you have "fixed it as well" so what did you do to fix it. It might lead to the devs understanding why it is affecting sporadic users. 

Hey there.. "moderator".   If you noticed I quoted "fixed" as oviously implied, you need to keep rebooting and re-installing just to have it temporarily "fixed.  You need to re-read my response.  This is a direct answer to a direct response.  You just "assumed" that I made an assumption.  You asked "Answer what".   So I answered. If you're going to get your feelings hurt over some vowels and syllables, you might not want to continue to be a 'moderator'.  If these issues were addressed in a timely manner, we wouldn't be here.  Your response's attitude, as a "moderator" is definitely not welcomed by the community.   Either way.  If you're going to help the issue, do so.  Otherwise you're assistance is useless.

Link to comment
Share on other sites

@livemoonkey I do not need to reread anything. You made an assumption clear as day. Has nothing to do with feelings getting hurt and everything to do with keeping negativity and poor attitudes out of our forum. Constructive feedback is always welcomed. Let's move on from this. Any more responses not involving the actual issue will be deleted. 

Link to comment
Share on other sites

8 hours ago, livemoonkey said:

Your response's attitude, as a "moderator" is definitely not welcomed by the community.

Actually it is welcomed by most, as whining and fighting with others over perceived issues while providing absolutely no information on what your issue actually is whilst throwing out comments like "If these issues were addressed in a timely manner, we wouldn't be here" helps no one at all. I suggest if you actually want the issue you are having investigated you provide information when asked to, or better yet logs after the issue occurs, nobody can just guess as to your issue.

Also its worth noting that just because your symptoms seem the same as the other user's it doesn't mean that cause also is, which is why details and information are important to be provided if you actually want some sort of resolution to your issue, if indeed it is on the Launchbox side and not specific to your hardware or programs you have installed.

Link to comment
Share on other sites

19 hours ago, neil9000 said:

 

@Retro808Sorry for @ just wanted to be sure you saw my replies, it might be useful information. For the record as well, I don't have external antivirus software effecting anything, Launchbox is allowed through any firewalls or things of that nature, etc. The PC is also not old and is quite a powerful one so I don't think its related to any issues like that. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...