Raised at Dart-Code/Dart-Code#1735
If Chrome isn't in the location that webdev checks it produces a bad error like:
Registering build targets...
Starting initial build...
Serving DevTools at http://127.0.0.1:6368
Starting resource servers...
Serving `web` on http://localhost:6361
CreateProcessW failed 2
It's possible for the user to set CHROME_EXECUTABLE but that's not obvious from the failure. I think instead the code should print a nicer message about not being able to locate Chrome and how the user can fix it.
(it's possible if you're migrating to browser_launcher then it may need some tweaks there too).