Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

How to fix compatibility mode error that can appear when installing Windows Phone Developer Tools or Visual Studio 2010

How to fix compatibility mode error that can appear when installing Windows Phone Developer Tools or Visual Studio 2010

Rate This
  • Comments 53

I have heard from a few people who tried to install the final release of the Windows Phone Developer Tools but get an installation error like the following:

Visual Studio setup cannot run in compatibility mode.
For more information see the 'Installing' section in the Visual Studio readme at http://go.microsoft.com/fwlink/?LinkID=143397.

The link in the error message points to the Visual Studio 2010 readme because this issue can affect all editions of Visual Studio 2010, including WPDT.  Item 2.1.10 in that readme provides a workaround for this issue.  In my past experience, that workaround has proven to be incomplete though, so here are some updated steps that usually help solve this type of error:

  1. Click on the start menu, choose Run, type regedit and click OK.
  2. Browse to each of the following keys and delete any value that refers to the WPDT setup program (named vm_web.exe):

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted
    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

If the above doesn’t help, then you can also try to save vm_web.exe to your computer and run it from there.  When compatibility mode is triggered by Windows, it is based on a full path to the setup executable, so if you save it to a different location than you previously tried to run it from and then run it again, that can help avoid triggering compatibility mode.

  • Any more ideas, Aaron?

    I've tried all the steps above but still cannot get vm_web.exe to install.  I have also tried running setup.exe from vm_web.exe and verified that compatibility was not checked and that also failed.

    My system is Win7 64-bit, VS 2010 Premium and no previous versions of Win Phone SDK installed



  • Hi Phong - If you're still getting a compatibility mode error, I'd suggest using regedit to search your entire registry for "vm_web.exe" to see if there are other locations where that is being stored.  If that doesn't help, then I'd suggest saving vm_web.exe to your hard drive, renaming it to something else (the exact name doesn't matter) and running it again after renaming it.

  • This post saved my day. Thank you very much

  • When I had this error I have tried everything mentioned everywhere, but did not solve!

    I was almost going nuts.

    Then for some reason I checked with Application Verifier and found that HighversionLie was set to Windows 7 on any Setup.exe file

    I don't really know why that was set, but removing it solved.

    Hope this solves your case.

  • I had VS 2008 Professional open which borked the install with a really lame prompt that didn't give the option to continue the install after closing VS 2008 (could only exit). Reattempts resulted in that message even after I shut it down and tried again.

    Moving the file to another folder did the trick for me.

    Lazy installer UI code. Bad MS dev! Bad!

  • Hi Erik Reppen - What probably happened in this scenario is that when you exited setup after it told you that VS 2008 was open, a dialog appeared that said that the setup didn't appear to complete successfully.  If you clicked Yes on that dialog, it will cause future attempts to run that installer to launch in compatibility mode, which will then trigger the error in this blog post.  Compatibility mode is stored in the registry based on the full path to the setup program, so it will appear every time you launch setup from the same location as it was originally launched from.  Renaming or moving the file will cause the path to be different so it won't trigger the compatibility mode dialog.

    I've reported a bug to the WPDT setup team about that files in use dialog not allowing the user to retry.  Hopefully this is something that will be investigated for a future release of WPDT.

  • Hey, I would just like to additionally add that I had the same problem as Erik Reppen but with Visual Studios 2010. I downloaded the setup to my desktop, ran it, had installation quit because VS2010 was open, then had all subsequent install attempts throw that error. Moving the setup to a different directory solved the problem. I agree that it is pretty weak on Microsoft's part to not allow you to close VS and continue the installation from that point once the program is called.

    Just wanted to make sure that if anyone else runs into this problem they try this.

  • Hi Brennan R - Thanks for posting about your experience.  The issue described in this blog post can affect all Visual Studio 2010 editions, including the Windows Phone Developer Tools.  Moving the setup program to a different directory should solve this issue because the Windows compatibility assistant uses the full path to a program when it decides whether or not to run in compatibility mode, and moving the setup program causes the full path to no longer match what is stored in the registry.

  • Your ret edit updates worked and saved me from wasting more time.

    Had the compatibility mode removed from vm_ware.exe to run uninstall.


  • I tried everything < I just can't get visual studios to download?? Dang,,,

  • Hi ZCerritos College - Are you getting an error downloading or installing?  If it is a download error, I'd suggest trying to use the ISO file at download.microsoft.com/.../WPDT_RTM_en1.iso instead of using the web download bootstrapper (vm_web.exe).

    If it is an install error, please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%\vslogs.cab that will be created by that tool to a file server (such as http://skydrive.live.com), then reply back here and provide a link I can use to download your log files and take a further look.

  • Hi! I've got problem "Error occurred during setup Setup could not install the following component: Microsoft Windows Phone Developer Resources" and I've already tryed to:

    1. Rename and change file location, and download it couple times

    2. Search anything in registry as it was suggested (nothing found by the way)

    3. Used ISO file - nothing

    4. Reinstall Windows o_O

    Please, could you help me, please???



  • Hi Perezhogin - Steps 1 and 2 that you listed are only helpful if you're getting a compatiblity mode error dialog like the one described above in this blog post.  Since that isn't the error that you're getting, those steps won't help.

    This is the exact error that I see in your log file:

    Error 1935. An error occurred during the installation of assembly 'Interop.SirepBootstrap,FileVersion="7.00.7003.0",version="",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyCache, component: {8B51A48B-422A-4AD9-8671-6433A35A1202}

    In the past, when I have seen this error while installing the SirepBootstrap file, it has been caused by the version of Windows being a pre-release version.  From the version information listed in your log files, it appears that you don't have the final release of Windows 7 installed on your computer.  Your logs say you have the 7260 build, but the 7600 build is the final release.  Where did you get your version of Windows 7 from on this computer?  Do you have a disc that contains the final release of Windows 7 that you can install instead of the build that you have?

  • Thank you!!!

    It works now - I don't know, how is it possible, but I realy had old 7260 version.

    Thank you again! :)))

  • In my case

    Application Verifier 3.4 utility was blocking the installation of VS 2010.

Page 1 of 4 (53 items) 1234
Leave a Comment
  • Please add 7 and 1 and type the answer here:
  • Post