Hi everyone,
Just a fellow CAD user here who has been incredibly frustrated by this exact same issue.
I know there's been a lot of confusion, so I wanted to share what I found after digging into the OS/hardware side of things.
I've read through the threads and saw that many of you correctly pinpointed recent Windows updates (like KB5083769 or KB5086672) as the culprit.
I also saw that some people found a weird workaround by pressing both Shift keys at the same time
Here is exactly what is happening:
In recent Windows 11 updates and some laptop power-saving firmwares, the way modifier keys (Shift, Ctrl, Alt) are handled has changed.
Normally, when you hold down a key, it sends an initial key_down signal, followed by a continuous stream of repeat key_down signals.
However, Windows is now suppressing those repeat signals for modifier keys--it only sends a single down signal and nothing else.
AutoCAD's temporary override (like holding Shift for Ortho) requires at least two consecutive down signals to register as a "held" key.
Because it only receives one signal from the OS now, the feature completely breaks.
The Solution:
Since we can't pause Windows updates forever and pressing both Shift keys is annoying, I wrote a few lightweight C++ background tools to bypass this OS limitation and fix the root cause.
I've uploaded the compiled tools and source code to my GitHub here:
https://github.com/Jione/AutoCAD-Shift-Fix
There are two main tools you can use:
1. AcadShiftFix:
This is a targeted fix. It monitors for a Shift key press only when acad.exe or acadlt.exe is the active window.
If it doesn't detect a repeat signal from Windows, it injects one automatically so AutoCAD recognizes the key is being held.
2. KeyRepeatAssist:
A universal fix that restores the classic repeat behavior for all modifier keys (L/R Shift, Ctrl, Alt) across the entire Windows OS.
There is also a KeyRepeatTester console app included if you want to verify that your system is dropping the repeat signals.
You can run these as standalone .exe files for your current session or use the installer to have them start with Windows.
I hope this saves some of you the massive headache I had trying to figure this out!