locked
Building Visual Studio 2010 project triggers "Please wait while Windows configures Visual Studio 2013" RRS feed

  • Question

  • The same situation as similar threads (like the VB6 one) but different details.

    I have a visual studio 2010 solution with 5 projects:

    1. an outlook add-in.
    2. a windows forms app that automates outlook.
    3. a placeholder project with manifest and VSTO for add-in.
    4. a 32bit setup and deployment for add-in.
    5. a 64bit setup and deployment for add-in.

    Whenever I build the project in Visual Studio 2010, I get the annoying "Please wait while Windows configures Visual Studio 2013 Professional" ... I've let it finish dozens of times, but it keeps popping up.

    Fiddling with build configurations I've discovered that it only happens when the Setup and Deployment projects are compiled.

    So, how can I appease Visual Studio 2013 so it will stop this nonsense?


    This signature unintentionally left blank.


    • Edited by Nick F. _ Friday, December 27, 2013 8:43 PM clarification
    Friday, December 27, 2013 1:52 PM

Answers

  • I resolved the problem on my own using brute force.

    I uninstalled both Visual Studio 2013 and Visual Studio 2010.

    Then I only reinstalled Visual Studio 2010 and now I can do my work without being told Visual Studio 2013 is broken every time I build.


    This signature unintentionally left blank.

    • Marked as answer by Nick F. _ Tuesday, January 14, 2014 7:03 PM
    Tuesday, January 14, 2014 7:03 PM

All replies

  • Hello Nick F.

    I just find a thread which is related to your problem so please read the following:

    "That's what happens when Windows Installer does a repair. ( aka Resilency ).
    Visual Studio is accessing a Key File ( probably COM server ) of one of the
    installed components and MSI is detecting it as not properly installed and
    trying to fix it before returning control to visual studio to actually use the
    component.

    You'll have to use Event Viewer to know the product and component ID being
    detected as broken and then use tools like Orca to find out what physical file
    that is. Solve that problem and the repairs should go away."

    Could you please give this solution a try? Just check your event log and check which component is causing this issue. Then use Orca to replace the file which needs repaired.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Proposed as answer by TheeBOBJohnson Monday, January 20, 2014 11:12 PM
    Monday, December 30, 2013 5:04 AM
  • Thanks Barry.  I appreciate that your answer was more than (again like the VB6 thread) "not supported"

    I looked in the event log and see the following two warnings:

    Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu' failed during request for component '{CBB86C09-565A-43CF-9120-9D45AE3374CA}'

    Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed.  The resource 'C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.

    I'm not familiar with Orca so I'm not quite sure what do do next.  I tried running repair as an admin, but it still wants to fix VS 2013 when I'm trying to build VS 2010..


    This signature unintentionally left blank.

    Tuesday, December 31, 2013 5:04 PM
  • Hello Nick,

    When I was post that post, I assume the problem is pending on your setup project. So I ask you to check the error from event viewer when you are running your setup project. The warnings may not what I want. It is because 'Visual_Studio_Professional_x86_enu'  is Visual Studio exe. However, it is not sure from my side. Please run this tool first: http://blogs.msdn.com/b/astebner/archive/2005/07/01/434814.aspx and find the specific product name using the following component(Ctril+F) :

    {9C593464-7F2F-37B3-89F8-7E894E3B09EA}

    CBB86C09-565A-43CF-9120-9D45AE3374CA}

    {E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}

    Please list the full info for me here, for example:

    "Microsoft .NET Framework 2.0 Beta 2
     Product code: {7A1ADD0C-17F3-47B8-B033-A06E189C835D}
     Product state: (5) Installed.
     Package code: {856D48D2-6F94-466D-9732-534DB5854FB3}
     Version: 2.0.50215"

    Then about that Orca, you may have to read this page http://support.microsoft.com/kb/255905/en-us and please notice that this tool needs Windows SDK installed on your OS. Orca can replace the files you are using in your setup project, what you need is to run your installer from orca. However, can you find errors in your event viewer? Not just those warnings? The info is still lack now.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.



    • Edited by Barry Wang Thursday, January 2, 2014 9:50 AM
    Thursday, January 2, 2014 9:48 AM
  • Only one of the GUID's appeared in the output file

    Microsoft Visual Studio Professional 2013
    Product code: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
    Product state: (5) Installed.
    Assignment: per machine
    Package code: {81283AAD-470A-438B-ACC6-B6CA4C82997A}
    Version: 12.0.21005
    Publisher: Microsoft Corporation
    Language: 1033
    Installed from: C:\ProgramData\Package Cache\{9C593464-7F2F-37B3-89F8-7E894E3B09EA}v12.0.21005\packages\professionalcore\Setup\
       Package: vs_professionalcore.msi
    Help link: http://go.microsoft.com/fwlink/?LinkId=133405
    Instance type: 0
    Local package: C:\Windows\Installer\5c2ea7b.msi
    Install date: 2013\11\07
    0 patch packages.

    There are no installer errors that I can see, only the two warnings repeated 3 times between some informational messages.

    BTW, I can reproduce the problem by doing the following steps.

    1. Launch Visual Studio 2010
    2. File | New | Project
    3. Pick Other Project Types | Visual Studio Installer | Setup Project
    4. Keep default name and location.  Click OK
    5. Build | Rebuild Solution

    At this point I get the pop-up that Visual Studio 2013 needs repair, and it repeats every time I build/rebuild.



    This signature unintentionally left blank.

    Thursday, January 2, 2014 2:07 PM
  • Sorry Nick for the late follow up.

    Would you mind to send full logs to me with the following steps:

    Please use  http://aka.ms/vscollect  to gather the installation logs. After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/  and share the link here.

    And I forget to paste the workaround I found to make this issue clear:

    http://stackoverflow.com/questions/10215458/installed-shortcut-causing-install-to-rerun-visual-studio-2010 

    We may see that 9C593464-7F2F-37B3-89F8-7E894E3B09EA is actually Microsoft Visual Studio Professional 2013 However it is not what we need. That {CBB86C09-565A-43CF-9120-9D45AE3374CA} and {E3FF99AA-78B9-4A06-8A74-869E9F65E1FE} are what we need. I will help you check your logs instead.

    Regards,

     



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 9:45 AM
  • Add a post, do you have Visual Studio 2010 Sp1 installed on your OS? I seems to reproduce this issue on a Win 8 test machine.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 12:23 PM
  • I believe the answer is yes for SP1, but I will have to re-check to be sure.  I'll do that in the AM along with gathering the logs.

    This signature unintentionally left blank.

    Wednesday, January 8, 2014 11:01 PM
  • Yes, I've got SP1, and here's the link to the collected logs

    This signature unintentionally left blank.


    • Edited by Nick F. _ Tuesday, January 14, 2014 7:00 PM removed skydrive link
    Thursday, January 9, 2014 4:40 PM
  • I resolved the problem on my own using brute force.

    I uninstalled both Visual Studio 2013 and Visual Studio 2010.

    Then I only reinstalled Visual Studio 2010 and now I can do my work without being told Visual Studio 2013 is broken every time I build.


    This signature unintentionally left blank.

    • Marked as answer by Nick F. _ Tuesday, January 14, 2014 7:03 PM
    Tuesday, January 14, 2014 7:03 PM
  • I am having the exact same issue with the same Product and Component IDs in my event log.  Did you ever try reinstalling VS 2013? I need both versions installed side-by-side.
    • Edited by scuba6388 Friday, March 14, 2014 3:38 PM
    Friday, March 14, 2014 3:34 PM
  • Yes, eventually I reinstalled 2013 and the problem (so far, knock on wood) has not returned.

    This signature unintentionally left blank.

    Saturday, March 15, 2014 3:01 AM
  • I get the same error and the StackOverflow link you add says check the Application Eventlog for MsiInstalelr warnings. The warning that I found that seemed significant was

    Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed.  The resource 'C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.

    And that path does not exist, I'm using Windows 7 64 bit.

    i ran msiinv and got a log and unexpected error: 1605 () but within the log i found

    Microsoft Visual Studio Professional 2013
        Product code:    {9C593464-7F2F-37B3-89F8-7E894E3B09EA}

    but i cannot find the guid E3FF99AA-78B9-4A06-8A74-869E9F65E1FE in the log file generated

    any ideas, is it a Vs 2013 extension?

    Edit

    --

    I have tried this solution to create the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ and it appears to have worked so far.

    http://social.msdn.microsoft.com/Forums/en-US/407058cd-22c5-44b7-bd0e-0571fdd2fc69/launching-vb6-editor-after-installing-visual-studio-2013-results-in-please-wait-while-windows?forum=vssetup

    • Edited by tdyen Friday, March 21, 2014 2:41 AM
    • Proposed as answer by Sayoung Han Friday, September 26, 2014 5:15 AM
    Friday, March 21, 2014 1:00 AM
  • I know this is old but tyden's fix worked for me by creating the folder:  C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC

    Thank you tyden!!!


    Thank you,

    Nick Metnik

    Please mark my response as helpful if it has helped you in any way or as the answer if it is a valid solution.
    Blog
    LinkedIn

    Monday, April 14, 2014 11:08 PM
  • I ran into this same problem today with failed requests for component '{CBB86C09-565A-43CF-9120-9D45AE3374CA}' causing VS2013 to repair itself whenever I built a deployment project in either VS2008 or VS2010.  The repair did not appear to do anything to resolve the issue, and would come up again on the next build.

    Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{66ED28A0-BA9C-4592-A347-1933652DDEB7}' failed.  The resource 'E:\' does not exist.

    Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu' failed during request for component '{CBB86C09-565A-43CF-9120-9D45AE3374CA}'

    In my case, "E:\" is a DVD drive that does not have a disk in it.  Putting a disk in the drive makes the error go away, until I remove the disk later.  

    Using the DumpComponentsList .VBS script from this page, I managed to track the component down to this:

    {CBB86C09-565A-43CF-9120-9D45AE3374CA} is used by:
         Microsoft Visual Studio Professional 2013 {9C593464-7F2F-37B3-89F8-7E894E3B09EA} at C:\Program Files (x86)\Common Files\Microsoft Shared\MSI Tools\mergemod.dll

    Once I knew which DLL was causing the problem, I simply did the following at an administrative command prompt:

    regsvr32 "C:\Program Files (x86)\Common Files\Microsoft Shared\MSI Tools\mergemod.dll"

    Once done, the next rebuild triggered one final VS2013 repair.  From that point on though, I've been able to build deployment projects in either VS2008 or VS2010 without error.

    Hope this helps someone else.  I've been struggling with this issue off and on on various machines for a while now, and haven't been able to resolve it until now.


    Richard Glidden - Brock Solutions - www.brocksolutions.com - Engineering Solutions that Perform.

    Tuesday, November 11, 2014 6:01 PM
  • Tyden - thanks from another Nick.  creating the empty folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ worked for me too

    Nick

    Tuesday, June 2, 2015 9:32 AM
  • Thanks Tyden!!   This worked for me as well :)
    Tuesday, December 13, 2016 12:51 PM
  • 3 Nick's out of 6 'Me too's'  Is this a pattern ;-)


    This signature unintentionally left blank.

    Wednesday, December 14, 2016 11:18 PM
  • Thanks tdyen!   Years later and another programmer who used this solution to fix a terrible problem.   Create the directory worked!

    I wonder how long it would have taken me to figure that out before reinstalling vs2013.

    dc

    Monday, March 4, 2019 11:38 PM