Fix Chrome on Windows 7 RC / Beta

Back when Windows 7 was in RC/Beta, Chrome had an ugly crash on it — pages with plugins would take the whole browser down. The community workaround at the time was to launch Chrome with the --in-process-plugins flag. If you’re digging through old bookmarks for this: that era is long over, and the flag is gone. Here’s the original fix for the record, and what the actual modern equivalents are.

The 2009 workaround, for the record

Right-click your Chrome shortcut and open Properties. On the Shortcut tab, find the Target field, which ends with chrome.exe, and append the flag after it:

C:\Users\user\AppData\Local\Google\Chrome\Application\chrome.exe --in-process-plugins

That forced plugins to run inside the browser process instead of a separate one, which happened to dodge the Win7-beta crash. It was a workaround, not a fix — and it traded stability for isolation, since one misbehaving plugin could now take down everything.

Why it’s obsolete

Two things killed this trick permanently:

• Chrome dropped NPAPI plugins entirely (2015). There are no plugins left to isolate — no Flash, no Java applets, no Silverlight. The whole plugin-process architecture this flag tinkered with has been dismantled; the switch itself no longer exists in Chromium’s source.
• Whatever Win7-beta bug it papered over was fixed in the shipping release. Nobody has needed it since Chrome went stable on Windows 7 in early 2010.

Also, for completeness: Windows 7 itself reached end of support in January 2020. If you’re still on it, no Chrome version is receiving security updates on that OS — the right fix is upgrading the OS, not tweaking flags.

If a site still needs a plugin-era technology

The legitimately current equivalents:

• Flash content: the Ruffle emulator (browser extension or self-hosted), which runs SWF files safely in WebAssembly.
• Old Java applets / ActiveX line-of-business apps: Microsoft Edge’s IE mode, for the intranet apps that genuinely can’t be rebuilt.
• Anything else: modern web standards — WebAssembly, WebGL, WebRTC — cover what NPAPI plugins used to do, natively.