Visual Basic 6 Windows Installer message - by vs2015junkie

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 544350 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/24/2010 2:43:41 PM
Access Restriction Public
Primary Feedback Item 542564


If one installs Visual Basic 6 AFTER installing Visual Studio 2010 RC, one is stuck with a Windows Installer loading message the first time the Visual Basic 6 IDE is loaded up.
Sign in to post a comment.
Posted by vs2015junkie on 3/26/2010 at 9:12 AM
I was able to solve this issue by reading this post:

After running the following command as described in the post:

mkdir "%ProgramFiles%\Microsoft Visual Studio 10.0\common7\IDE\FromGAC"

My issue with the Windows Installer loading message for VB6 went away.

Please advise.
Posted by Microsoft on 3/26/2010 at 12:34 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below.
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\

You can get more details about how to get the log files here:

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Posted by vs2015junkie on 3/25/2010 at 9:24 AM
I just tested the installation of Visual Basic 6 if I install it prior to Visual Studio 2010, and the original Visual Basic 6 installation is stuck with a Windows Installer message in this scenario as well.
Posted by Microsoft on 3/24/2010 at 7:26 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you