Krita 5.3.2.1 Released: Fixes Layer Docker Bugs and Windows Signing Issues
The latest Krita 5.3.2.1 update drops a critical patch for the layer docker that was causing sync failures, random crashes, and stubborn group behavior. Users who stuck with version 5.3.0 or jumped straight to 5.3.2 will finally get a stable canvas without fighting broken layer management. This release also patches unsigned Windows binaries so security software stops flagging the installer as suspicious.
Why Krita 5.3.2.1 Fixes the Layer Docker Bug
The layer docker bug in version 5.3.2 was not a minor glitch. It quietly desynced layers from their parent groups, which meant brush strokes would paint on invisible canvases or crash the entire application mid-stroke. Artists frequently lose hours of work because the interface shows one thing while the rendering engine does another. The patch restores proper communication between the docker panel and the underlying layer stack, so grouping, visibility toggles, and opacity adjustments behave exactly as expected. Anyone who relies on complex compositions or frequent layer merging should update immediately before starting a new project. Trying to manually rebuild affected files after a crash is pointless and usually corrupts the brush history anyway, making a clean install of this patch the only reliable fix.
Windows Package Signing and Installation Notes
Previous Windows builds shipped without proper code signatures, which means Defender and third party security suites treated the installer like malware. The updated package now carries a valid signature from the Krita development team, so users can run the standard installer without disabling real time protection or digging through quarantine logs. The update installs over existing versions without wiping custom brush packs or workspace layouts, but backing up the appdata folder remains a sensible habit before any major patch. Keeping a copy of the configuration directory prevents hours of frustration when the updater decides to reset default keybindings or delete custom color palettes during the transition.
Should You Skip the Qt6 Branch?
The announcement explicitly marks version 6.0.2.1 as experimental due to the heavy migration from Qt5 to Qt6. While newer toolkits often bring smoother rendering and better HiDPI scaling, they also introduce unpredictable behavior in plugin ecosystems and older hardware drivers. Most studios and freelance illustrators will find Krita 5.3.2.1 far more reliable for daily deadlines until the Qt6 branch matures past its current testing phase. Switching to the newer build only makes sense if you actively test third party plugins or need specific Qt6 performance gains that outweigh the risk of unexpected crashes. The experimental branch still struggles with legacy scripters, and forcing it on a production machine just invites unnecessary downtime.
Grab the installer from the official site when ready, and keep the old version handy until the new one proves stable on your hardware. Happy painting.
