visual studio 2013 windows program compatibility mode - visual-studio-2013

I install windows 10 , after i install visual studio 2013 ultimate
bat cannot run VS2013 setup
Error - windows program compatibility mode is on. turn it off and then try setup again
pleas help me solve problem

I had the same problem, and tried every solution on the internet but none of them worked for me.
(my setup file was a .iso file that I mounted on a virtual disk.)
I simply copied the files from virtual drive to one of my hard drives and ran the setup again: it worked!

Right Click on your file installer visual studio .exe then properties>details> look at the Originil file name, rename visual studio installer using the same name in originil file name. Run it and it work...!
i hope this work...

Related

Visual studio installation path grayed out

I had to reformat one of my drives (T:) and change its purpose. I had Visual studio 2015 installed on it, uninstalled it before formatting and now the drive has a different letter (can't change it, other things installed on it). I want to install visual studio 2015 again, but on the C: drive. When I run the installation, I get this:
The T: drive doesn't exist anymore, and I can't change the installation path to another drive.
I tried some solutions where I had to delete registry keys, but didn't succeed since most of the solutions were for older versions of visual studio. Is there a way to change the path?
Run installer in command line (Admin Mode) In folder keep File vs_community_ENU.exe
and put this command
vs_community_ENU.exe /uninstall /force
Then put this
vs_community_ENU /CustomInstallPath C:\VisualStudio2015
NewDrive:\VisualStudio2015
it work for me
Hope this helps
I had the same problem. I had an installed Visual Studio on a crashed harddisk.
I tried everything above, nothing worked. You should use this method as ultima ratio:
There is a VisualStudioUninstaller by Microsoft.
Download it
Extract it
Run it with Setup.ForcedUninstall.exe in an administrator command prompt
If this fails:
Start an elevated powershell:
install-package msi -provider PowerShellGet
get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' | get-msiproductinfo | uninstall-msiproduct -properties IGNOREDEPENDENCIES=ALL
Try again. If this fails, replace the GUID with one of the following:
Visual Studio 2015: {777CBCAC-12AB-4A57-A753-4A7D23B484D3}
Visual Studio 2013: {56E09E41-21B6-4F87-8D60-0787D028ECDD}
Visual Studio 2012: {DB786F13-64A8-45D7-8C03-0E819DF9F7B3}
Visual Studio 2010: {01696F98-947C-4CF9-8BD3-ABE70332FDED}
Sources: blogs.msdn.microsoft.com
and
landinghub.visualstudio.com
If this fails get an exorcist or/and reinstall your system.
I know you said it worked, but for some (including me) it did not. After multiple hours, however, I found a way. Here are the steps to my solution:
If you have not uninstalled VS2015 yet, do it through Control Panel.
Run the setup (ect. vs_community.exe).
If you cannot install on desired drive, keep reading here :)
Copy the path from where the VS2015 want you to install it on (e.g.: "D:\Programmer\Microsoft Visual Studio 14.0").
Open regedit(Just press windows key, type it in, and press Enter).
Warning, now you are in the windows registry, be careful or you may cause system-wide instability.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData Here there should be 2 folders called something like S-1-5-18 and S-1-5-21-345634235-23423416487. Just start with the one with the smallest number.
Go into the Components folder, and here you should see many folders with numbers and letters as name. Right click on the first of these, and click Search. ("Find" for Windows 10)
Paste the path from step 4. here, and make sure that the 3 top boxes are checked (they should be by default).
Right-click the first result of the search and click export. Save it somewhere you remember, then right-click it again and delete it this time.
Run the VS2015 setup again (vs_community.exe) and check if you can change the path now. If not go back to 9. and continue.
If it worked, just install VS2015 and just remember where you put your saved reg files. If anything goes wrong, you can restore them again by running the file.
Hope this helps someone!
This worked for me:
Start procmon and run the VS installation.
In procmon, find the relevant registry by looking for:
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\*\Components"
Make sure the key you've found was successfully opened (result should be SUCCESS)
Open regedit and find the relevant Components folder.
Search for the key you have found.
Export it for backup, and then delete it.
Hope it works for you too :-)
For me, it was the mistake of installing SQL Server Management Studio 2016 before installing Visual Studio 2015. SSMS 2016 is now based of VS 2015 Shell Core. And the new setup doesn't allow for any interaction except pressing the Install button. That way, part of VS 2015 was installed to C: drive. And hence, all options to change VS 2015 Enterprise install path failed.
I removed SMSS 2016 and, explicitly, VS 2015 Shell Core and then tried to install VS 2015 and it worked with Custom Path and Browse button.
You can use junction tool by Microsoft to create a REAL directory on other partition (e.g. D:\Program Files (x86)\Microsoft Visual Studio 14.0) and make a symbol link to it as C:\Program Files (x86)..., just like the command shows below, then windows will use C:\Program Fil.. as path and the real dirs/files are in D:\Prog...
junction.exe 'C:\Program Files (x86)\Microsoft Visual Studio 14.0' 'D:\Program Files (x86)\Microsoft Visual Studio 14.0'
Download junction tool from https://technet.microsoft.com/en-us/sysinternals/bb896768.aspx
In case someone still has this problem (I had it, since I deleted my partition, on which Visual Studio was installed before):
Open the registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\Setup
and there you will find some files. At least one of these files should contain the old path. Delete the file and the installation should work now.
In case there are other people who couldn't get it to work with the solutions already posted, here's what I did:
My problem was, that I had VS installed on partition E. The harddrive containing E crashed one day, and I couldn't uninstall VS properly anymore.
/uninstall /force wouldn't do the trick, since the setup would crash every time.
So I took my partition "D" and gave it the letter "E". Now I was able to install VS to the specified path. After that, I uninstalled it with /uninstall /force and the setup finished successfully.
After that I changed the partition "E" back to "D" and was able to install VS to "D".
I hope this helps someone with the same problem.
I know this is old, but just so you know there are command line switches that are very helpful for this sort of thing. In the command prompt, call your executable followed by /CustomInstallPath then the directory, as follows (adjust your executable pathname, of course, as necessary):
vs_community__e45cb735eddf4e4b9d95904be6e1ba26.exe /CustomInstallPath
Just a heads up, this didn't work for me the first time, so don't be afraid to try a couple times. I left my computer for the weekend (logged out), and ran the exact same command without doing anything else and it worked. Go figure...
In powershell:
Remove-Item
Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\CACBC777BA2175A47A35A4D7324B483D
see https://stackoverflow.com/a/33839884/3353857

Can't open text file in Visual studio while debugging in virtual machine

I tried to search for the problem on google but didn't manage to find anything useful.
I'm working with a MacOsx with Parallels running Windows 8.1, I installed Visual Studio 2013 and set the Project Default Location in
C:\Users\myname\Documents\Visual Studio 2013
so that is a local location.
The problem is that when I try to debug a program which need to read a text file, such file is not read properly.
The text file is in the same folder of the executable.
Strange thing is, if I navigate to that directory with the cmd.exe and try to run the executable, the file is correctly read.
That prevents me to use the debugger, because when I try to use it the file is not read.
What kind of problem is that? Any clue about how I can solve it?
EDIT: After some searches, I think this could be related to .NET Trusted folders.

Microsoft Visual Studio 2013 Shell (Minimum) error in installation

When I'm installing Microsoft Visual Studio Express for Windows Desktop I keep getting this error:
Here is the screenshot:
.
Here is the log file: http://pastebin.com/z95nT0st
I use MagicIso to extract the iso vs2013.4_dskexp_ENU. I tried to mount it into virtual disk too.
I fully reformatted my laptop so theres no old version of VS here.
I figured out now why I get that problem.
When I reformatted my laptop, I downloaded recovery software to recover the files I need (visual studio installer and others), and then when i install it, it didnt get installed successfully. So I deleted the file, but I think it already installed some other components of visual studio uncompletely before it fails to installed the vs.
Finally, I downloaded VS shell, and installed it in MVS folder but it fails to install half of it, so when I try again to install the VS, I got different error, it says the VS shell cannot be opened, (so this means I'm right) I get the error because its trying to open the "uncompletely" and continue to install it, but it cannot open it because its "uncomplete".
So now when I type this command G:\wdexpress_full.exe/uninstall/force in cmd, it deletes all the remnants of VS and then it fix my problem.
Most likely you have downloaded a bad image. Download it again.
As an aside why not use the VS2013 Community Version?

Error while installing Microsoft visual studio Professional 2010

I am trying to install Microsoft visual studio Professional 2010 on my Windows XP SP3 edition. I am getting the error "vs_setup.msi could not be open" :
I have seen some forums mentioning the same problem for different reasons, and mostly because of having a previous version of Microsoft visual studio installed, but this is the first time for me to install it. Any idea how to fix that ?
Note: The actual setup files are in the path "G:\Visual Studio 2010 Professional". I do not know why the setup is trying to look for vs_setup.msi inside the "G:" directly ! Of course it is not there.
Maybe this setup is from DVD image and it's hardcoded to work in root directory.
Try to move all setup files to G:\ or another drive root
It probably doesn't like the spaces in the installation folder name. Rename "Visual Studio 2010 Professional" to VS2010Pro and see if it doesn't start working.
Also look for the setup log in %temp%. Sometimes it's cryptic but you can usually get SOME idea of what went wrong. Maybe edit your question with the errors from that log. It's called dd_something*something* etc.
Microsoft Visual Studio 2010 Shell (Isolated) Redistributable Package.
With 7zip open and extract VSIsoShell.exe in a New Directory (there are many files inside of this .exe).
After this is done, redirect to the right path w/ the extracted files (with vs_setup.msi file).
7zip is an Open source Windows utility for manipulating archives (www.7-zip.org)

Problems opening solution file in Visual Studio 2005 running under Parallels

I wrote a simple program in C# on Visual Studio 2005 on a windows machine at work. I tried to open the solution file at home in Visual Studio 2005, inside of Parallels, on my mac and I get the error:
Unable to read the project file 'filename.csproj'. Invalid URI: The hostname could not be parsed.
Does anyone know a way to fix this?
Odds are the project file is referencing a hostname that is only valid within your network at work. You'll have to find the hostname it is referencing and manually change it to one that works within your network at home.
Ok well I figured it out. The shared folders are .psf which is invalid to Visual Studio.
In case anyone is interested:
Inside of XP in Parallels, Map a Network Drive 'X' to the 'Home' folder.
Open the Solution file in the Networked Drive using Visual Studio
Done.

Resources