Trackpad on Galaxybook 2 360 not working since update yesterday

[ethos123]

My laptop seems to have downloaded a Windows update yesterday - and since then, the trackpad has not worked.  The cursor is not visible either.  Looking at Windows update, it did the following yesterday: 

KB5066835

https://support.microsoft.com/en-gb/topic/october-14-2025-kb5066835-os-builds-26200-6899-and-26100-6...

I've tried the following:

1. Restarting multiple times

2. Switching the trackpad on and off using the Fn-F5

3. Run Samsung Update

but no joy.

Could anyone please help?

[johnz237]

Does plugging in a mouse/keyboard work?

If so, log in, go to Device Manager, right-click them and uninstall them both, then restart the device (it should install generic drivers).

If it still doesn't work, go to cmd, open as administrator, search for sfc/scannow, and wait for it to be done. Restart the PC.

Worst case, boot the laptop, hold shift, and press "restart," keeping shift held until the troubleshooting screen shows up. Go to troubleshooting and try a restore point.

If not it may be best to backup and factory reset

[479]

I have to do a hard reboot to get the trackpad back online. Sometimes i had to do it 2 or 3 times. Hold the power button down until it shuts off. Just restarting didn't cut it. This has happened after EVERY SINGLE UPDATE over the past few months. I presume this is a software glitch of some sort, i don't know much about drivers. It's very frustrating.

Samsung Galaxy Book2 - windows 11

[SponkS]

Same issue here. Mouse works, trackpad works in BIOS (so not a hardware issue). Hard reset (hold power button) helped.

[boris510 · Accepted solution]

same problem here , pls try to delete the Mice and other pointing devices in the Device Manager and the recent update of the Window, reset  the laptop. It works to me so far, but need to do iit everytime after Win update

[ethos123 · Accepted solution]

@Boris  That's kind of what finally worked for me - deleting the device and then restarting.  The same issue occurred once more last month (again after an update) and the same thing fixed it again.  Thanks!