device dosn't apper in multi control

[mostafaelhalfawy]

multi control works but device dosn't appear i enabeld it in the phone and pc i have Intel® Wi-Fi 6 AX201 160MHz

[mostafaelhalfawy]

i restarted the app and auto connection setting worked and it connected and now it refuse to work again

[rinkeshpingale]

I faced the same issue on my HP Victus Ryzen 7 5800H. Do the following: Go to Apps > Installed Apps > Multicontrol > 3 dots > Advanced Options > 1st Terminate > 2nd Reset ✅> 3rd Repair ✅.

This shall fix it. Restart the PC if required.

[mostafaelhalfawy]

auto connection setting worked thanks but device dosn't apper

[rinkeshpingale]

Same thing happened with me. I stayed on that screen for a few minutes, lets say 5, and in the mean time toggeled Multi Control on and off on the phone. My device appeared there.

I have done this 3 times (I had reinstalled the Galaxy Book Enabler with different versions and Book versions), and it it worked each time.

Also toggled the Bluetooth on and off on the laptop.

[mostafaelhalfawy]

you are a legend it worked( after you changed the version it worked all the time ? ) what version you use

[rinkeshpingale]

Currently spoofed to Book 5 Pro 360. Have tried Book 5 Pro and Book 3 Ultra (Legacy) on the same (AMD Realtek) machine.

I have Book 3 Ultra currently on my other (Intel) laptop.
Surprisingly, everything worked fine on it and did not need any troubleshooting.

[rinkeshpingale]

Fix for Multi Control Connection Issues

​I validated this fix on both my existing setup and after a fresh 'nuke' reinstall. It resolved the issue consistently in both scenarios.
Current Profile: Galaxy Book 3 Ultra

​Root Cause
​The issue appears to be a race condition during system startup.
The GalaxyBookEnabler scheduled task is currently configured with a 10-second delay. However, Samsung background services (specifically Samsung Continuity Service) start immediately upon Windows boot. These services detect the non-Samsung hardware identifier before the spoofing task executes, causing the Multi Control feature to mark the device as unsupported in memory.

--

Solution for Users (Workaround)
​If you are currently experiencing this, you can fix it by removing the delay from the Windows Scheduled Task:

1. ​Press Win + R, type taskschd.msc, and press Enter.
2. ​In the left pane, select Task Scheduler Library.
3. ​​Locate and right-click the task named GalaxyBookEnabler, select Properties.
4. ​Go to the Triggers tab.
5. ​Double-click the trigger labeled At System Startup.
6. ​Uncheck the box labeled "Delay task for:" (currently set to 10 seconds).
7. ​Click OK twice to save and close.
8. ​Restart your computer.
9. ​After rebooting, the spoof runs immediately, beating the Samsung services check, and Multi Control connects instantly.

--

Recommendation for Developers
​To prevent this in future installations, I suggest removing the delay from the installation script.
​In Install-GalaxyBookEnabler.ps1, the task trigger creation currently includes a delay:

$trigger = New-ScheduledTaskTrigger -AtStartup
$trigger.Delay = "PT10S"  # <--- This causes the race condition

--

Proposed Change:
Comment out or remove the delay property to ensure the spoof applies before Samsung services initialize:

$trigger = New-ScheduledTaskTrigger -AtStartup
# $trigger.Delay = "PT10S"

@Bananz0 @mostafaelhalfawy

[Bananz0]

Nice find, that must've snuck past me as I was overhauling the install processes. Currently on holiday and have finals to prepare for so it might take some time but I will fix this soon!

[Bananz0]

I removed the delay trigger on my laptop and still run into the same problem on my laptop too. I think more research is needed into this because it usually works well for the first install but stops after a couple of days