Skip to content
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.

Some registry keys left behind after running this tool #84

Open
ewanharris opened this issue Jul 12, 2017 · 0 comments
Open

Some registry keys left behind after running this tool #84

ewanharris opened this issue Jul 12, 2017 · 0 comments

Comments

@ewanharris
Copy link

Hey, firstly thanks for the tool!

Here's what I did

  • Install VS 2017, selecting the UWP workload
  • Uninstalled the workload
    • At this point I realized there was still some reg keys lying around
  • Ran this tool
    - Noticed there was still some reg keys lying around

Specifically the main key that is causing a problem is HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v10.0, I use this key to detect Windows 10 SDKs in some tooling.

I guess my questions are

  1. Is it expected for this tooling to remove that key?
  2. Do you know of a better (more reliable) way to detect Windows 10 SDKs on the system? I took a look through and maybe I should be using Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant