In the VS official website to download the installation package, the results repeatedly download resources, the installation progress bar has not been moving, reinstall, copy a variety of methods have tried, still not……
Later, I noticed that the download needed to be verified after completion, and I felt that there was an error during the verification, so I downloaded it. The following is the solution
1. Run the command line and type the command gpedit.msc
2. Open the Local Group Policy Editor and find Windows Settings
3. Open Windows Settings and find Security Settings ->; The local policy
4, find the security option – system secret ->; Use FIPS compatible algorithms for encryption, hashing, and signature – set to disable
5. Right-click on the property and set it to Disable
6, then click the VS2017 installation package again will not prompt the signature failed, you can install
Later, I noticed that the download needed to be verified after completion, and I felt that there was an error during the verification, so I downloaded it. The following is the solution
1. Run the command line and type the command gpedit.msc
2. Open the Local Group Policy Editor and find Windows Settings
3. Open Windows Settings and find Security Settings ->; The local policy
4, find the security option – system secret ->; Use FIPS compatible algorithms for encryption, hashing, and signature – set to disable
5. Right-click on the property and set it to Disable
6, then click the VS2017 installation package again will not prompt the signature failed, you can install
Read More:
- Record the pits you stepped on – NSS error – 5938 (PR_ END_ OF_ FILE_ ERROR), curl: (35) Encountered end of file
- An error occurred when installing vs2017: failed to verify the signature of the installation program list
- Problems encountered in VS2010 compilation
- Solutions to some problems encountered in programming with vs2017
- Summary of problems encountered in compiling and installing vtk7 + vs2013 / 2015 + cmake
- Vs (Visual Studio) encountered a solution that could not open iostream
- Small problems encountered in compiling OpenGL under VS2010
- Record of problems encountered in using vs2017
- Problems encountered in the installation of pyromacoustics
- Vacuum box installation CentOS encountered the pit
- Problems encountered in vs2015 configuration using OpenGL environment
- Flash back record of vs2017 installation process
- Ubuntu 18.04 installation of opencv2.4.13 encountered fatal error. Possible solutions
- Problems encountered in VTK installation
- DirectX encountered “unresolved external symbol” when compiling on vs2015__ The solution and reason of “vsnwprintf”
- The installation of Homebrew encountered a 400 Bad Request error
- VTK + QT + vs compilation and installation configuration
- Recording some pits of VTK + QT
- NPM installation module encountered enoent: no such file or directory, rename error
- Compiling QT project under vs encountered “error 89error msb6006:“ cmd.exe ”Exited with code 3