Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GetLatestWinSDK assumes registry key will point to 32bit node for win10 sdk
See original GitHub issueFirstly I’m not entirely sure if this is a Visual Studio installer issue or DNNE but after running the visual studio installer to add the win10 sdk to the system the KitsRoot10 registry key is pointing to C:\Program Files\Windows Kits\10\ where the sdk’s files appear to actually be in the 32bit node’s location of Program Files (x86). As far as I can tell it seems like the win10 sdk always winds up in Program Files (x86) so I was curious if it made sense to instead have GetLatestWinSDK check the WOW6432Node for the sdk location to ensure it always pointed to the correct location?
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@UnityAlex Should be updated now.
Awesome! Thank you. I really appreciate the quick response & turnaround on this issue.