![]() |
So I’ve had things working fine on linux and now i’m trying to set up the same on windows so I can use the newer gpu in a new machine. The problem is that after install of both CUDA toolkit and cuDNN, the libraries are never picked up even after several restarts. I’ve searched quite a bit and haven’t turned up anything that works, and don’t know of a way to get Windows to look in the new PATH variable that the installer did properly set up. These are the offending libraries One thing to note is that when I copy the offending dynamic libs to System32, my run on the command line picks up the libraries and detects my gpu as it should. So something’s happening with searching for them in another PATH, I just don’t know how to fix it. This sort of thing rarely happens on linux and even when it does, ldconfig is usually the answer. Update: I tried something I didn’t think would work, but it turns out it did. I originally downloaded python from the windows app store because I figured it would save some time and python using scoop as the installer wasn’t working. I uninstalled the windows app store version of Python 3.8 and installed the same version from the python organization’s website, and now everything is working. I’m not sure what the issue is with windows app store downloads, but i’ve had an incident with Slack via the same method. The issue with Slack was completely different, but from what I can tell, python was installed in a different location from the windows store than it normally would’ve been, and I think that contributed somehow. On linux, there’s 4 folders anything could ever be installed to automatically by convention, so we don’t run into this specific problem on the platform. That’s why troubleshooting this was so tiresome. submitted by /u/CrashOverride332 |
Categories
Detecting CUDA libraries on Windows
![](http://databloom.com/wp-content/uploads/2022/01/HYemuiiyD_Yj8SAOBlDWgOWWgW-sQzM66HksN_mV5fg-WZRIsz.jpeg.pagespeed.ce.PhI3FsFbJu.jpg)