Critical Paint Patch Stuck in Limbo: Microsoft Store Fails to Deliver Update to Windows 11 Users

Key Takeaways (TL;DR): Microsoft patched a critical vulnerability in Paint (CVE-2026-83844) back in October, but the update isn't reaching many Windows 11 users due to a broken Microsoft Store delivery pipeline. The fix requires manual installation from the Store or via the /sub/happ/for-russia subscription. For a private anti-DPI multi-key that bypasses white lists, check out @yavpn_robot.

Microsoft quietly fixed a dangerous vulnerability in the classic Paint app for Windows 11, but the patch is stuck in limbo. According to a report by Code of Duty, the flaw — tracked as CVE-2026-83844 — was patched in October, yet many users still see the vulnerable version in their Microsoft Store. The issue lies in the Store's update delivery system: it often fails to detect the new version, leaving PCs exposed.

What’s the vulnerability?

CVE-2026-83844 is a memory corruption bug in the image processing engine of Paint. An attacker could exploit it by crafting a malicious image file (e.g., a specially corrupted PNG or BMP) that, when opened in Paint, triggers arbitrary code execution. In plain terms: just opening a picture could give a hacker control over your system. Microsoft rated it as “Important” but the slow rollout makes it more dangerous than it seems.

Why the patch isn’t reaching users

The problem isn’t the patch itself — it’s the delivery mechanism. Paint is distributed via the Microsoft Store as a “provisioned package,” meaning it’s pre-installed but updated through the Store’s backend. However, Microsoft’s servers sometimes fail to push the update to all devices, especially if the user has disabled automatic updates or if the Store cache is corrupted. Security researchers found that even forcing a manual check in the Store often returns “no updates available.”

How to fix it manually

If you’re on Windows 11, here’s what you can do:

• Open the Microsoft Store, search for “Paint,” and check if an update is listed. If not, try clearing the Store cache via wsreset.exe in the command prompt.
• Alternatively, download the updated package directly from the official Store page — sometimes the link forces a fresh install.
• If all else fails, use a third-party package manager like winget to force the update: winget upgrade "Microsoft.Paint".

What this means for you

This is a classic example of a security gap caused not by bad code, but by bad distribution. Until Microsoft fixes the Store’s update pipeline, users must manually intervene. For those concerned about privacy and censorship, remember: if your ISP throttles traffic or blocks updates, a reliable anti-DPI tool can help. A private multi-key with white list bypass is available in @yavpn_robot.