# HELP \\ Bypass “close other app first” detection on Windows (no VM/Sandbox) **URL:** \ **Category:** Discussion & Solutions\ **Tags:** solved\ **Created:** [July 27, 2026, 10:18pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194 "2026-07-27T22:18:53Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![alshekbahaa](https://onehack.st/user_avatar/onehack.st/alshekbahaa/32/159799_2.png) [@alshekbahaa](https://onehack.st/u/alshekbahaa)\ **Post date:** [July 27, 2026, 10:18pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/1 "2026-07-27T22:18:53Z")
Hi everyone, I’m looking for a **Windows method or tool** to **bypass a restriction** enforced by an application. **Problem:** When I launch app **(A)**, it scans the system, detects that app **(B)** is running, blocks startup, and asks me to close **(B)** first. **What I want:** - Bypass this check/restriction - Keep **(B)** running and active - Run **(A)** at the same time - Without uninstalling **(B)** and without fully stopping it **To be clear:** I don’t mean only hiding **(B)** from the installed-apps list. I mean **stopping (A) from detecting that (B) is currently running** (e.g., process/window concealment or similar session-level techniques). **Note:** I’m **not** looking for **VMs** or **Sandbox** solutions. Please suggest other practical tools/methods if you know any. Any useful tips are appreciated. Thanks. ---
**Author:** ![teodor11](https://onehack.st/user_avatar/onehack.st/teodor11/32/158489_2.png) [@teodor11](https://onehack.st/u/teodor11)\ **Post date:** [July 28, 2026, 1:59pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/2 "2026-07-28T13:59:45Z")
Your problem is that you started App B and then wanted to install, uninstall or update App B using App A! You will have to close App B. By the way, what are the 2 applications you are talking about? If you tell me I could give you the solution! I searched the net and found the following solutions. \*\*To bypass or force-close the background programs triggering the \*\* \*\*“Close other app first” block in Windows 10, you must terminate \*\* \*\*the conflicting background processes using Task Manager or \*\* \*\*Command Prompt. Windows triggers this warning when an installer, \*\* \*\*uninstaller, or updater detects that an active instance of the \*\* **program (or a related dependency) is still running in the background.** **Force-Close the Blocked App via Task ManagerPress:** **1.Press Ctrl + Shift + Esc to open the Windows Task Manager.** **2.Click More details at the bottom if you are in the compact view.** **3.Switch to the Details tab at the top to see exact executable files.** \*\*4.Look for the name of the app you are trying to update or install \*\* **(e.g., Teams.exe, Discord.exe, or msiexec.exe).** \*\*5.Right-click the process and select End process tree to kill it \*\* **and all associated hidden processes.** **Bypass Stuck Installers via Command Prompt:** \*\*If you are getting a similar “Another installation is in progress” \*\* \*\*or an installer is locked, you can clear it instantly via the \*\* **command line:** \*\*1.Right-click the Start Menu and select Command Prompt (Admin) or \*\* **Windows PowerShell (Admin).** \*\*2.Type the following command in CMD to forcefully kill any stuck installation \*\* **engines and press Enter:** **taskkill /f /im msiexec.exe** **3.If a specific app like Zoom or Chrome is blocking you, swap the image name:** **taskkill /f /im zoom.exe** **Terminate Stuck Windows Store Singletons** **If the error occurs within the Microsoft Store while updating apps:** **1.Open Windows Settings (Win + I) and click on Apps.** \*\*2.Search the list for Microsoft Windows App Runtime Singleton \*\* **(or the specific app failing to update).** **3.Click on it, choose Advanced options, scroll down, and click Terminate.** **4.Return to the store and click Retry.** **Prevent the App from Auto-Starting** \*\*If the application launches itself silently every time you reboot, \*\* **you can block its startup permissions:** \*\*-Open Task Manager, click the Startup tab, select the app, \*\* **and click Disable.** \*\*If you are still unable to bypass the message, let me know \*\* \*\*the exact name of the app you are trying to open or install \*\* **so I can give you the precise background process name to kill.** ---
**Author:** ![BlueHacker](https://onehack.st/user_avatar/onehack.st/bluehacker/32/174721_2.png) [@BlueHacker](https://onehack.st/u/BlueHacker)\ **Post date:** [July 29, 2026, 12:27am UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/3 "2026-07-29T00:27:55Z")
![Close it first is just a scan - make it see nothing](https://onehack.st/uploads/default/original/3X/b/8/b885b5432431dcae1bae5dea4dbaecee69337b88.jpeg) You’ve got it exactly right — this isn’t “close B,” it’s “make A **not see** B.” 🎯 (@teodor11’s steps are for a different problem — an installer that’s genuinely still running.) Here’s the thing A won’t tell you: **“close B first” is just what A prints when its scan finds B.** A doesn’t need B gone — it needs its scan to come back empty. And a scan only ever looks at _one_ surface: B’s **process name** , B’s **window** , or a **“already running” lock** (a named mutex). Break that one signal and both run. Two ways in 👇 ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 🟢 The no-reversing shortcut (try this first) A only scans **its own login session and desktop.** So put B somewhere A never looks — no hiding, no patching, no VM: ├─ 👥 **Run B as a second Windows user** → **[RunAsTool](https://www.sordum.org/8368/runas-tool-v2-1/)** (one click, save the login) or **[AdvancedRun](https://www.nirsoft.net/utils/advanced_run.html)** / **[RunasCs](https://github.com/antonioCoco/RunasCs)**. B lives in another session → A’s scan can’t reach it, B stays fully running └─ 🖥 **Run B on a separate desktop** → **[Desktops (Sysinternals)](https://learn.microsoft.com/en-us/sysinternals/downloads/desktops)**. `FindWindow`/`EnumWindows` only see the caller’s desktop, so A on the main desktop is blind to B’s windows That alone fixes most “close it first” apps. If A digs deeper, break the exact signal 👇 ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 🔬 Step 1 — make A show you _how_ it finds B Point a tracer at A’s launch and it prints the exact call **and the exact name/title/mutex it’s hunting** — that one line tells you your fix: ├─ ⚡ **[Frida](https://github.com/frida/frida)** → `frida-trace -i "Process32Next*" -i "FindWindow*" -i "OpenMutex*" -p ` — logs every check with its arguments ├─ 🖱 **[WinAPIOverride](http://jacquelin.potier.free.fr/winapioverride32/)** — no-code: watch the call _and_ force it to return “not found” in the same tool └─ 🧾 **[Dependencies](https://github.com/lucasg/Dependencies)** (peek A’s imports first) · **[Process Monitor](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon)** (catch a registry/mutex probe) **Match what you see to your move:** | A calls… | it’s checking | break it → | | --- | --- | --- | | `Process32Next` · `EnumProcesses` · `NtQuerySystemInformation` | B’s **exe name** in the process list | rename/repack B, hide it, or hook the list | | `FindWindow` · `EnumWindows` | B’s **window title/class** | rename or hide B’s window | | `OpenMutex` · `CreateMutex` | B’s **single-instance lock** | close or rename the mutex | ━━━━━━━━━━━━━━━━━━━━━━━━━ > **🧬 A scans the process list (by exe name) — 3 ways to vanish B** > > ├─ ✏ **Rename B’s identity on disk** → **[CFF Explorer](https://ntcore.com/?page_id=388)** (rename the PE + rewrite company/version strings) · **[Resource Hacker](https://www.angusj.com/resourcehacker/)** (baked-in strings) · **[UPX](https://github.com/upx/upx)** (repack → new hash, beats a hash check). Enough when A only greps a name/hash > ├─ 🫥 **Hide B from the list entirely** → **[M00nRise/ProcessHider](https://github.com/M00nRise/ProcessHider)** (ready EXE/PowerShell, hooks `NtQuerySystemInformation`) · **[JKornev/hidden](https://github.com/JKornev/hidden)** (kernel mini-filter — drops B from every enumeration API) > └─ 🎣 **Make A’s own scan lie** (surgical) → inject a hook into A that filters B out of the results it gets: **[Microsoft Detours](https://github.com/microsoft/Detours)** (official) · **[MinHook](https://github.com/TsudaKageyu/minhook)** (tiny, hooks `NtQuerySystemInformation`) · or **[Frida](https://github.com/frida/frida)** `Interceptor.replace` — no recompile > **🪟 A scans open windows (title or class) — rename or hide B's window** > > ├─ 🏷 **Rename B’s window at runtime** → **[AutoHotkey](https://github.com/AutoHotkey/AutoHotkey)** one-liner `WinSetTitle` · **[window-title-spoofer](https://github.com/jmazzola/window-title-spoofer)** (rename by PID). A’s `FindWindow`-by-title stops matching > ├─ 🙈 **Hide the window off the enumerable surface** → **[NirCmd](https://www.nirsoft.net/utils/nircmd.html)** `win hide title "B"` · **[WinLister](https://www.nirsoft.net/utils/winlister.html)** (list every window + class, then hide) > └─ 🔎 First read B’s exact title **and class** (A may match either) → **[WinLister](https://www.nirsoft.net/utils/winlister.html)** / WinSpy++ > **🔒 A checks a single-instance mutex (the classic 'already running') — close it** > > ├─ 👀 **See the lock’s real name** → **[Process Explorer](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer)** (Ctrl+F a mutant name) · **[WinObj](https://learn.microsoft.com/en-us/sysinternals/downloads/winobj)** (read the literal string A’s `OpenMutex` compares against) > ├─ ✂ **Close it live, no restart of B** → **[System Informer](https://github.com/winsiderss/systeminformer)** → B’s handles → right-click the Mutant → Close · or **[Handle](https://learn.microsoft.com/en-us/sysinternals/downloads/handle)** `handle -c` from a script > └─ 🧭 Or sidestep it → run B in a different session (**[PsExec](https://learn.microsoft.com/en-us/sysinternals/downloads/psexec)** `-u`) so its `Local\` mutex lands in a separate namespace and never collides > **🎯 A is stubborn / you want to read its logic — pin the exact check** > > ├─ 🧠 **Static** → **[Ghidra](https://github.com/NationalSecurityAgency/ghidra)** decompiles A to show the detection routine (which string/mutex/API) before you even run it · **[PE-bear](https://github.com/hasherezade/pe-bear)** narrows the imports > ├─ 🐞 **Live** → **[x64dbg](https://github.com/x64dbg/x64dbg)**: attach to A, `bp OpenMutexW`/`FindWindowW`, watch the exact value it tests, then NOP the branch that decides “B is running” > └─ 🛡 If A fights the debugger → **[ScyllaHide](https://github.com/x64dbg/ScyllaHide)** (user-mode) / **[TitanHide](https://github.com/mrexodia/TitanHide)** (kernel) hide your debugger so you can still step the scan > **🧱 Bulletproof, still no VM — box B so A physically can't reach it** > > ├─ 🔐 **[Process Governor](https://github.com/lowleveldesign/process-governor)** — wrap B in a Windows **Job object** with UI-handle limits, so B can’t touch window objects outside its box (a real enumeration boundary, on bare metal) > └─ 👥 **[ShellRunas](https://learn.microsoft.com/en-us/sysinternals/downloads/shellrunas)** / RunasCs — a dedicated second local account for B is the cleanest permanent split; A’s same-user scan never sees another user’s processes or windows ━━━━━━━━━━━━━━━━━━━━━━━━━ The whole trick: A’s block is a scan result, and a scan reads one surface. See which surface, change what B looks like there — or move B to a session A never scans. B keeps running; A opens like B was never there. _“Close it first” is a question, not a lock — answer “nothing’s running” and the door opens._ ---
**Author:** ![teodor11](https://onehack.st/user_avatar/onehack.st/teodor11/32/158489_2.png) [@teodor11](https://onehack.st/u/teodor11)\ **Post date:** [July 29, 2026, 7:14am UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/4 "2026-07-29T07:14:49Z")
BlueHaker, congratulations, excellent analysis. Unfortunately the methods and software presented by you are very advanced! You are using methods and software used in Hacking, which a regular user like Mr. ASLHEKBAHAA DOES NOT UNDERSTAND AND CANNOT USE! For example: -FRIDA - Is an dynamic instrumentation toolkit FOR DEVELOPERS, REVERSE-ENGINEERS, and security researchers. -WinAPIOverride is an advanced API MONITORING software for 32 and 64 bits processes. -Dependencies - can help Windows DEVELOPERS troubleshooting their dll load dependencies issues. … and many others No offense but I think Mr. ASLHEKBAHAA IS NOT A DEVELOPER, because he would not have asked the question and would have solved it himself!! Congratulations again for your excellent analysis. ---
**Author:** ![BlueHacker](https://onehack.st/user_avatar/onehack.st/bluehacker/32/174721_2.png) [@BlueHacker](https://onehack.st/u/BlueHacker)\ **Post date:** [July 29, 2026, 10:50am UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/5 "2026-07-29T10:50:17Z")
Fair point 👍 — Frida/WinAPIOverride are only if you want to crack the exact check. But the **easy** path in my post needs zero hacking, and it’s the first thing there: → Run **App B as a second Windows user** with **[RunAsTool](https://www.sordum.org/8368/runas-tool-v2-1/)** (one click), or on a **separate desktop** with **[Desktops](https://learn.microsoft.com/en-us/sysinternals/downloads/desktops)**. App A only scans its own session, so it simply can’t see B — both keep running, no coding. That part’s for exactly the non-dev case you mean. 🙂 ---
**Author:** ![teodor11](https://onehack.st/user_avatar/onehack.st/teodor11/32/158489_2.png) [@teodor11](https://onehack.st/u/teodor11)\ **Post date:** [July 29, 2026, 2:22pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/6 "2026-07-29T14:22:51Z")
Hi BlueHacker! **You misunderstood.** I was referring to the solution from point 1. down. Otherwise you are right. It was very simple to stop App B. Run App A and then Run if App B is still needed. But we still don’t know which are the 2 applications A and B, because it is very important. The solution may be different from one application to another!!!. So let ALSHEK BAHAA tell us which are the 2 Applications he is talking about. And I hope the situation is real not “invented” by him 😆. ---
**Author:** ![BlueHacker](https://onehack.st/user_avatar/onehack.st/bluehacker/32/174721_2.png) [@BlueHacker](https://onehack.st/u/BlueHacker)\ **Post date:** [July 29, 2026, 2:50pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/7 "2026-07-29T14:50:45Z")
**You never needed to know which A and B are — that’s the whole point.** The second-user / separate-desktop route never touches either app; it just drops B into a session A’s scan can’t reach. Same move for any pair. `run A then B` ❌ works only if A scans once, at launch `2nd user / separate desktop` ✅ B stays invisible even while A keeps re-scanning Their identity matters only if A goes looking _outside_ its own session — the lone job the tracer’s for. ---
**Author:** ![teodor11](https://onehack.st/user_avatar/onehack.st/teodor11/32/158489_2.png) [@teodor11](https://onehack.st/u/teodor11)\ **Post date:** [August 1, 2026, 12:46pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/8 "2026-08-01T12:46:14Z")
> [@teodor11](#): > > BlueHacker! Hi BlueHacker! 3 days have passed and ALSHEK BAHAA HAS NOT REACTED. Is it possible that this user is a BOOT? Maybe this user should be checked by the stuff Because if the user is a BOOT then from now on WE THE COMMUNITY, when we answer any request on this forum, will have to carefully analyze the question. Honestly, it seemed to me from the beginning that the question was purely theoretical, not referring to anything concrete. The message can appear in Win 10 for many reasons. WITH MOST RESPECT, teodor11 ---
**Author:** ![system](https://onehack.st/user_avatar/onehack.st/system/32/165705_2.png) [@system](https://onehack.st/u/system)\ **Post date:** [August 1, 2026, 1:45pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/9 "2026-08-01T13:45:26Z")
@teodor11 Reviewed on our side — the account is an established member (real read history, active here today), not a bot; the question’s legitimate, they simply went quiet. Nothing to flag, and a solid answer serves every future reader regardless. ✅ ---
**Author:** ![BlueHacker](https://onehack.st/user_avatar/onehack.st/bluehacker/32/174721_2.png) [@BlueHacker](https://onehack.st/u/BlueHacker)\ **Post date:** [August 1, 2026, 2:30pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/10 "2026-08-01T14:30:56Z")
![Close other app first is just a scan - make it empty](https://onehack.st/uploads/default/original/3X/1/6/16b7dccf80c38325fe5243aafcb742d51006c1d3.jpeg) Quick truth before any tool: **“close App B first” isn’t a lock — it’s just what App A prints when a scan spots B.** A doesn’t need B _gone_; it needs its scan to come back **empty**. And that scan only ever checks one small thing — B’s **process name** , B’s **window** , an **“already-running” tag** (a _mutex_ = a one-copy flag), or a **claim on a file/device** (a _handle_). Make that one thing invisible and both apps run. No VM, no sandbox — you don’t even need to tell anyone which two apps you’ve got. ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 🟢 Start here — the 15-second fix, zero skill The most common reason is B’s “already-running” flag. Pop it with clicks, no code: 1. Grab 🔧 **[Process Explorer](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer)** — it’s Microsoft-signed, so your antivirus stays calm. 2. `Ctrl+F` → type App B’s name → it lists what B is holding. 3. Right-click the line marked **`Mutant`** (that’s the flag) → **Close Handle**. 4. Launch App A. Its scan finds nothing. ✅ Both run. ↳ Same move, plus stuck **file** locks: 🔧 **[System Informer](https://systeminformer.com/downloads)** (open, portable). ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 🔍 Not that one? Find YOUR reason in 10 seconds The message pops for different reasons — each reads a different surface, each has its own one-click grab-fix. Match your row: | Why it’s really blocking you | What A actually reads | Grab this → do this | | --- | --- | --- | | “B is already running” (2nd copy of same app) | a **mutex** (one-copy tag) | **Process Explorer** / **System Informer** → Close the `Mutant` | | A blocks _while_ B runs (overlay · wallet · recorder · rival) | B’s **process name** | **[Portapps](https://portapps.io/)** → run B under a different exe name | | A hunts B’s **window** | window **title / class** | **[WinLister](https://www.nirsoft.net/utils/winlister.html)** reads the exact title → **[NirCmd](https://www.nirsoft.net/utils/nircmd.html)** hides/renames it | | “Another app is using your camera/mic” | a **device handle** | **[Lavawall Monitor](https://www.lavawall.com/Camera_Mic_Speaker_Monitor.php)** → names it (even the browser _tab_) → Stop | | “File in use / another install in progress” | a **file handle** | right-click file → **[File Locksmith](https://github.com/microsoft/PowerToys)** (PowerToys), or **[OpenedFilesView](https://www.nirsoft.net/utils/opened_files_view.html)** → Close handle | | Can’t even find the flag’s name | a hidden **mutex/event** | **[WinObj](https://learn.microsoft.com/en-us/sysinternals/downloads/winobj)** → open `\BaseNamedObjects`, read it by name | ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 🚪 The move that beats ALL of them at once A only ever scans **its own login session.** Drop B into a _different_ session and every check above goes empty together — nothing to rename, nothing to close, still no VM/sandbox: ├─ 🖱 **[NirSoft AdvancedRun](https://www.nirsoft.net/utils/advanced_run.html)** — browse to B, set **Run As → a different user** , click Run. Save a `.cfg` for one-click next time. ├─ 💾 **[RunAsTool (Sordum)](https://www.sordum.org/8727/runastool-v1-6/)** — drag B in once → get a password-free desktop shortcut that always launches B in the other account. ├─ 🖥 **[Sysinternals Desktops](https://learn.microsoft.com/en-us/sysinternals/downloads/desktops)** — 199 KB; makes a 2nd desktop, run B there, hotkey back. Window scans can’t cross desktops. └─ 🛡 **[PowerRun (Sordum)](https://www.sordum.org/9416/powerrun-v1-9/)** — run B as SYSTEM/TrustedInstaller; beats A when it only checks _your own_ user’s processes. ━━━━━━━━━━━━━━━━━━━━━━━━━ ## 📦 Or don’t fight at all — grab a copy that has no lock ├─ 📦 **[Nucleus Co-Op](https://github.com/SplitScreen-Me/splitscreenme-nucleus/releases)** — a launcher whose per-app handlers auto-kill/rename the mutex + symlink a 2nd instance. Add a handler, hit play. └─ 🔗 **[Link Shell Extension](https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html)** — if A only checks _a file exists_, right-click → point that path at an empty target with a junction. Pure clicks. ⚠ **Skip the “clever” one that fails:** _freezing/suspending_ B doesn’t help — a paused app **still holds** its mutex, window and file locks, so A’s scan still hits them. Empty the surface, don’t pause the app. > **🧨 Heavier gear — only if the flag re-appears or a normal close won't take** > > - 🐉 **[HRSword / 火绒剑](https://github.com/szdyg/HRSword)** — Chinese kernel tool; its 句柄 (handle) view force-closes protected locks user-mode tools can’t touch. > - 💣 **[KillMutex](https://mojoware.org/p/source/kill_mutex.html)** — CLI that _deletes_ a named mutex even while it’s held; drop it in a `.bat` launcher. > - 🔁 **[GameMutexKiller](https://github.com/rosudrag/GameMutexKiller)** — watchdog that re-closes the mutex every 10s, for apps that instantly re-create their lock. > - 🎫 **[NSudo](https://github.com/M2TeamArchived/NSudo/releases)** — one dropdown runs B under a System/TrustedInstaller token. > - 🔐 **[RunAsSpc / RunAsRob](https://www.runasspc.com/)** — bakes B + a 2nd login into one encrypted file; double-click runs it as that user off a USB, no password shown. > - 🖧 **[RDP Wrapper](https://github.com/sebaxakerhtc/rdpwrap)** — unlock a 2nd concurrent Windows session, RDP into `127.0.0.2`, run B there. Different session ID = every `Local\` scan misses it. Free, not a VM. > - 🔎 **[WinObjEx64](https://github.com/hfiref0x/WinObjEx64)** / **[Handle CLI](https://learn.microsoft.com/en-us/sysinternals/downloads/handle)** — when the lock hides in `Global\`, or you want a reusable double-click `.bat` unlocker. ━━━━━━━━━━━━━━━ **A can’t block what its scan can’t see. Empty the scan, not the app.** ---
**Author:** ![system](https://onehack.st/user_avatar/onehack.st/system/32/165705_2.png) [@system](https://onehack.st/u/system)\ **Post date:** [August 1, 2026, 2:32pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/11 "2026-08-01T14:32:06Z")
> [@BlueHacker](#): > > [Close other app first is just a scan - make it empty] Quick truth before any tool: “close App B first” isn’t a lock — it’s just what App A prints … **🚀 The Core-Community team AI-improved the reply above.** ---
**Author:** ![alshekbahaa](https://onehack.st/user_avatar/onehack.st/alshekbahaa/32/159799_2.png) [@alshekbahaa](https://onehack.st/u/alshekbahaa)\ **Post date:** [August 2, 2026, 6:40am UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/12 "2026-08-02T06:40:17Z")
Hello friends, thank you all for your solutions. However, the issue is about how to hide application **(B), such as UltraViewer**, from application **(A) , which is LockDown Browser**, or any other application that works in the same way. That is what I meant. I tried several methods that were sent to me, but they did not work. I want application BB to function properly, whether it is UltraViewer or any other application; it is not limited to UltraViewer . ![001](https://onehack.st/uploads/default/original/3X/9/2/9238d4fcc54cf88b1a22327c20aa1fb6bb8a80ae.jpeg) ---
**Author:** ![teodor11](https://onehack.st/user_avatar/onehack.st/teodor11/32/158489_2.png) [@teodor11](https://onehack.st/u/teodor11)\ **Post date:** [August 2, 2026, 8:01am UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/13 "2026-08-02T08:01:20Z")
NOW WE CAN CLARIFY THINGS! This is about using LockDown Browser, the student testing console in the Respondus system. For those who don’t know, Respondus has been a pioneer in online testing for two decades. Every year, hundreds of millions of exams use LockDown Browser and Respondus Monitor to ensure academic integrity in educational institutions. Respondus technology is embedded in over 70 third-party assessment platforms, from homework systems to certification tests. It connects the teacher and the students who are being tested. At one end of the system is the teacher using Respondus Monitor and at the other end are the students using the LockDown Browser on the testing console. WHAT IS LockDown Browser? LockDown Browser® is a custom browser that locks down the testing environment within a learning management system. Used in over 2000 higher education institutions, LockDown Browser is the “gold standard” for securing online exams in classrooms or proctored environments. **It’s about using LockDown Browser, the student’s testing console in the Respondus system.** Sir, since in your answer you refer to using LockDown Browser, it means that you are a student who took an exam and it didn’t work. IT DIDN’T WORK because YOU RUN UltraViewer to have access to the teacher’s console but it blocked your browser. In order to be able to take the exam, you must stop UltraViewer. Otherwise, IF YOU ARE A TEACHER, you should have referred to Respondus Monitor. **Show the message to the examining teacher and ask him to solve the problem.** In conclusion, I was right that the question DOES NOT REFER TO A COMMON SITUATION. With much respect, teodor11 ---
**Author:** ![BlueHacker](https://onehack.st/user_avatar/onehack.st/bluehacker/32/174721_2.png) [@BlueHacker](https://onehack.st/u/BlueHacker)\ **Post date:** [August 2, 2026, 12:50pm UTC](https://onehack.st/t/help-bypass-close-other-app-first-detection-on-windows-no-vm-sandbox/324194/14 "2026-08-02T12:50:07Z")
![The block is a scan matching a name-list — see it, catch it, fix it](https://onehack.st/uploads/default/original/3X/6/2/62bc0250f58d5b81d75bc59dd1dfa5409db9452a.jpeg) For any _“App A won’t start while B is open”_ — that box is a **scan matching a name-list, not a lock.** See it → catch it → fix it, no guessing: 🔎 **SEE what it reads:** [Process Explorer](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer) (`Ctrl+F` the other app → who holds a handle) · [Strings](https://learn.microsoft.com/en-us/sysinternals/downloads/strings) `strings64 -n5 app.exe` — the blocklist is usually **plaintext inside the .exe** · [WinObj](https://learn.microsoft.com/en-us/sysinternals/downloads/winobj)+`handle.exe` (the hidden “already-running” mutex) · [System Informer](https://github.com/winsiderss/systeminformer) · [GUIPropView](https://www.nirsoft.net/utils/gui_prop_view.html) (window-class) · [OpenedFilesView](https://www.nirsoft.net/utils/opened_files_view.html) (who locks the file) · `tasklist /svc` 🎧 **CATCH the trigger:** [Procmon](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon) → filter the app, read the burst before it blocks, double-click → **Stack tab** = the exact DLL · [Sysmon](https://learn.microsoft.com/en-us/sysinternals/downloads/sysmon) **Event 10** = literally _“A opened a handle to B”_ · [Regshot](https://sourceforge.net/projects/regshot/) · [x64dbg](https://x64dbg.com/)/[WinDbg TTD](https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-overview) (step **backwards** from the block) 🔧 **FIX it clean:** disable the service ([services.msc](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sc-config)/[Autoruns](https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns)) · run each app in its own lane ([Sandboxie-Plus](https://github.com/sandboxie-plus/Sandboxie)/[Windows Sandbox](https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview)) · if **your** app is the one flagged, whitelist it → [WDSI](https://www.microsoft.com/en-us/wdsi/filesubmission) + [every AV’s FP portal](https://github.com/yaronelh/False-Positive-Center) + [code-sign it (even from Linux)](https://github.com/mtrojnar/osslsigncode) 🐧🍎 **Any OS:** [Frida](https://frida.re/docs/frida-trace/) `frida-trace -i "Process32Next*" -f app.exe` prints the **literal name it compares** · Linux [strace/ltrace](https://strace.io/) · [ProcMon-for-Linux](https://github.com/microsoft/ProcMon-for-Linux) · [lsof](https://github.com/lsof-org/lsof) · [systemctl mask](https://www.freedesktop.org/software/systemd/man/latest/systemctl.html)/[Firejail](https://github.com/netblue30/firejail)/[Flatseal](https://flathub.org/apps/com.github.tchx84.Flatseal) · macOS [fs\_usage/eslogger](https://keith.github.io/xcode-man-pages/eslogger.1.html) · [LaunchControl](https://www.soma-zone.com/LaunchControl/)