– CUDA10.0 failed installation
is basically due to a visual studio integration installation failure. As shown in the figure.
-
solution 1
. Find the graphics card related options in the driver management
2. Stop associated service
3. Delete all folders associated with NVIDIA (C:\ data, C:\Program Files, C:\Program Files(x86)NVIDIA associated folders). 4. Restart -
. If the problem cannot be solved
is largely because the installation of visual studio version is incompatible with CUDA10.0 version, it can be solved by installing CUDA9.0 version. This installment was successfully installed with visual studio2015.
there is also a way to uninstall visual studio integration by selecting custom installation at installation time. However, after this installation, you will not be able to create CUDA if you create Pj with Visual Studio. Solution reference links: https://blog.csdn.net/zzpong/article/details/80282814 p> li> ul>
Reference URL:https://devtalk.nvidia.com/default/topic/1033111/cuda-setup-and-installation/cuda-9-1-cannot-install-due-to-failed-visual-studio-integration/p>
Read More:
- CUDA Visual Studio Integration Installation failed
- There are three ways to deal with the problem of vs (Visual Studio) 2017 flashback. I feel that none of them is the fundamental solution.
- Non 7z achieve. Error reported during CUDA installation. Solution: the installation file is damaged
- Visual Studio 2010 compilation error fatal error lnk1123: failed during conversion to coff: solution to invalid or corrupt file
- Solution to the flash of visual studio console program output window
- Successfully solved the problem that visual studio code could not go to the definition, and there was no mouse prompt
- How to solve the problem that the console window disappears in a flash after visual studio 2017 runs
- Detailed steps for installing Visual Studio 2010 + Intel parallel studio Xe 2013 and configuring mpich2
- Flashback problem of output window of visual studio 2017 console program
- Visual Studio 2005 — Error code 1603 for this component means “Fatal error during installation.
- PIP installation error: Microsoft Visual C + + 14.0 is required perfect solution
- Solution to the flashback of visual studio output window
- Solution to the flash of visual studio 2017 running program
- Visual studio 2017, OpenGL program running prompt glut32.dll missing solution
- The solution of windows not flashing back when visual studio console program is running
- Vs (Visual Studio) encountered a solution that could not open iostream
- Solve the problem of flash back in Visual Studio 2010
- Solution to flash back of visual studio 2017 running program
- Android studio installation virtual machine error ® HAXM installation failed.
- The solution to the black window flash of running program on Visual Studio