Error in installation log for Visual Studio 2013 Update 2 RC can be misleading

Error in installation log for Visual Studio 2013 Update 2 RC can be misleading

Rate This
  • Comments 13

Given many of the exciting announcements and features demonstrated recently at Build 2014, customers are downloading Visual Studio 2013 Update 2 RC. This update is quite a bit bigger than VS2013 Update 1 since it contains many new features. A small number of customers, however, are experiencing problems installing VS2013.2 RC.


While specific symptoms vary, some customers see an error dialog almost immediately or they see warnings after installation completes successfully. In these cases, customers have spotted the following error in the bundle installation log:

[1543:4DC8][2014-04-09T12:00:30]e000: Error 0x80070103: Failed to find product code for given upgrade code.
[1543:4DC8][2014-04-09T12:00:30]i000: MsiProductSearch failed: ID 'EmulatorWP81_Version', HRESULT 0x80070103

This error is not fatal, however. This denotes that a particular search did not find a product installed and was logged improperly (and has been fixed). Normally searching for “Error” in a bundle installation log is helpful (unlike Windows Installer package logs), though we hope you never have the need.

Blocking condition

First check the bottom of the log (tip: Ctrl+End in notepad.exe) for the process exit code. In some cases we’ve seen, the following was logged:

[1543:4DC8][2014-04-09T12:01:15]i007: Exit code: 0x80044000, restarting: No

Error code 0x80044000 is that a condition is blocking install, which is displayed in the error dialog and also found in the log as “Stop Block”. In the cases we have investigated a qualifying product like Visual Studio 2013 Ultimate or Express for Windows was not installed even though Update 1 might’ve installed successfully (Update 1 didn’t properly block installation when a qualifying product was not installed).

[1543:4DC8][2014-04-09T12:00:35]i000: MUX:  Stop Block: NoApplicableUpdates : Update 2 RC does not apply, or is blocked by another condition on your computer.

Some tools like Remote Tools 2013 have their own upgrades and are not primarily serviced by VSUpdate.

If you are sure you installed a qualifying product like Visual Studio 2013 Professional, Premium, Ultimate, Express for Web, Express for Windows, or Integrated Shell, the bundle registration might have been corrupted. Run the install program for any bundles you installed again and re-install or repair the bundle when prompted.

Reboot required

If scripting the installation of VSUpdate, you might get error code 0x80048bc7 which our VS2013 administrator guide documents as, “Incomplete”.

[1543:4DC8][2014-04-09T12:01:15]i007: Exit code: 0x80048bc7, restarting: No

This means that setup has not yet completed but a reboot is required to complete the install. This is common if Hyper-V was not already enabled in Windows and you are installing the Windows Phone 8.1 SDK and emulator.

In this case, restart the machine and setup will resume once you log back in.

More information

VSUpdate applicability depends on bundle information that is written to the registry key for Programs and Features, or simply "ARP". Since VSUpdate is a related bundle that will patch qualifying bundles like those mentioned above, related bundles must be registered correctly. Be sure to install Visual Studio using only the install program

Enjoy all the great new features Visual Studio 2013 has to offer and be sure to check out some of the cool videos!

Leave a Comment
  • Please add 3 and 8 and type the answer here:
  • Post
  • "Windows Phone 8.1 Emulators - ENU  Fatal error during installation." This is the error I'm getting.

    Install cannot continue because some required components failed.

    What do I do....????

    Here's the Screenshot:

  • I'm getting the error as shown in the screenshot.

    It says " Install can't be completed because some required components failed.

    Windows Phone 8.1 Emulators - ENU. Fatal error during installation.


    What do I do....?

  • @Siddharth Ajmera, it would help to have logs. Please run and share the %TEMP%\ on your OneDrive account along with a link to them.

  • I have encountered the 'setup blocked' problem on my dell R14 laptop running win7 64 bit.  My c drive has 17.6 gig free.   My log is here:

  • Hi iam also getting fatal error during vs2013 installation error is microsoft visual c++ reditributable is not installed ( user cancelled the installation . my system is upto date with all the patch updated and while onstalling for first time i was not having space in c drive  so i did cancelled the installation and second time if i run the setup it is giving this error kindly help

  • @rakesh, please run and upload the %TEMP%\ file to a new Connect bug on so we can have a look.

  • I'm trying to install Visual Studio 2013 Ultimate Express on my laptop. I just upgraded it to Windows 10 and it keeps showing me an error saying that the compatibility mode is on and that I should turn it off before trying again. I have tried troubleshooting the compatibility, but no matter what settings I try its still gives me the same error. What should I do?

  • @Bhagya, we have no SKU named "Ultimate Express". Could you tell me the display name on the download page so we can work with Windows to make sure the compatibility database is updated?

  • I'm sorry, I meant ultimate. Its visual studio ultimate 2013 32-bit.

  • @Bhagya, Visual Studio 2013 Ultimate RTM should be correctly shimmed in Windows 10 RTM. Are you trying to install a slipstream version with Visual Studio Update baked in? Could you right-click on the vs_ultimate.exe, select Details, and tell me the file version?

  • The file version is 12.0.21005.13. I downloaded it from my school website. Its from Dreamspark

  • @Bhagya, seems Windows is checking the file name to disable app compat mode. Did you rename the file when you downloaded? What was the file name whether you changed it or not?

    As a workaround, you might rename it to vs_ultimate.exe and that should work around the issue.

  • Yup, that was the problem. Its working now. Thank you!!! :)

Page 1 of 1 (13 items)