I was installing Visual Studio-Community 2015, and I got the error (0x80070643), also known as Team Explorer Fails. The installer runs for a while, and then outputs this: (Screenshot) I have used microsoft repair tools, reinstalled the redistributables, checked the hash, (fine) and run a SFC scan, (fine). I have been searching everywhere, yet I am to have found a solution. Here is the log, (shortened, because it is massive): (Error Log)
That error code is generic in that it just means "Fatal error during installation"
You need the installation log of the particular MSI that failed.
Do you have that already? Look in your temporary directory (i.e. just type in %TEMP% in the windows explorer address bar and hit enter) for something like "dd_vs_version info_vs_teamExplorerCore.log"
If that's not there, you might be able to manually execute the MSI yourself and capture a log:
From a command prompt (ideally elevated) you could run the command:
msiexec /l*v "%TEMP%\teamexplorer.log" /i "*full installer path*packages\TeamExplorer\Core\vs_teamExplorerCore.msi" MSIFASTINSTALL="7" USING_EXUIH="1"
You need to update that command so that the path to the MSI is correct. If you've downloaded the ISO, then it will be in there; otherwise, while you're running the installer, you can probably find it under the package cache, e.g. C:\ProgramData\Package Cache{48992F68-BEE6-35D8-89AC-6A81406F1096}v14.0.24712 looking at the log.
Using a tool like Void Tools Everything will make it easy to find the MSI and logs amongst a sea of temporary folders and caches.
Related
I'm currently trying to publish my AWS lambda functions using Visual Studio 2019 community (v4.8.03752) and leveraging the AWS Toolkit for Visual Studio (v1.20.1.0). After right clicking my project and selecting 'Publish to AWS Lambda' I receive the following error:
- Zipping publish folder C:\Users\Matt\source\repos\programName\programName\.\bin\Release\netcoreapp3.1\publish to C:\Users\Matt\AppData\Local\Temp\HelloWorld-CodeUri-Or-ImageUri-637489827969959200.zip
- Failed to find the "build-lambda-zip" utility. This program is required to maintain Linux file permissions in the zip archive.
- Error packaging up project in C:\Users\Matt\source\repos\programName\programName\. for CloudFormation resource HelloWorld: Failed to find the "build-lambda-zip" utility. This program is required to maintain Linux file permissions in the zip archive.
I've been able to deploy this MANY times over previous months, up until Friday 2/12 when I started receiving this error (after a reboot). What's even more strange is that if I uninstall the AWS Toolkit for VS, then reinstall it, I'm able to publish successfully 1 time. With my 2nd attempt, I begin to receive this error again.
Steps I've taken to attempt to resolve:
Repair Visual Studio
Uninstall/Reinstall Visual Studio
Uninstall and reinstall amazon.lambda.tools using dotnet tool install -g Amazon.Lambda.Tools
Uninstall AWS Toolkit for VS, Reinstall toolkit. (This works for first deployment, fails when trying to deploy a 2nd time)
UPDATE:
Per some comments below, it looks like this is being caused by McAfee Real-Time Scanning. In checking the logs during a deployment I noticed a "Virus or threat found" record that points directly to the build-lambda-zip.exe file. To permanently avoid this issue moving forward please follow the steps provided by user2174794 in the comments below.
I'm having the same issue. Just started happening today. It was working within the last 2 weeks.
Failed to find the "build-lambda-zip" utility. This program is required to maintain Linux file permissions in the zip archive.
Running Windows 10, Visual Studio 2019
My solution for now is to use the .NET Core CLI
https://docs.aws.amazon.com/toolkit-for-visual-studio/latest/user-guide/lambda-cli-publish.html
Specifically, the
dotnet lambda deploy-function
A recent update must have broke the AWS Toolkit For Visual Studio.
I have the same problem, it was because my antivirus detect the executable build-lambda-zip.exe, then delete it.
I restore the executable from my antivirus, or restore dotnet tools with the command :
dotnet tool update -g Amazon.Lambda.Tools
I also faced the same issue,
This is because the "build-lambda-zip.exe" file is getting removed by the McAfee Antivirus.
For the permanent fix, you need to follow the below steps.
Step 1
Go to McAfee Settings >> Quarantined Items
You will find the "build-lambda-zip.exe" file there. Restore it to the original location.
Now If you will try to publish, the error won't get displayed. But again on the next scan, the file will get removed.
Step 2
We need to Exclude this file from getting Scanned and removed. So for that,
Go to McAfee Settings >> Real-Time Scanning and Add the "build-lambda-zip.exe" file in the Excluded files list.
For the file path of "build-lambda-zip.exe" got to
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\ and search for the file name.
Maybe you should try reinstalling the AWS Tool Kit and before you make deployments please turn off your antivirus protection. I was troubbling the same issue and my antivirus(McAfee) was deleting build-lambda-zip.exe file when I did deployment first time.
I'm curious about the state of the extension installation. Can you go to VS's extension directory in Windows explorer C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions and in the search box search for AWSToolkitPackage.dll.
Ideally it should only show one instance of that file. Assuming it finds a single instance right click on the file and select "Open File Location". Now that you are in the root folder of the AWS extension check the Resources folder and see if it contains the file build-lambda-zip.exe.
I know the question is in a windows system, but under a linux system, in my case the following command was needed:
sudo apt-get -y install zip
This error presents itself immediately upon first launch of the program following the attempted install.
click to enlarge
I have ran %programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe -full and then re-ran the installer and the issue still presents itself.
I have tried the solutions here and they did not resolve my issue.
I also tried both of the answers here.
Any guidance here or things to try next will be very helpful!
Here are my log files from when I tried this in March. They're old, but re-running this installation still shows the exact same error.
https://pastebin.com/7D2JwGKF
for i in 12 do this.function
try this one
Open a command prompt with admin privileges
Run following command (this will clean up previous install cache. -full option is important) "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe" -full
Restart the installer
A product matching the following parameters cannot be found during VS Installation
I use the permission of Administrator to install vs_enterprise.exe.
But the install package don't work at all.
OS: win10 professional
The install log in appdata/local/temp/ is as follow:
dd_bootstrapper_20170313103210:
Beginning of the log. Start Time: 13/03/2017 10:32:10 VisualStudio Bootstrapper:13/03/2017 10:32:10: Current Optin root path does not
exists VisualStudio Bootstrapper:13/03/2017 10:32:11: Commandline
arguments =
dd_vs_enterprise_decompression_log.txt:
[3/13/2017, 10:32:4] === Logging started: 2017/03/13 10:32:04 === [3/13/2017, 10:32:4] Executable: D:\vs2017\vs_enterprise.exe
v15.0.26206.0 [3/13/2017, 10:32:4] --- logging level: standard ---
[3/13/2017, 10:32:4] Directory
'C:\Users\gary\AppData\Local\Temp\b012f31d56525c685e\' has been
selected for file extraction [3/13/2017, 10:32:4] Extracting files
to: C:\Users\gary\AppData\Local\Temp\b012f31d56525c685e\ [3/13/2017,
10:32:5] Extraction took 484 milliseconds [3/13/2017, 10:32:5]
Executing extracted package:
'vs_bootstrapper_d15\vs_setup_bootstrapper.exe ' with commandline ' '
[3/13/2017, 10:32:11] The entire Box execution exiting with result
code: 0x0 [3/13/2017, 10:32:11] Launched extracted application
exiting with result code: 0xc000000d [3/13/2017, 10:32:11] ===
Logging stopped: 2017/03/13 10:32:11 ===
Thank You~
I was having this exact problem, thought it was a services thing. The installer would start if I ran it as soon as Windows booted; if I waited, it didn't.
Turns out it was RivaTunerStatistics server that was running for my gaming overlays. Closed it, and voila, working again. Tried multiple times to confirm.
I had a similar issue, my Visual Studio Professional 2017 installer was closing before the installation starts. I solve the issue by following these steps:
1 - Open the prompt(CMD) with administration rights
2 - Check if you have the "InstallCleanup.exe" file inside the folder "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\". If the file is there then go to step 7
3 - Manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder
4 - Relaunch the newly downloaded visual studio installer
5 - Allow the first step to install the installer
6 - Once the installer comes up and you can see workload choices (.net desktop and the like), close it
7 - inside CMD navigate to the folder "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\"
3 - run this command: "InstallCleanup.exe -full"
4 - that's it. Just run the installer again.
It worked for me.
I had the same Problem on two different Pc's (both win10) and the only thing that worked for me, was reinstalling Windows's and rerun the visual studio installer. I know, that's not a good, fast or easy solution, but it works.
I had a similar issue with the VS 2017 installer (similar error message), and I was finally able to resolve my problem after 4 days of troubleshooting with Microsoft Support. I'm developing on a Dell laptop and the support technician believes one of the Dell services was causing issues with the winmgmt service.
Below is a command that failed to run during troubleshooting. After making sure we had an OS restore point saved, we issued the winmgmt /resetRepository command. After that, the VS 2017 Pro installer was able to execute without error.
Here are the exact steps taken by Microsoft Support:
Step 1: Create a Windows system restore point.
Step 2: From the command prompt with administrative rights or elevated privileges, execute the following command: net stop winmgmt
Step 3: Open a Windows Explorer and locate the path to C:\windows\system32\WBEM\ folder and rename the Repository folder to something else like RepositoryOLD (right click and choose 'Rename Folder').
Step 4: restart the computer
Step 5: From the command prompt with administrative rights or elevated privileges, execute the following command: net stop winmgmt
C:\>net stop winmgmt
The Windows Management Instrumentation service is stopping.
The Windows Management Instrumentation service could not be stopped.
Step 6: From the command prompt with administrative rights or elevated privileges, execute the following steps and execute the following this: winmgmt /resetRepository
C:\>winmgmt /resetRepository
WMI repository has been reset
Step 7: restart the computer.
Hope this helps someone else.
I had the same problem but it was solved by the answer #Ben Logan gave (Closing RivaTunerStatistics).
After trying all the suggested answers here (using VS 2017), I followed the instructions on the official Microsoft docs which worked for me. In summary:
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.
For anyone still having this problem:
One of my co-workers encountered the same problem. We spent 4 hours searching for solutions, uninstalling VS and other software that we thought might be the culprit.
In the end, THIS LINK helped us figure it out. The problem is somehow explained there and is linked to NODE_OPTIONS variable. If you have that variable set, remove it then restart your computer. This solved his problem.
Configuration:
Widows 10, Visual Studio 2017 Enterprise.
I hope this helps you
Copy vs_enterprise.exe to a USB and run. It will work.
try to run this file using console
example: c:/vs_community__556869458.1519050247.exe
I am trying to install the Visual Studio 2015 Update 3, but I am receiving an error each time. I have tried both the web installer and the ISO, and I have also tried going into Control Panel/Programs and modifying the 2015 install. All of these result in the same error: "Setup Engine - The parameter is incorrect". I've read about some of the other issues with the installer, but I'm hoping somebody else might have seen this one or something similar. The logs always have the following error in them:
[1B10:1DA0][2016-07-18T11:39:28]e000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4}
[1B10:1DA0][2016-07-18T11:39:28]e151: Detect failed for package: Win10_Universal_CRT_SDK_Extension_SDK, error: 0x80070057
I have even tried to download the full installer for VS2015, but all installers seem to run through the same error. Any ideas on how I might repair this particular component so the installs will succeed?
Additional information, this is happening on a VM of Windows 10 running in Parallels 11.
Screen shot of installer failing
I found a similar issue here： https://connect.microsoft.com/VisualStudio/feedback/details/974081/visual-studio-update-3-installation-keeps-failing-error-message-setup-engine-the-parameter-is-incorrect
The reply from Heath[MSFT]:
The logs confirm that some of your Windows Installer product
registration is corrupt. For the first issue, open a command prompt
(preferably elevated to avoid multiple UAC prompts later) and run the
following:
start /wait msiexec /fomus {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} REINSTALL=ALL
That should get
you past the first problem. If it does not, manually remove the
product like so and re-install it from the package cache:
start /wait msiexec /x {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} IGNOREDEPENDENCIES=ALL
start /wait msiexec /i "C:\ProgramData\Package Cache\{A79F6653-6AF1-4AF2-BC15-F5D6C05E1E6A}v2.0.40326.0\packages\sptoolsDependencies\enu\WorkflowManagerTools_x64.msi" ADDLOCAL=ALL NOVSUI=1
(change the above file
WorkflowManagerTools_x64.msi according to your log file record) After
this, installing VS Update 3 should work.
I had a very similar problem which at its root exhibited the same issue identified above in the Visual Studio 2015 Update 3 setup error (I couldn't install SSMS 17.1 which uses the Visual Studio 2015 Isolated Shell). I tried the solution above which unfortunately did not work for me. I did some more digging through the vs_isoshell.exe log file and found lines similar to those below.
[6BE0:36E0][2017-07-13T13:05:36]i000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {9A7E3828-17FB-3E0C-9B28-48493E01937A}
The ProductCode refers to the "Microsoft Visual C++ 15 x86 Debug Runtime - 14.10.24269".
A perusal of my installed programs showed I did not have this installed, and I was unable to install it again due to a later version being present (it turns out it was upgraded, or removed, when I installed Visual Studio 2017).
I did some more searching and came across this page which had steps I adapted to my situation. I performed the same registry profiling of the installer with Process Monitor and the same key was missing. I added a key called DisplayVersion (string - REG_SZ) to the path below with a value of 14.10.24629 and that worked.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\8283E7A9BF71C0E3B9828494E31039A7\InstallProperties]
Adding the key/value pair allowed the installation of the VS 2015 Update 3 Isolated Shell to finish successfully which in turn allowed the SSMS 17.1 installation to complete successfully.
So I wanted to force an uninstallation of VS2015 Enterprise with "vs_enterprise.exe /uninstall /force", but I get an error message:
Update for Microsoft Windows (KB2999226) : The storage control blocks were destroyed.
I tried to restart my PC, so that Windows can apply that update, but it didn't work, the uninstall process always exits with that error.
I have no idea how to proceed.
When I tried to uninstall Visual Studio 2015 Community Edition I first when to the Control Panel > Programs and Features, tried to uninstall it that way.
Then found the following link:
force uninstall a visual studio 2015 preview or release candidate
Then navigated to C:\ProgramData and typed:
dir /s vs_community.exe
It generated this useful path info:
C:\ProgramData\Package Cache\{50b32652-69d2-4b93-9316-edcd12067b8b}
Then used Windows Explorer to go to that folder, Shift + Right Click > Open command window here and ran:
vs_community.exe /uninstall /force
I then got this error screen after a LONG time...
Then saw the below question:
removing visual studio components left behind after an uninstall
So I tried to run:
vs_community.exe /repair
It ended up hanging and I force quit it after about a half hour. Then I ran:
vs_community.exe /uninstall /force
This time I checked the error log, and found the following line very near the bottom.
Applying execute package: Windows7_MSU_x64, action: Uninstall, path: 2999226, arguments: '"C:\windows\SysNative\wusa.exe" /uninstall /kb:2999226 /quiet /norestart'
Thought I had to install the KB2999226 update because of the error:
Update for Microsoft Windows (KB2999226) : The storage control blocks were destroyed.
So I installed it, but vs_community.exe still wouldn't force uninstall. I probably already had the update installed, but can't find out because my windowsupdate.log file only goes back a month or so? Anyhow, my installing of the update probably didn't change anything.
According to the following articles:
sysnative folder 64 bit windows
File System Redirector - MSDN
The Windows7_MSU_x64 was trying to get to the C:\Windows\System32 folder, but because I have a 64-bit version of Windows 7, it was trying to reach the C:\windows\SysNative folder, because it is an auto-redirect to the real System32 folder. For some reason I don't have a SysNative folder, so...
I then went to Windows Update and uninstalled the KB2999226 update and went back to:
C:\ProgramData\Package Cache\{50b32652-69d2-4b93-9316-edcd12067b8b}
Ran the following again:
vs_community.exe /uninstall /force
This time it worked and I got the screen:
I had the same issue (WINDOWS 7) and I solved by making sure the following KB's were installed:
KB3139923
KB3072630
Having one installed without the presence of the other was causing the issue.
In case anyone encounters this again, the following did the trick for me:
Download and install KB2999226 from
https://www.microsoft.com/en-us/download/details.aspx?id=49093
Create a symbolic link from c:\Windowss\SysNative to c:\Windows\System32 using the following command line:
mklink /D c:\Windows\SysNative c:\Windows\System32
Running the following command from command prompt:
"C:\ProgramData\Package Cache\{68432bbb-c9a5-4a7b-bab3-ae5a49b28303}\vs_professional.exe" /uninstall /force
The {6844...} part might be different on different machines and the vs_professional.exe might be located at different location but I guess anyone should be able to search for it inside the "PackageCache" folder
I had just the same issue. But for me nothing here has worked.
The only way worked for me was the standard way through the Windows Uninstall panel. The only difference here you have to reboot and uninstall it again until the option disappeared from the panel.
The below steps fixed it for me.
First uninstall KB2999226:
wusa.exe /uninstall /kb:2999226 /quiet /norestart
Download and re-install KB2999226 (the one we just uninstalled above):
https://www.microsoft.com/en-us/download/details.aspx?id=49093
Uninstall Visual Studio from admin shell (you can use the install exe you originally used for the install):
vs_community.exe /uninstall /force