I started downloading Visual Studio for offline installation using layout switch. When the installation was 19.1Go, I closed the console and the download got stopped. Today I restarted it in the same folder (where previous files were) thinking it would continue. However, from what I see, it simply overwrites the previous files (files are still downloaded from internet). So, I am wondering if someone has a way to make it continue.
Thank you.
simple retype the command after opening command prompt in my case it was vs_community.exe --layout c:\vs2017layout --lang en-US
NOTE directory should be same as previous
it first verify the previously downloaded packages and then resumed the downloading here are some logs
Verified existing package 'Microsoft.VisualC.140.CRT.Redist.X86.Msi,version=14.0.24225'
Verified existing package 'Microsoft.VisualC.140.CRT.Source.Msi,version=14.0.24225'
Verified existing package 'Microsoft.VisualC.140.CRT.x64.Desktop.Msi,version=14.0.24225'
Verified existing package 'Microsoft.VisualC.140.CRT.x64.OneCore.Desktop.Msi,version=14.0.24225'
Verified existing package 'Microsoft.VisualC.140.CRT.x64.Store.Msi,version=14.0.24225'
Verified existing package 'Microsoft.VisualStudio.OfficeDeveloperTools.WIF.WindowsFeature,version=15.0.26621.2'
Total packages to download: 307
Starting 'UpdateLayout' operation
Download of 'https://download.visualstudio.microsoft.com/download/pr/10661194/7385009d7cc46622284fa28aea9a82bf/netfx45_dtp.msi' succeeded using engine 'WebClient'
Download of 'https://download.visualstudio.microsoft.com/download/pr/10715705/f34cc4a1fd105b0276170faf7f5e0271/VC_CRT.X86.Desktop.msi' succeeded using engine 'WebClient'
Download of 'https://download.visualstudio.microsoft.com/download/pr/10715705/f34cc4a1fd105b0276170faf7f5e0271/cab2.cab' succeeded using engine 'WebClient'Download of 'https://download.visualstudio.microsoft.com/download/pr/10661194/7385009d7cc46622284fa28aea9a82bf/netfx45_dtp.cab' succeeded using engine 'Bits'
UpdateLayout progress: 0.06%
Download of 'https://download.visualstudio.microsoft.com/download/pr/10715069/2f1ac63ac0488abe845c76ad6690d8c9/VC_CRT.X86.OneCoreDesktop.msi' succeeded using engine 'Bits'
Download of 'https://download.visualstudio.microsoft.com/download/pr/10715705/f34cc4a1fd105b0276170faf7f5e0271/cab1.cab' succeeded using engine 'WebClient'
Yes , now we can resume the offline installation. Latest installer Verifies the files if directory is unchanged and Resumes from there But they should provide torrent links of at least VS community edition, it is more reliable especially if files are multiple and are large in size.
Related
I have download an offline package of visual studio 2019 a year or more ago, since that date, and when a new update is released I use this command vs_Community.exe --layout pathToVS2019OfflinePackage --lang en-US to update my visual studio 2019 offline package.
But this time, when trying to do what I do each time:
vs_Community.exe --layout pathToVS2019OfflinePackage --lang en-US
Then it downloads the last version of the installer
Then nothing happens (Supposed in this step the update starts).
Why the update doesn't start (I didn't change any settings)?
Normally, the offline update VS’s process is like this:
On the machine with network
1). Move the existing layout folder from the machine without network to this machine.
2). Download the latest version of VS bootstrapper file(.exe file from official website).
3). Open CMD and cd to the directory where you saved the downloaded .exe file.
4). Type command like vs_community.exe –layout XXXX\XXXXX\XXXX –lang en-US and wait for it completes.
On the machine without network(offline)
5). Move the updated layout folder to this machine.
6). Launch Visual Studio Installer > find VS 2019 > click Update.
Looks like you are blocked on step 4), you need to make sure that you have downloaded and are using the latest .exe file and make sure that these operations are performed on a network based machine.
Details: Update a network-based installation of Visual Studio.
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
It worked for years.
Yesterday for no reason (?) I'm not able to compile LESS files any more.
I tried to
reinstall the Web Compiler extension,
reinstall Web Essentials 2019 extension,
reinstall the whole Visual Studio 2019 for 3 times,
start a new project from scratch
I do not know if some automatic update happened under the hoods, but basically, every time I try to compile a LESS file I get:
module.js:471
throw err;
^
Error: Cannot find module 'C:\Users\igor\AppData\Local\Temp\WebCompiler1.12.394\node_modules\less\bin\lessc'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:390:7)
at startup (bootstrap_node.js:150:9)
at bootstrap_node.js:505:3
Thanks for any help!
For VS2017 and VS2019:
Uninstall the Web Compiler extension
Delete* the directory C:\Users\<username>\AppData\Local\Temp\WebCompiler1.12.394
Install Web Compiler
I do not know why the "lessc" file disappeared.
* From cmd.exe:
rd /S %LOCALAPPDATA%\Temp\WebCompiler1.12.394
From a PowerShell prompt:
rm -r $env:LOCALAPPDATA\Temp\WebCompiler1.12.394
How I found the solution: I attempted to re-create the .vsix file from the GitHub repository for the Web Compiler extension so that I could get the lessc file; I had installed Node.js and all its associated gubbins. Trying to use the node_modules.7z generated by build.cmd in the Web Compiler files didn't work in the end because there are several deprecated things in it - I ended up with the error described in 3.10: Breaks IE Compat Option. So I thought: oh dear, it is all broken, why not just delete the directory and try the install again?
I deleted the C:\Users\<username>\AppData\Local\Temp\WebCompiler1.12.394 folder and ran the compilation from Task Runner Explorer which recreated the folder without having to reinstall Web Compiler.
Maybe it is related to also having the BuildWebCompiler 1.12.405 NuGet package installed in the project.
I was able to fix a similar problem with a "node-sass" file missing from the Web Compiler (although the entire bin folder was empty) by performing the following actions:
close Visual Studio 2019
delete the C:\Users<username>\AppData\Local\Temp\WebCompiler1.12.394 folder
restart Visual Studio.
When I restarted VS, the folder was recreated with all the necessary files back where they needed to be.
When I ran into the issue I had just came back to work after taking a little over a week off. At least for me, I think a program on my computer that automatically cleans up unused temp files may have been the culprit.
I had to disconnect my laptop from the internet for some time (before disconnecting the offline installation was working just fine and had already downloaded 11.6GB). When I got back I ran the vs_enterprise.exe --layout C:\vs2017offline --lang en-US command again but now it gets stuck on
=> Layout operation correlation: {"id":"5c09fc12-236c-4c7e-9a8e-7d24500b9e1d"}
I checked my error log file and it is empty.
Below are my log files. I can't understand why this is happening, so any help will be appreciated.
=>[29e8:000f][2017-03-18T10:56:51] Download requested: https://go.microsoft.com/fwlink/?linkid=833502
=>[29e8:000c][2017-03-18T10:56:51] Download requested: https://go.microsoft.com/fwlink/?linkid=833501
=>[29e8:0012][2017-03-18T10:56:51] Attempting download 'https://go.microsoft.com/fwlink/?linkid=833502' using engine 'WebClient'
=>[29e8:0013][2017-03-18T10:56:51] Attempting download 'https://go.microsoft.com/fwlink/?linkid=833501' using engine 'WebClient'
I'm trying to install the package of Microsoft Visual C++ Redistributable as my xampp apache module cannot be installed. The installation take a very long time to complete. What should I do? Is this common and is all I have to do is wait?
They are dead stuck with this setup progress as the indication
Processing: Windows7_MSU_X64
To install the Visual C++ 2015 Redistributable, you do not need to remove or uninstall the previous versions.
Refer to the error message, you can have a look at the installation log file and search ‘error’, if you can find the error message about Windows6.1-KB2999226-x64.msu, check this similar issue and have a try with the following to troubleshot this issue:
Download the update KB2999226 for your OS edition from here: Update for Universal C Runtime in Windows and before it, since your OS is windows 7, make sure SP1 is installed.
Manually install the KB2999226 as below:
Find the Windows6.1-KB2999226-x64.msu from the folder C:\ProgramData\Package Cache\xxxxx\packages\Patch\x64, which you can the path from the installation log
Create a folder named ‘XXXX’ in that and execute following commands from Admin command prompt
wusa.exe Windows6.1-KB2999226-x64.msu /extract:XXXX
DISM.exe /Online /Add-Package /PackagePath:XXXX\Windows6.1-KB2999226-x64.cab
vc_redist.x64.exe /repair
If you have no idea about the installation log, you can go to %temp% and order by ‘Date modified’, then you should find the installation log, or you can use http://aka.ms/vscollect to gather the installation logs. After using it, you will find vslogs.zip under %temp% folder then upload the file to https://onedrive.live.com/ and share the link here.
I first tried a clean boot and that didn't work so I opened up the task manager to see what other processes I might kill while it was stuck at "Processing: Windows7_MSU_X64" I killed the process titled "windows update standalone installer" and the install completed successfully the moment I killed that process.
Okay, I found the solution for my stucked installation. I updated my Windows manually using wsusoffline tools as my Windows can't seem to update with the usual ways.
Install wsusoffline and select all update for Windows (Windows 7 for me). Make sure to choose the folder to save your update.
Wait for the update to be downloaded
Install the update
Install the MV C++ Redistributable again
Done!
I finally can install my Xampp Apache module and access to the localhost.