When a window manager opens normally but cannot move another app’s windows, start with the access it needs. Seeing a settings window does not prove that macOS has authorized it to control other apps.
The checks below keep the test small and reversible. Save your work, choose two ordinary windows, and change one thing at a time. This is more informative than reinstalling several utilities or resetting permissions for the whole system.
Quick answer
Check System Settings → Privacy & Security → Accessibility, verify you enabled the app you actually launched, and test one ordinary window through the app’s interface. Then investigate running state, shortcuts, and individual app behavior separately.
Understand the permission you are granting
Accessibility access lets an authorized app use macOS accessibility features to interact with other apps. Apple requires you to grant that access explicitly and recommends reviewing an app’s terms and privacy policy before trusting it. It is a meaningful permission, not just a checkbox to dismiss.
For a window manager, the practical need is to interact with windows it does not own. Glidro’s own control interface can open even when that interaction is unavailable. Its setup guidance makes the permission and engine state visible, so use that guidance before trying unrelated changes.
Accessibility is different from Screen Recording. Glidro’s documented scope does not include screen recording or a live screenshot overview. Do not assume a window-moving failure means you should grant every privacy permission you can find.
Check the exact app in System Settings
Open System Settings → Privacy & Security → Accessibility. Find Glidro, or the app named by the setup prompt, and inspect its permission. If the intended app is absent, Apple documents using the add button to select it. Choose the installed copy you mean to run.
A frequent source of confusion during troubleshooting is having more than one copy of an app: one in Applications, one in Downloads, and perhaps an older build elsewhere. Quit duplicates and launch the intended copy before deciding the permission is broken. Follow any engine access step the app’s onboarding explicitly presents.
Return to the app and use its own permission check or setup indicator if provided. If it asks to relaunch after a change, do so after saving work. Avoid broad permission-reset commands as your first experiment.
Separate permission from the running state
Confirm that window management is running rather than paused. A permission can be correct while the engine is intentionally stopped. In Glidro, the menu bar and setup controls are the right place to inspect that state; closing the control window is not the same thing as requesting a pause.
Now test an ordinary resizable document window. Use a command through the interface where possible, rather than relying exclusively on a shortcut. If the interface action works, authorization and window interaction are at least functioning for that test. Your next suspect is the input binding.
If no window action works, note the exact message shown in Help or setup. A clear state description is more useful for support than a report that the app “does nothing.”
Test shortcut ownership separately
Pause other window utilities and temporarily avoid launcher or remapper bindings that use the same keys. Run the same Glidro action again. If the menu command works but the keys do not, inspect Controls and macOS Keyboard Shortcuts for an overlap.
Test in more than one app. A terminal, editor, and browser may treat the same key combination differently. Also check whether the command is being invoked while a text field or special panel is active. Do not change several unrelated shortcuts after one failed attempt.
Record which action you wanted, which binding you pressed, and which app was foreground. Those three details narrow the problem much more than “keyboard shortcuts are broken.”
Distinguish an app-specific limit from a general failure
If normal document windows move but one particular window does not, the issue may be specific to that app or window type. Full-screen windows, dialogs, and windows with strict minimum dimensions should not be treated like ordinary desktop documents. Return to a normal resizable window for comparison.
Try a modest resize rather than a tiny target. If the app refuses a narrow width, preserve a usable size or consider floating that app when appropriate. Glidro exposes app inclusion and exclusion controls; use exceptions deliberately rather than making the whole layout less useful.
If the problem remains, collect the app version, macOS version, engine details available through Help, affected app, and a short reproduction sequence. Send only the information needed to explain the behavior. That gives support a concrete case without requiring a system-wide reset.
Common questions
Should I enable Screen Recording to fix window movement?
Do not assume that is required. Check the app’s documented permissions. Glidro’s documented scope does not include screen recording or a live screenshot overview.
Why can settings open when windows will not move?
An app can display its own interface without being authorized to control other apps. Also check that its window engine is running and the test window is manageable.
