-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reimplementation methods to find DNS path via the registry #252
Reimplementation methods to find DNS path via the registry #252
Conversation
- wmi dependence removed for _winreg - does not use Win32_Product() - Renamed _validate_natspeak() to _validate_engine_path() as its engine agnostic
Remove the wmi package in command prompt or windows powershell.
|
- Yapf Formated
- Renamed exe_path to engine_path - Renamed DisplayVersion to DnsVersion for clarity as needed - Edited comments for clarity
As it would be helpful to try out many set ups as possible to make sure everything functions as expected. The registry can be a finicky thing. The following attachment is a reimplementation of the _find_natspeak(). For testing purposes it only prints to counsel. Three options
Example
The output should produce similar results
|
Thanks for testing! I'm able to reproduce the error |
During QueryValue the value of a subkey for each installed program.
DisplayName is undefined because of dirty registry keys or subkey does not have DisplayName string. |
…toolbox#252 Defines object variables as not all subkeys contain an object.
The error should be fixed. It took me a while to out puzzle why it was happening in the context of the code on different machines. |
It seems to be working for me (DNS 13 Home, Windows 10 Pro):
|
@mrob95 |
Yes, working now |
Do to issues #248 with Win32_Product and wmi I have re-implemented #242 #243 methods to find DNS path via the registry.
Overview of changes