MicrosoftEdge / MicrosoftEdge/WebView2Feedback

EmbeddedBrowserWebView.dll.pdb not found on symbol server

Open
#4,919 1 comment 2 reactions 1 assignee View on GitHub

@ambikakunnath is already working on this.

Since Nov 20, 2024.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Windbg shows the following:
C:\ProgramData\dbg\sym*https://msdl.microsoft.com/download/symbols
EmbeddedBrowserWebView.dll.pdb
17BC6ED4F11086ED4C4C44205044422E1
SYMSRV: UNC: C:\ProgramData\dbg\sym\EmbeddedBrowserWebView.dll.pdb\17BC6ED4F11086ED4C4C44205044422E1\EmbeddedBrowserWebView.dll.pdb - path not found
SYMSRV: UNC: C:\ProgramData\dbg\sym\EmbeddedBrowserWebView.dll.pdb\17BC6ED4F11086ED4C4C44205044422E1\EmbeddedBrowserWebView.dll.pd_ - path not found
SYMSRV: UNC: C:\ProgramData\dbg\sym\EmbeddedBrowserWebView.dll.pdb\17BC6ED4F11086ED4C4C44205044422E1\file.ptr - path not found
SYMSRV: HTTPGET: /download/symbols/EmbeddedBrowserWebView.dll.pdb/17BC6ED4F11086ED4C4C44205044422E1/EmbeddedBrowserWebView.dll.pdb
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: HTTPGET: /download/symbols/EmbeddedBrowserWebView.dll.pdb/17BC6ED4F11086ED4C4C44205044422E1/EmbeddedBrowserWebView.dll.pd_
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: HTTPGET: /download/symbols/EmbeddedBrowserWebView.dll.pdb/17BC6ED4F11086ED4C4C44205044422E1/file.ptr
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: RESULT: 0x80190194

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

130.0.2849.80

SDK Version

No response

Framework

Other

Operating System

Windows 10

OS Version

No response

Repro steps

See what happend.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.