New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MS Office 2010 crash when open VBE #3855
Comments
First off, please check the %APPDATA%/Rubberduck folder for logs and attach them here. This is to my knowledge the first report of a hard-crash with 2.1.1 |
I bet it's the missing \Plug-ins folder again. Can you verify under the install folder (default %PROGRAMDATA%\Rubberduck) and see if there's a "Plug-ins" subfolder? If not, create it & try restarting the VBE. |
Oh, I see it has \Plugins folder but the problem still exists. Anyway, I try to install with Office 2016, no problem in here. So, thanks for your help. |
@datvq I'm wondering - did you have 2010 and 2016 installed at the same time when you first tried to install Rubberduck on the 2010? |
@bclothier Right, I have 3 devices, in my company and home with diffirent versions. |
Sorry, I should be more clearer --- were they on the same machine? It sounds like not. |
Yes. One machine have mso 2016 and base on Windows 10 build 1709 and that ok. One another, mso 2010 on Windows 7 SP1, it has problem. |
Hmm. I am also assuming you can't get to the log since you can't change the setting because it crash. So if you could please, save the below as at the path Also, another thing to check is whether you have other VBE addins and if so, to try and disable them all and see if you can load with only Rubberduck enabled.
|
Closing the issue because we already released 2.2 which introduced changes to installation which may or may not alleviate the reported issue. I cannot reproduce this with recent versions of installer. If this is an issue still, feel free to reopen. |
After I installed Rubberduck.Setup.2.1.1.exe, I open Excel (version 2010) and open VBA (Alt+F11). So, Excel crash. What should I do to solve that problem?
The text was updated successfully, but these errors were encountered: