Skip to content

Recommendation

Depends

On a desktop PC, blocking is safe: there are no motion sensors, and it does not break any visible features.

On a tablet or laptop with auto-rotate and a pedometer, check that they work first.

Main effect
Blocking access to motion sensors
FPS and memory
See the research

BoosterX enables a general block for Store/UWP apps — the same global toggle as on the Windows page “Settings” → “Privacy” → “App permissions” → “Motion”. The data comes from device sensors such as the accelerometer and gyroscope. The visible consumers are features that react to tilt and steps: for example, auto-rotation of an app’s screen on a tablet or a pedometer in a fitness app. After the block, they do not receive sensor data. A desktop PC usually has no such sensors, so the block changes only the access itself — there are no visible losses.

Classic Win32 programs read sensors directly if they use them, and are not subject to the block. A per-app block remains on the same system page. Do not confuse this with the “Sensors” setting: it disables system access to sensors entirely, which is a different level. BoosterX supports the setting in Windows 10 and Windows 11.

On a device with sensors, rotate the tablet or laptop: the interface of the running app should rotate. Apply the block, restart the app and repeat the rotation. On a desktop PC there is nothing to verify the visible effect with — there are no sensors.

Open “Optimization” → “Privacy” → “App permissions” → “App access to motion data”, move the toggle to the “On” position: BoosterX will apply the block on access to motion data. Click “Apply”. If “Instant apply” is enabled, a separate button is not required. To revert, move the toggle to the “Off” position and apply the change again: BoosterX will return Windows to its default state with access to motion data allowed.

Last verified: 2026-09-19.