search

gucci-on-fleek / lockdown-browser

Run the ”Respondus Lockdown Browser“ in the ”Windows Sandbox“
Other
122 stars 23 forks source link

Does not work on VM #60

Open rbm2000 opened 7 months ago

rbm2000 commented 7 months ago

I went through all the steps, and I was able to get into a test. After I scrolled down a little bit I got a picture with a moose that told me a VM was detected and it promptly closed. This was ran on a VM, and there were no issues when ran on a host os.

gucci-on-fleek commented 7 months ago

This was ran on a VM, and there were no issues when ran on a host os.

Do you mean that you ran the Lockdown Browser inside the Windows Sandbox, all inside of another virtual machine (Hyper-V, VirtualBox, VMware, etc.)? Or do you just mean that you ran the Browser inside the Sandbox, which is running directly on your host computer?

al3naziiy commented 6 months ago

image

al3naziiy commented 6 months ago

pregnancy period. When I run it Vmware shows me this

rbm2000 commented 6 months ago

This was ran on a VM, and there were no issues when ran on a host os.

Do you mean that you ran the Lockdown Browser inside the Windows Sandbox, all inside of another virtual machine (Hyper-V, VirtualBox, VMware, etc.)? Or do you just mean that you ran the Browser inside the Sandbox, which is running directly on your host computer?

I ran the lockdown browser in the windows sandbox that was inside a windows 10 VM running off of vmware esxi.

al3naziiy commented 6 months ago

Can you help me explain this with pictures?

Note: The locked browser program was running inside the Vmware Work program and this error appeared in the image above

al3naziiy commented 6 months ago

Not work??!

gucci-on-fleek commented 5 months ago

@rbm2000

This was ran on a VM, and there were no issues when ran on a host os.

Do you mean that you ran the Lockdown Browser inside the Windows Sandbox, all inside of another virtual machine (Hyper-V, VirtualBox, VMware, etc.)? Or do you just mean that you ran the Browser inside the Sandbox, which is running directly on your host computer?

I ran the lockdown browser in the windows sandbox that was inside a windows 10 VM running off of vmware esxi.

Hmm, so that means that the Lockdown Browser is detecting that it's in a VM through some other way that this repo isn't blocking. There's a near-infinite number of ways that it could be doing this though, so I'd suggest going through the Device Manager and the registry and deleting anything that looks VM-y (from INSIDE the Sandbox).

But I'd check #65 and https://github.com/gucci-on-fleek/lockdown-browser/discussions/53#discussioncomment-8909229 before trying this since many people have been having issues lately.

al3naziiy commented 4 months ago

I ask you for a full explanation from the beginning of the step to the last. The video is not clear. I used the same thing in the video and it is rejected. I hope for a full explanation of the topic if possible. ![Uploading sandboxx.png…]()