-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
wslview fails when registry access is disabled #291
Comments
I found the
|
I've been walking through the code to see what can be done without checking the registry. Looks like the biggest offender is getting the Windows build number. I've found a reliable fallback which I've patched into my installed version, and it's much quieter, but not completely error-free.
|
It also looks like the codepage variable isn't being set which is causing the Powershell errors. This can also be handled by (ironically) calling Powershell as above:
|
And with those two patches, I'm not hitting
|
Windows Version
Windows 11
Windows Build Number
22621.2428
WSL Version
WSL 2
Distro Version
Debian 12
WSL Utilities Version
4.1.1
Describe the bug
On a corporate GPO-managed Windows workstation where group policy prohibits access to the registry, multiple calls to
reg.exe
fail with errors, leading to internal failures in the utility and broken functionality. Pages do load in my Windows browser, so obviously these calls to the registry aren't core to the functionality. Would be really great to either not depend on REG at all, or have an option flag to not check whatever it is trying to check.Steps to Reproduce
$ wslview "http://github.com"
Expected behavior
Script runs quietly and launches Windows web browser, without several lines of error messages.
Additional context
Error stream output from script:
Code of Conduct
The text was updated successfully, but these errors were encountered: