Annoying snapping of the scroll slider

Hi!
When I’m working in a window of a random application and I want to scroll up/down or left/right in this window, the scroll slider snaps to the starting position when I move the mouse pointer beyond a certain distance of the slider.
See this example.
Why is that? It’s quite annoying. In macOS I can move the mouse pointer wherever I want on the screen without this snapping of the scroll bar.

Question: is it possible in Windows 10 to disable this (for me) pointless feature?

Greetz,
sgrhill.

This behavior has bothered me too but I am not aware of any way to change it. It goes back to at least NT4 released in 1996. I suspect this was designed to provide a way to back out of a scroll operation. Some other Windows controls provide for this as well. There may be a way to change the distance required but I don't know what it might be.

I know it is possible in Windows 10 to drag the scroll bar without this snapping, because the scroll bar of a random Windows Settings window proves this. For example: Press Win + I and choose Apps. No problem here.
I cannot find in Windows Settings an option to 'unsnap' the scroll bar. Maybe my request must be altered in the Registry.

ThnX!
I've walked your steps, but unfortunately no luck either. On 'Performance' with all the features unchecked and after sign-in, the backsnapping of the scroll bar is still visible.

This option is already unticked.

I'm not the only one with this annoyance.
1
2
3
4
5

These examples show that this issue is quite old.
You see in the 5th example that Windows draws an invisible square around the scroll bar area. This area contains a fixed amount of pixels. When the mouse pointer leaves this area the back snapping occurs.
I've worked many years on a 22" screen with 1680 x 1050 pixels. Now I use a 27" QHD monitor containing 2560 x 1440 pixels. Since the pixels on the new monitor are smaller, the 'safe area' around the scroll bar is also smaller. I noticed that the back snapping occurs far more often than on the 22" screen.

ThnX for your input!

I've also posted this issue on the Microsoft forum. I'll keep you posted.