tauri: [bug] Tauri App not running on Windows 11

Describe the bug

When creating a new tauri app, running npx tauri dev builds and opens a window, but does not show anything and displays an error in the console. The error can be found in the Stack Trace section of this report.

Reproduction

  1. On Windows 11, create a new tauri project however one wishes
  2. run npx tauri dev or with the rust cli
  3. wait for the window to open and watch the ensuing blank screen and errors

Expected behavior

I expect tauri to open the window as normal with no errors and display the web app’s contents.

Platform and versions

Environment
  › OS: Windows 10.0.22000 X64
  › Webview2: 101.0.1210.53
  › MSVC: 
      - Visual Studio Build Tools 2022
  › Node.js: 17.7.1
  › npm: 8.5.2
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-pc-windows-msvc 

Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.11
  › @tauri-apps/api [NPM]: Not installed!
  › tauri [RUST]: 1.0.0-rc.11,
  › tauri-build [RUST]: 1.0.0-rc.9,
  › tao [RUST]: 0.8.5,
  › wry [RUST]: 0.16.2,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../build
  › devPath: http://localhost:3000/
  › framework: Svelte

App directory structure
  ├─ .svelte-kit
  ├─ node_modules
  ├─ src
  ├─ src-tauri
  ├─ static
  └─ tests

Stack trace

Compiling app v0.1.0 (C:\Dev\Commercial\manteados-grecia\sistema-procesos\src-tauri)
    Finished dev [unoptimized + debuginfo] target(s) in 4.52s
     Running `target\debug\app.exe`
[0524/105510.088:ERROR:validation_errors.cc(106)] Invalid message: VALIDATION_ERROR_UNEXPECTED_NULL_POINTER ([0524/105510.088:ERROR:interface_endpoint_client.cc(665)] Message 1283517667 rejected by interface embedded_browser.mojom.EmbeddedBrowser


### Additional context

I came across this error when I was teaching a friend how to use Tauri. They were on Windows 10, and did not have any issues. I, however did, as stated above.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 20 (5 by maintainers)

Most upvoted comments

@altunenes would recommend running “procmon” it will show you some helpful log messages.