-
Notifications
You must be signed in to change notification settings - Fork 26
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
Opening Sandbox.wsb doesn't open lockdown browser, and when trying the workaround, it does not work #44
Comments
Check the location of your exe is correct, it may vary by name if you are using an OEM browser. |
This suggests that the installer didn't run properly for some reason. Is there an icon for the Browser somewhere on the Sandbox's desktop? If not, then the Browser isn't even installed, so there's no point in trying to run it. If there is an icon, then @bluesangheili's comment
If the Browser didn't install properly, you can try manually installing it in the Sandbox (double-click on the installer, click through the wizard, etc.), then try running that workaround again. |
Thanks for responding. I will try out your solutions whenever I come back home. Right now I am unable to do it at this moment. |
I am having a similar issue where nothing happens when I open the sandbox. The runtime directory is on the desktop, and the lockdown installer is in there too. If I try to install lockdown browser manually i get the message that lockdown cannot be run in virtual environments VMs etc. Any ideas? |
Have you tried the steps listed in the main instructions?
|
@gucci-on-fleek I fixed it. I think you will find this interesting. First, to answer your question, no I didn't try that because I wasn't getting an error, just nothing was happening once the sandbox opened. I tried a few troubleshooting steps like reinstalling the lockdown browser installer, the git repository, even sandbox, but nothing worked. I restarted my computer, nothing. I eventually got it to work by updating my computer to windows 11 from windows 10. I don't know why this works, but it did. What I find interesting is that I had this working on windows 10 a few days ago, just yesterday it didn't want to work but as soon as I updated my computer to windows 11, it was working perfectly. Figured I would post that info here incase it's of any value to you are anybody running into the same issue. |
Well that's an unexpected solution, but I'm glad to hear that it worked. Thanks for the update. |
PS C:\Users\WDAGUtilityAccount> cd C:\Users\WDAGUtilityAccount\Desktop\runtime_directory\
Any ideas on what the issue is / work arounds?
The text was updated successfully, but these errors were encountered: