From e7fccfa06a966b8323037e4be2211b320463fab6 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sat, 21 Jun 2025 21:16:27 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/FAQ.md b/FAQ.md
index 76bb12c..2665fea 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -369,10 +369,6 @@ The controlled side works fine with UDP `21116` port, but it can not connect to
 
 ![image](https://github.com/user-attachments/assets/db2be786-89e3-4a2a-9702-d511fa453feb)
 
-# CTRL-ALT-DEL does not work
-- Make sure you install RustDesk on Windows, a system service is required for this so you have to install
-- Check if `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\SoftwareSASGeneration`registry have correct value, 1 or 3. https://knowledge.broadcom.com/external/article/21517/ctrlaltdel-does-not-work-on-remote-contr.html
-
 # Deploy RustDesk server in intranet.
 
 First you should set relay server with public ip (you need to fix NAT hairping problem to use public ip in intranet first) explicitly on "settings" -> "relay" of web console. Or you can set relay server (public ip) explcitly on controlled side (remote side, the device you want to control).
@@ -418,6 +414,11 @@ NAT Reflection Mode: https://www.reddit.com/r/PFSENSE/comments/fp9h1f/can_someon
 
 > Also make sure your relay server has correct key, https://github.com/rustdesk/rustdesk/issues/7358
 
+# CTRL-ALT-DEL does not work
+
+- Make sure you install RustDesk on Windows, a system service is required for this so you have to install
+- Check if `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\SoftwareSASGeneration`registry have correct value, 1 or 3. https://knowledge.broadcom.com/external/article/21517/ctrlaltdel-does-not-work-on-remote-contr.html
+
 # Unable to display image despite screen sharing being enabled on Android
 We encountered this issue when there are multiple RustDesk clients operating on Android, one being the public release and the other a custom client. If you initiate the service of one client and subsequently start the service of the other, you will not be able to retrieve an image. To rectify this, you must forcibly close the first client (making sure it's not running in the background) and then restart the other one. If the issue persists, please reboot your Android device.