Description

My Wails application displays a blank window with the error ERR | WebVie2wProcess failed with kind 1 in the terminal. This issue started suddenly after some modifications, but even after reverting to previous working code states and creating fresh demo projects, the problem persists.

To Reproduce

1. Create a new Wails project: wails init -n demo
2. Build the project: wails build
3. Run in development mode: wails dev
4. The application window opens but displays blank/white content
5. Terminal shows repeated ERR | WebVie2wProcess failed with kind 1 errors

Expected behaviour

The application window should display the frontend content properly without errors.

Screenshots

• Blank/white application window
• Terminal shows ERR | WebVie2wProcess failed with kind 1 errors repeatedly
• Frontend DevServer is accessible via browser at http://localhost:34115 with some errors but functional content
• Both new and legacy WebView2 loaders exhibit the same issue

Attempted Fixes

1. Reverted code to previous working states - problem persists
2. Created fresh demo projects - same issue occurs
3. Updated WebView2 runtime - no improvement
4. Modified registry settings based on MSDN documentation - no solution found
5. Tried legacy WebView2 loader (-tags native_webview2loader) - same error occurs
6. Verified WebView2 installation through wails doctor - shows installed and up-to-date
7. Browser testing - accessing the dev server directly in Edge/Firefox shows content but with different errors:

   ERR | process message error: runtime:ready -> Unknown message from front end: runtime:ready
   ERR | Unknown message from front end: runtime:ready
   

System Details

Wails Doctor

# Wails
Version | v2.10.2

# System
┌───────────────────────────────────────────────────────────────────────────────────────┐
| OS           | Windows 10 Enterprise LTSC 2019                                        |
| Version      | 1809 (Build: 17763)                                                    |
| ID           |                                                                        |
| Branding     | Windows 10 企业版 LTSC                                                 |
| Go Version   | go1.25.0                                                               |
| Platform     | windows                                                                |
| Architecture | amd64                                                                  |
| CPU          | Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz                               |
| GPU          | Intel(R) UHD Graphics 630 (Intel Corporation) - Driver: 27.20.100.9316 |
| Memory       | 16GB                                                                   |
└───────────────────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────┐
| Dependency | Package Name | Status    | Version       |
| WebView2   | N/A          | Installed | 142.0.3595.65 |
| Nodejs     | N/A          | Installed | 22.18.0       |
| npm        | N/A          | Installed | 8.0.0         |
| *upx       | N/A          | Available |               |
| *nsis      | N/A          | Available |               |
|                                                       |
└─────────────── * - Optional Dependency ───────────────┘

Additional context

• The issue started suddenly after working fine for days
• Both production builds (wails build) and development mode (wails dev) exhibit the same problem
• The frontend framework being used is Svelte, but the issue also occurs with vanilla templates
• The dev server URLs are accessible via browser, suggesting the issue might be related to WebView2 communication rather than frontend compilation
• Error occurs with both the new Go WebView2Loader and the legacy native loader