2.1.2.08 get detected

[alagouna6]

Common issues

• If you get a "Terminal Services" error message, have you tried the troubleshooting steps from the main instructions?

• If you get a "the setup configuration provider is not registered" error message, have you installed the "Visual Studio C++ Tools"?

• You have tried rebuilding from scratch (Reset your build with ./build.ps1 -Clean, and it will reset your workspace and build.).

Issue

please can anyone help to skip this issue with 2.1.2.08 with windows 10 pro 22h2 without minimize sandbox (just alt+tab)
i get this after submit the exam and try to open it again after third one i get blocked
my lms need to open exam by link from browser then redirect me to lockdown browser

Expected Behavior

.

Error Messages

No response

Lockdown Browser Variant

Lockdown Browser (no webcam)

Lockdown Browser Version

2.1.2.08

Windows Version and Build

windows 10 pro 22h2 Version 10.0.19045 Build 19045

Repository version

last version (default )

Other

No response

[cachebag]

Do not try this again, you will probably get banned.

Can you be more clear with when this message popped up? Did you finish your exam and_then_ you got this message?

i get this after submit the exam and try to open it again after third one i get blocked

So you submit the exam, and then tried to open LDB again through the Sandbox and got this message?

Did you try and rebuild using build.ps1 before opening it again?

There's no concrete fix for bypassing the detection. You must have done something to trigger it.

Were you able to freely navigate LDB before doing the exam? Did this only happen when you started/finished your exam?

[alagouna6]

Do not try this again, you will probably get banned.

Can you be more clear with when this message popped up? Did you finish your exam and_then_ you got this message?

i get this after submit the exam and try to open it again after third one i get blocked

So you submit the exam, and then tried to open LDB again through the Sandbox and got this message?

Did you try and rebuild using build.ps1 before opening it again?

There's no concrete fix for bypassing the detection. You must have done something to trigger it.

Were you able to freely navigate LDB before doing the exam? Did this only happen when you started/finished your exam?

i open the exam for first time normal and use (alt + tab) then i submit it
after that i try to submit again with same things (its a test exam ) but get that message
yes i try to rebuild before second attempt but the same thing
i try different lms and different computers (windows 10 and windows 11) but the same problem

[alagouna6]

Do not try this again, you will probably get banned.

Can you be more clear with when this message popped up? Did you finish your exam and_then_ you got this message?

i get this after submit the exam and try to open it again after third one i get blocked

So you submit the exam, and then tried to open LDB again through the Sandbox and got this message?

Did you try and rebuild using build.ps1 before opening it again?

There's no concrete fix for bypassing the detection. You must have done something to trigger it.

Were you able to freely navigate LDB before doing the exam? Did this only happen when you started/finished your exam?

bro if you are now work on 2.1.2.08 and that's working fine with you tell me what are use
ex i must change 2.1.2.08 setup exe and use another one ?

[cachebag]

Do not try this again, you will probably get banned.
Can you be more clear with when this message popped up? Did you finish your exam and_then_ you got this message?

i get this after submit the exam and try to open it again after third one i get blocked

So you submit the exam, and then tried to open LDB again through the Sandbox and got this message?
Did you try and rebuild using build.ps1 before opening it again?
There's no concrete fix for bypassing the detection. You must have done something to trigger it.
Were you able to freely navigate LDB before doing the exam? Did this only happen when you started/finished your exam?

bro if you are now work on 2.1.2.08 and that's working fine with you tell me what are use ex i must change 2.1.2.08 setup exe and use another one ?

I can't explain or understand why it will not work for you. Different schools have different systems in place for their instances of LockDown browser.

My school is running a 2 year old LDB Lab version through the Virtual Machines that they host. Does your school have anything like that? Perhaps those will work better for you than injection methods.

Like I said earlier, it's hard to tell what you're doing that's causing to your detection without specific log entries or anything like that.

[gucci-on-fleek]

@alagouna6

i get this after submit the exam [...]

Huh, I've never seen anyone get that message after submitting an exam, only during an exam. That's very interesting (albeit very unfortunate for you).

---

@cachebag

My school is running a 2 year old LDB Lab version through the Virtual Machines that they host.

Wait, your school is intentionally running the Lockdown Browser inside of a VM? And they're using a 2-year-old version? If so, that actually suggests that there might be some configuration flag that we can toggle that will make the regular Lockdown Browser be okay with using an older version and running inside of a VM.

[cachebag]

@gucci-on-fleek

Correct.

For more context: we have these Virtual Labs through VMWare (they call them Virtual Labs but they are literally just virtual machines) so students can run things that typically require licenses like MATLAB, Siemens, etc. These virtual labs can be run within a browser, or through VMWare's native client. In both instances, LDB opens up and even warns the user that the version is old and if they'd like to continue anyways.

To be specific, the variant of LDB they use is...

And the message that pops up before running it is...

Here is the full version info

I was able to run the practice exam all the way through. Alt+Tab, switching windows- basically operating my computer was (seemingly) completely undetected by VMware's VM.

This of course, only applies to my University, I'm not sure how other ones have their "Virtual Labs" setup.

If so, that actually suggests that there might be some configuration flag that we can toggle that will make the regular Lockdown Browser be okay with using an older version and running inside of a VM.

Can you elaborate on this? I'm now curious.

[gucci-on-fleek]

@cachebag

If so, that actually suggests that there might be some configuration flag that we can toggle that will make the regular Lockdown Browser be okay with using an older version and running inside of a VM.

Can you elaborate on this? I'm now curious.

Usually the Lockdown Browser refuses to run if it detects that it's in a VM or RDP is active (see #3 for an example of the message). But since you're successfully running it in a VM at your school, that means that this installation has been configured to bypass the VM detection stuff. And since the “This browser can't be used while Remote Desktop or Terminal Services are active” message shows up before the Browser connects to the network, that means that the “allow VMs” setting must be stored somewhere in the local installation.

So if we can find where this setting is and modify it, then that means that we'd be able to configure anybody's Lockdown Browser installation to be okay with running inside of a VM, which would completely resolve #132. Of course, it's possible that Respondus made a special one-off build specifically for your school with the VM checks disabled, but this still looks like an interesting avenue to explore.

[cachebag]

@gucci-on-fleek

I'd be happy to look into this. I'm not sure how feasible it would be for me to get any de-compiling tools on the VM but I'm more than happy to try. If there's anything you'd like me to try and sniff out, feel free to let me know and I can just update you here or open a PR once I figure it out.

[alagouna6]

Do not try this again, you will probably get banned.
Can you be more clear with when this message popped up? Did you finish your exam and_then_ you got this message?

i get this after submit the exam and try to open it again after third one i get blocked

So you submit the exam, and then tried to open LDB again through the Sandbox and got this message?
Did you try and rebuild using build.ps1 before opening it again?
There's no concrete fix for bypassing the detection. You must have done something to trigger it.
Were you able to freely navigate LDB before doing the exam? Did this only happen when you started/finished your exam?

bro if you are now work on 2.1.2.08 and that's working fine with you tell me what are use ex i must change 2.1.2.08 setup exe and use another one ?

I can't explain or understand why it will not work for you. Different schools have different systems in place for their instances of LockDown browser.

My school is running a 2 year old LDB Lab version through the Virtual Machines that they host. Does your school have anything like that? Perhaps those will work better for you than injection methods.

Like I said earlier, it's hard to tell what you're doing that's causing to your detection without specific log entries or anything like that

No bro, unfortunately my university do not using vm labs
ok lets me explain
my university doesn't offer practice test for lockdown so i use the setup exe from the university (2.1.2.08) with blackboard (free trial ) and create test exam by myself
after first attempt noting happened but when i start new attempt after 10 second i get that message

[alagouna6]

@alagouna6

i get this after submit the exam [...]

Huh, I've never seen anyone get that message after submitting an exam, only during an exam. That's very interesting (albeit very unfortunate for you).

@cachebag

My school is running a 2 year old LDB Lab version through the Virtual Machines that they host.

Wait, your school is intentionally running the Lockdown Browser inside of a VM? And they're using a 2-year-old version? If so, that actually suggests that there might be some configuration flag that we can toggle that will make the regular Lockdown Browser be okay with using an older version and running inside of a VM.

yes bro during second attempt

[alagouna6]

here is my university setup 2.1.2.08 can you please check it

https://drive.google.com/file/d/1UsOEy0J5h3SLknDlrZtpQEeksUaSs7z3/view?usp=sharing

[cachebag]

here is my university setup 2.1.2.08 can you please check it

https://drive.google.com/file/d/1UsOEy0J5h3SLknDlrZtpQEeksUaSs7z3/view?usp=sharing

We can't fix this for you- I've already mentioned that if your School has a different protocol for LDB instances, there is not a way around that unless you can go digging and find out what they're doing to detect you.

Or, you probably are doing something to be detected yourself but just don't know it.