when I build the DeviceQuery VS solution I get this error:
Severity Code Description Project File Line Suppression State
Error MSB8036 The Windows SDK version 10.0.15063.0 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting “Retarget solution”. deviceQuery C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\v141\Toolset.targets 36
I am using VS 2017 and windows sdk 10.0.16299. Should i install the 10.0.15063.0 instead?
The complaint started in 5-12-2015, and now it is October 2018!
The problem is a simple line in the documentation which claims that some exe files should be there, where they are not. Then you have do do some searches to find out the the documentation is wrong.
Can someone in NVIDA fix this please? It is just a very minor edit.
Hi，Tom
I just wanna know when can you guys handle this problem?
I already installed CUDA 10.0 ,cudnn10.0 and Microsoft Visual Studio 2017.But I CAN’T to build the .exe files.The installation location of the CUDA and cudnn is the default,but VS2017 is not,when I build the Samples_vs2017.sln, VS 2017 will say that some files didn’t import such as CUDA 10.0.props etc.
OK, I’ve had this problem with CUDA Toolkit 10 under Windows 10. In my case, I do never use the admin account, and the installation was done from the user account, entering the admin password when necessary. After repeated trials, here’s what worked for me:
Make sure to uninstall any old version of CUDA and Visual Studio (just to have a clean start)
Restart the computer
Install Microsoft Visual Studio Community Edition. During the install, make sure to select the C++ Development tools
Restart
Install the Cuda Toolkit
Restart
With this, I had all the files. But the deviceQuery still would not compile because it was targeted to an older version of Windows. To compile it, one needs to ‘Retarget’ the project to the current windows SDK. However, this doesn’t work out-of-the-box because the ‘deviceQuery_vs2017.vcxproj’ file is read-only for regular users.
So, there are two possible solutions:
Copy the folder to some place where you have write permission, or
(This is what I used, for convenience) Using Windows Explorer, navigate to the `C:\ProgramData\NVIDIA Corporation` directory. Right click on the 'CUDA Samples' directory, select 'Properties'. Under the 'Security' tab, click 'Edit' and add your user to it.
This way you can Retarget the solution in place. After that, I could open the solution in MS Visual Studio, Retarget it, build it and test it, and all worked fine.
Hey, I had the exact same problem today. I could not find DeviceQuery in file explorer or in the directory listed on the instructions page. Since this is a quick fix and the R Tensorflow interface still requires v10.1,
I thought I might update this conversation; though I do realize it is old. This solution is different than the ones discussed and works as of Feb 2021 for v10.1. So who knows what solution will work for whom…The documentation is still not updated to cover this particular issue from what I found.
I located deviceQuery VS file in the following directory:
C:\ProgramData\NVIDIA Corporation\CUDA Samples\v10.1\1_Utilities
After locating the file I built it in MS Visual Studio.
I had to move the subsequent deviceQuery.exe to a different folder other than the one specified above, in this case I chose the Documents folder. From here I could run it from the command line and avoid the blinking screen issue mentioned by Toan_Le.
Hope this helps anyone else who encounters this. Sorry if I am beating a dead horse.
In case anyone was as clever as me and installed Visual Studio in German: “build solution” is called “Projektmappe erstellen” - you can find it at “Erstellen” in the menu bar.
Thank you for posting this. From the few forum questions I have glanced at so far, there is a general lack of motivation for NVIDIA support to actually answer user issues. Strange.
Here are some useful links, the first of which should linked-to in the official installation guide.
If you get an error about the environment variable TRACEDESIGNTIME, go to your environment variables and create a new one named TRACEDESIGNTIME and set the value to true.
Thanks Pinkshanck thanks to all; I have read the references that you have kindly left but I have not yet been able to resolve; like you i am having many difficulties in installing the cuda qualifications on my pc.
sorry for my english seasoned italians are not very attracted to languages … however the translator helps … I state I first installed the incorrect versions of cuda (cuda 11.5) and VS 2019 then I uninstalled everything and installed the correct versions for the my driver: the cuda 9.1 for 392.67 display driver and VS 2017 at this point not finding “deviceQuery” I found in the folder C: \ ProgramData \ NVIDIA Corporation \ CUDA Samples \ v9.1 \ Samples_vs2017.sln
from the forum I understood that by compiling this file solution with VS2017 I would have had to get the “deviceQuery” program … unfortunately VS 2017 does not open the file correctly, not finding a long list of references how can I solve it ?? maybe during the uninstallations not everything is deleted? then reinstalling some files are not copied? I am not a programmer so imagine my difficulty … however I do not give up.
I’m waiting for help from someone or useful advice thanks and greetings
For those who might visit this thread again in the search of deviceQuery.exe, here is one quick solution I am using without build dependency on VS2017
Just build the exe using makefile present in the respective samples folder and you can do it in windows as well. Few line edits in the make file, install the makefile for windows and you won’t be solely dependent on VS versions (Ofcourse you will still need the cl.exe else try gcc)