Share via

Long delay loading Excel Solver Add-In after multiple reinstallations

Anonymous
2022-04-18T16:45:40+00:00

Any attempt at using solver requires a lengthy delay for the add-in to load. I'm using Office 365 on Windows 10, Ryzen 9, RTX 3060 laptop. I followed various rebooting reinstalling steps including uninstalling through the control panel and then uninstalling through Microsoft Support and Recovery Assistant with reboots along the way for good measure. I did multiple quick repairs and full repairs of Office 365 and even ran a "Temp File Deleter" in between reboots and uninstallation to try to clear as much as possible. Active X is confirmed enabled (prompt).

Excel opens quickly in safe mode or if the solver add-in is disabled. I can load solver using the VBA window and manually browsing to the Solver XLAM file (Tools -> References -> Browse) but it takes many minutes to load. Once loaded, I can use solver and add it in through the typical add-in options menu. However, if I do add it in and close excel, so it is enabled for the next load, Excel will again not load getting stuck on "Solver.XLAM" for many minutes. If I load solver through VBA and do not add it through the options menu, thus disabled at the next load up, Excel boots up automatically.

Attempting to add Solver through the options menu or having Solver enabled at start up also stalls Excel for a very long time. Given I have a new computer, it isn't a performance issue. After testing some more, I realize that once Solver loads, I can easily disable it and enable it in that instance. However, once I close and open excel it again stalls for a long time (~5 minutes).

The issue started after uninstalling Oracle Crystal Ball but initial stalls started after installing Oracle Crystal Ball. Are there any tools that can diagnose Excel Add-Ins specifically or cleanup the back end? I suspect it may have to do with windows registry but wondering if there are other potential solutions.

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2022-04-19T01:57:32+00:00

    Hello Rolando,

    Welcome to Microsoft Community and appreciate your time taken for sharing detailed information. I could share with you some of my thoughts on this issue.

    If this involves the Windows registry, it would be a troublesome thing. Because changing the registry may cause a larger problem. I want to ask what your version of Office is like, have you ever tried to update your Office? Judging from your description, it is possible that it is a problem caused by a third-party file. You could try do a Clean Bootand see if the problem is still the same later.

    (Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background program is interfering with your game or program and to isolate the cause of a problem. 

    These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get you back on track.)

    You should have tried Safe Mode, and if it is true that after disabling this add-in, Excel opens quickly and normally. Then the problem may be that the external third-party file caused the add-in to start slowly, if you do a clean boot, Excel is still such a problem, indicating that it is possible that the add-in caused the startup time is too long. But if you start up via VBA very quickly, it's possible that your VBA code would run faster than the menu bar provided by Microsoft.

    Feel free to post back if you need any further assistance.

    Best Regard,

    Kevin | Microsoft Community Support Specialist


    *Beware of scammers posting fake support numbers here."

    *Kindly Mark and Vote this reply if it helps, as it will be beneficial to more community members reading here.

    *If your problem is not solved, you could reply to the post again and we would continue to provide technical support for you.

    Was this answer helpful?

    0 comments No comments