From 10554c1238bf5ba9f5fe2e263f46bb68f6f23496 Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Sat, 25 Jul 2026 22:34:59 -0700
Subject: [PATCH] Updated Known issues (markdown)

---
 Known-issues.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Known-issues.md b/Known-issues.md
index 8c99bc9..6077f3f 100644
--- a/Known-issues.md
+++ b/Known-issues.md
@@ -29,7 +29,6 @@
 ## Configurator (spicecfg)
  * If `spicecfg.exe` fails to launch or crashes, try running `spice.exe -cfg` or `spice64.exe -cfg`  in the command line instead of spicecfg, which launches the configurator but with logging enabled. It's not *exactly* the same environment as spicecfg, but it's close enough.
     * If you still can't figure out the problem, delete the config files (`%appdata%\spicetools.xml` and `%appdata%\spice2x`) and try again.
- * `spicecfg.exe` may fail to launch or be super slow to open while OBS is running. This is due to a bug in OBS that locks the Windows HID APIs. Try turning off OBS temporarily.
  * `spicecfg.exe` may fail to launch when run from a network share (UNC path).
 
 ## Input