Visual Studio 2017 Enterprise installation stucks at Win10SDK_10.0.14393.795 In Process Monitor it shows message result No such file Path %AppData%\Local\Microsoft\VSApplicationInsights\vstelAIF-312cbd79-9dbb-4c48-a7da-3cc2a931cb70*.trn I tried to put empty file a.trn in folder vstelAIF-312cbd79-9dbb-4c48-a7da-3cc2a931cb70 and after that it says error Invalid name parameter. I first tried to install Visual Studio 2017 beside Visual Studio 2015 then I tried to uninstall Visual Studio 2015 and install Visual Studio 2017 and same problem happens.I tried to skip Win10SDK_10.0.14393.795 but then in stucks at Microsoft.VisualStudio.Debugger.JustInTime with same message.
I've encountered similar hangs with various Visual Studio operations (including installation) in the past.
The solution has been to create an empty file in the directory (or directories) it's looking for with a .trn extension. For whatever reason this satisfies it and it's able to progress past this point.
Related
When i try open Visual Studio, I immediately receive an error message. The message only tell me to open a xml file to receive more informations.
The directory of the xml file is C:\Users\User\AppData\Roaming\Microsoft\VisualStudio\15.0_ae456ee1\ActivityLog.xml
I already tried some possible solutions, like delete the privateregistry.bin file, on this directory: C:\Users\User\AppData\Local\Microsoft\VisualStudio\15.0_ae456ee1. But when I delete this file and try open Visual Studio, instead of receive the error immediately, the logo of Visual Studio appears, then the error message appears and the privateregistry.bin file is re-created.
This problem first happened in the Visual Studio 2017 Community. I reinstalled this version and downloaded Visual Studio Professional, but the error continues.
Repair Visual Studio 2017
Sometimes your Visual Studio installation becomes damaged or corrupted. A repair can fix this.
Find the Visual Studio Installer on your computer.
For example, on a computer running Windows 10 Anniversary Update or later, select Start,
and then scroll to the letter V, where it's listed as Visual Studio Installer.
Note
On some computers, the Visual Studio Installer might be listed under
the letter "M" as the Microsoft Visual Studio Installer.
Alternatively, you can find the Visual Studio Installer in the
following location: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe
Click or tap to start the installer, then select More, and then select Repair.
My exact issue was for an Unreal Engine 4 solution. The problem was the the intermediate folder was moved, and a new one re-generated. Instead of having to re-generate project files (from the .uproject), I simply deleted the auto-generated intermediate folder and replaced with the moved/old version (which included the build files from an initial project generation from the .uproject).
It is at least better to try a solution other than repairing the install, as that will delete external plugins and preferences...
I was trying to update VS 2017 to 15.6.2 version. As usual VS asked me to update the Installer. But the Installer updating failed and now, when I try to launch the VS updating again, I get this error message:
Error loading vs_installershell.exe: No signature was present in the subject.
Anyone has ever seen this before? Any help will be appreciated.
Microsoft recommends the following procedure in this case:
Close the Visual Studio Installer.
Delete the Visual Studio Installer directory. Typically, the directory is C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Run the Visual Studio Installer bootstrapper. You may find the bootstrapper in your Downloads folder with a file name that follows a vs_[Visual Studio edition]__*.exe pattern. If you don't find that application, you can download the bootstrapper by going to the Visual Studio downloads page and clicking Download for your edition of Visual Studio. Run the executable to reset your installation metadata.
Try to install or update Visual Studio again. If the Installer continues to fail, go to the next step.
There is also a bit of warning:
Performing the following actions reinstalls the Visual Studio Installer files and resets the installation metadata.
But in the end, it reinstalls the VS Updater.
Source: https://learn.microsoft.com/en-us/visualstudio/install/troubleshooting-installation-issues
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
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.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I am using visual studio 2010 proffesional.
I have started to take errors after installing sql 2012 express.
I did the instructions here :
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/59147ba0-82d2-418a-a33d-08f75eb68387
(
1.Remove Visual Studio 2010 Sp1 manually from control panel
2.Remove Visual Studio 2010 with this tool http://archive.msdn.microsoft.com/vs2010uninstall
and this command:Complete (VS2010_Uninstall-RTM.ENU.exe /full /netfx)
)
Also i deleted all user data and every folder about visual studio and installed again.
I have removed all add-ins.
But the result is the same.
Here are the errors:
Here is the log file (ActivityLog.xml)
How can i correct this?
Thanks,
Looking at regkey
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\ExtensionManager\EnabledExtensions
I removed an entry with a lot of question marks: ??????????????????
All started working fine then.
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.