"This browser can't be used while Remote Desktop or Terminal Services are active"

[lolzz1234]

"This browser can't be used while Remote Desktop or Terminal Services are active"

[gucci-on-fleek]

I think that this tool is unfortunately broken with versions ≥ 2.1.2.04; see #65 and #53 (comment). It could be something else though, so you can try all the fixes listed in “Common Solutions” (although I doubt that that will help anything).

[Bible567]

I encountered the same error described in the image posted by the user who opened this issue. The error was: "This browser can't be used while Remote Desktop or Terminal Services are active." By following the suggestion in the "common solutions" section for "Terminal Services," I ran the recommended code and managed to reach the login screen without seeing the error anymore.

However, I am now worried that if I proceed with the login, I might get banned. I tried restarting the sandbox without executing the suggested code, and the error reappeared. This indicates that the only way to bypass the error is by running the recommended code in the sandbox shell prompt.

Additionally, every time I start the sandbox, I get the message "Downloading an update." When I check the properties of Respondus in the sandbox, under links and file path, I noticed there is a new Respondus file dated today. Although I have version 2-1-1-03, when I reach the login screen, it indicates that I am using version 2-1-2-04 of Respondus. This makes me think there is an automatic update of Respondus in the sandbox.

I am seeking your advice on how to proceed. Is it safe to log in after running the suggested code, or do I risk getting banned? Has anyone had similar experiences and can offer suggestions?

[gucci-on-fleek]

@Bible567

This makes me think there is an automatic update of Respondus in the sandbox.

Yes, correct.

I encountered the same error described in the image posted by the user who opened this issue. The error was: "This browser can't be used while Remote Desktop or Terminal Services are active." By following the suggestion in the "common solutions" section for "Terminal Services," I ran the recommended code and managed to reach the login screen without seeing the error anymore.

[…]

I tried restarting the sandbox without executing the suggested code, and the error reappeared. This indicates that the only way to bypass the error is by running the recommended code in the sandbox shell prompt.

Additionally, every time I start the sandbox, I get the message "Downloading an update."

Given the circumstances that you describe, the error dialog is to be expected. What's happening is that when you open the Sandbox, it installs the Lockdown Browser, then launches it with the GetSystemMetrics-Hook.dll hook. But since there's an update available, when you open the Browser, instead of showing your school's home page, it downloads and installs an update, then relaunches itself without the GetSystemMetrics-Hook.dll hook. But since it's now updated itself, when you relaunch it with withdll.exe /d:GetSystemMetrics-Hook.dll … it works as normal.

The best fix here is to download an updated Browser installer .exe, but your current approach of letting it update itself then manually starting it with withdll.exe /d:GetSystemMetrics-Hook.dll … should be fine too.

However, I am now worried that if I proceed with the login, I might get banned.

When I check the properties of Respondus in the sandbox, under links and file path, I noticed there is a new Respondus file dated today. Although I have version 2-1-1-03, when I reach the login screen, it indicates that I am using version 2-1-2-04 of Respondus.

I am seeking your advice on how to proceed. Is it safe to log in after running the suggested code, or do I risk getting banned? Has anyone had similar experiences and can offer suggestions?

A few points:

1. 2.1.2.04 is a “bad” version according to #65 and #53 (comment).

2. Back when I first made this tool (November 2020), the Browser would either refuse to start up entirely and give you an error message, or everything would work perfectly—there were no circumstances where it would appear to work and let you login but then later detect that it was running in the Sandbox.

3. At some point, the Browser was updated so that (at least sometimes) it would let you launch an exam before it would show an error message. See #65 (comment) and https://ericswpark.com/blog/2024/2024-02-20-i-hate-lockdown-browser/#theres-a-second-lockout for some examples.

4. Based off of some of the comments that I've seen, this tool maybe still works for some people—but it's tough to say since people generally only post issues here when things don't work.

5. Some people have gotten banned from using the Browser after being detected (see #65, #70, and #71). These bans appear to be linked to your school account, so the only way to fix it would be to have a very awkward conversation with your school administrators.

   But even in cases where the student wasn't doing anything sketchy (like using this tool), I've seen reports where Respondus still refuses to lift the ban, even if asked directly by a teacher.

6. In all the reports that I've seen, you get a warning before you get banned, so in theory it's safe to test this with a real exam exactly once. But even if you only get a warning, it still might notify your teacher.

So there's no clear-cut answer either way for whether or not it's safe to use this tool; it comes down to your personal risk tolerance.