GridinSoft Threat Intelligence

Microsoft.Web.WebView2.Core.dll file report

Clean record File reputation report
MD5 28c6a96591a4890d33deaa7dbabebf10
Latest seen 2024-11-27 23:01:36 (a year ago)
First seen 2024-11-27 23:01:33 (a year ago)
Size 488 KB
Publisher Microsoft

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-11-27 23:01:33 (a year ago); latest analysis 2024-11-27 23:01:36 (a year ago).

Publisher context

Company metadata: Microsoft. Product metadata: WebView2 .NET Interop Wrapper.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

Microsoft.Web.WebView2.Core.dll is a Windows file recorded in the ThreatInfo database. It is associated with WebView2 .NET Interop Wrapper. The reported company name is Microsoft. The current detection status is Clean, based on the latest analysis from 2024-11-27 23:01:36 (a year ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: WebView2 .NET Interop Wrapper
Company Name: Microsoft
MD5: 28c6a96591a4890d33deaa7dbabebf10
Size: 488 KB
First Published: 2024-11-27 23:01:33 (a year ago)
Latest Published: 2024-11-27 23:01:36 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-11-27 23:01:36 (a year ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%localappdata%

ThreatInfo has observed Microsoft.Web.WebView2.Core.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for Microsoft.Web.WebView2.Core.dll is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

Microsoft.Web.WebView2.Core.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x0007930e
Image base 0x10000000

PE Sections:

Sections 3
Raw data 489984

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 488448 bytes · 99.7% of section data
MD5 f40380c536860b47cb9503f835a8a667
.rsrc 1024 bytes · 0.2% of section data
MD5 86880277bf991dcc5462410afecdbe10
.reloc 512 bytes · 0.1% of section data
MD5 9718983028eec4ec70954e5b1b08f82e

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 28c6a96591a4890d33deaa7dbabebf10.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.