Quicken Classic blank UI on Windows 11 24H2 — root cause summary

Quicken launches with a blank shell — only File/Help menu visible

“Quicken Classic Business & Personal installs, but the UI does not render at all. I only get a blank window with File and Help. No accounts, no menu, no dashboard — nothing.”

The %localappdata%\Quicken folder never gets created

“During install, Quicken never creates the Local AppData engine folder. %localappdata%\Quicken remains completely empty — no Awesomium, no WebCache, no BrowserEngine, nothing.”

I am running Windows 11 build 26200 / 24H2 — IE/Trident/MSHTML is removed

“I am on Windows 11 build 26200 (24H2). Microsoft removed IE11, the Trident engine, and MSHTML WebView. Quicken’s installer still depends on those components to initialize Awesomium. They no longer exist in this build.”

Quicken cannot initialize its embedded browser engine (Awesomium) on 24H2

“The Awesomium WebCore engine fails silently during installation because the HTML engine it depends on has been removed from Windows. Since Awesomium never initializes, Quicken cannot build its UI.”

This is NOT a data file issue, NOT a user profile issue, NOT a permissions issue

“This is not a corrupted data file, not a user permissions issue, not antivirus, not Controlled Folder Access, and not a bad install. This is a Windows-compatibility issue with Quicken’s embedded browser engine.”

Quicken’s desktop installer is currently incompatible with Windows 11 24H2 builds

Your installer still relies on legacy IE-based components that have been fully removed in 24H2. The installer needs to be updated to use WebView2 instead of Awesomium/MSHTML.

💥 “Is Quicken Classic currently supported on Windows 11 24H2 preview builds?”

💥 “If not, when will a compatible installer be released?”

💥 ““Do you have a WebView2-based installer or a Microsoft Store deployment for Quicken Classic Business & Personal that bypasses the removed IE engine?”

• Quicken installs, but the main application window is blank except for File/Help.

• %localappdata%\Quicken never populates — Awesomium/WebCache/BrowserEngine are never created.

• On Windows 11 build 26200 (24H2), Microsoft removed IE, MSHTML, Trident, and the legacy WebBrowser control.

• Quicken’s installer still relies on these components to initialize its embedded WebView engine (Awesomium 1.6.x).

• Since the dependent HTML engine is gone, Awesomium fails silently during installation.

• With no UI engine initialized, Quicken cannot render its interface.

• This is not a file problem, not a reinstall issue, not permissions, not a corrupted Windows profile — it is a compatibility issue between Quicken’s legacy engine and Windows 24H2.

• Quicken must update the installer to use WebView2 or provide a compatible build.

• Request escalation to engineering — Level 2/Level 3 support — because this is not fixable by normal reinstall procedures.