MS Word & Visual Basic Environment

from Stardock Forums

When I have Groupy turned on and I open an MS Word attachment from Outlook (i.e., double-click on it), I get the following error:

"The Visual Basic environment could not be initialized."

When I turn off Groupy and attempt to open the same Word file from Outlook, it opens without any error. So it is definitely Groupy causing the problem. The error mentions something about running out of memory, but I have 32GB of RAM in a very high-end laptop with Win10 Pro x64 installed.

Any ideas how to fix this?

groupy
4,422 views 5 replies
Reply #2 from Stardock Forums Top

I went through the procedure above, and the VB error still shows up. What next?

Galactic Civilizations III
Reply #3 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

When I have Groupy turned on and I open an MS Word attachment from Outlook (i.e., double-click on it), I get the following error:

"The Visual Basic environment could not be initialized."
End of quote

I will mention it ot the Devs but I am not seeing the same here with Office 365 (is that what you have):

https://cdn.stardock.us/support/uploads/2019-08-27_11-41-58.mp4

Is there anything special about the document you are opening?  If you disable your AV software, does it still happen?

Sean Drohan
Stardock Support Manager

 

Reply #5 from Stardock Forums Top

I turned off antivirus and still got the same VB error. So, I tried to narrow down the problem by opening .doc and .docx files from both File Explorer and Outlook.

I double clicked on two .doc and .docx files from File Explorer, and no VB error was generated. Interesting, so I thought I was onto something.

Then I e-mailed those same two files to myself, double clicked on them in Outlook and no VB error was generated there as well. Very strange.

I then tried double clicking on every one of those files multiple times and the error never showed up. This problem showed up a week or so ago, but I rebooted, it went away, so I just ignored it. It came up again yesterday, so I think it is an intermittent problem. I wonder if there is some software garbage collection that is not working that builds up over time?

Hope this data helps you guys find it.