GridinSoft Threat Intelligence

WindowsFormsIntegration.dll file report

Under review File reputation report
MD5 f6b19e8c0387992c46535dea9bd049f3
Latest seen 2026-04-28 23:01:39 (a month ago)
First seen 2026-02-02 23:01:32 (3 months ago)
Size 190 KB
Signed by .NET

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-02 23:01:32 (3 months ago); latest analysis 2026-04-28 23:01:39 (a month ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: WindowsFormsIntegration.

Digital signature

Signed by .NET. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

WindowsFormsIntegration.dll is a Windows file recorded in the ThreatInfo database. It is associated with WindowsFormsIntegration. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2026-04-28 23:01:39 (a month ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: WindowsFormsIntegration
Company Name: Microsoft Corporation
MD5: f6b19e8c0387992c46535dea9bd049f3
Size: 190 KB
First Published: 2026-02-02 23:01:32 (3 months ago)
Latest Published: 2026-04-28 23:01:39 (a month ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-04-28 23:01:39 (a month ago)
Signed By: .NET
Status: Valid

The signature on WindowsFormsIntegration.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%

ThreatInfo has observed WindowsFormsIntegration.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 WindowsFormsIntegration.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.

WindowsFormsIntegration.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
Image base

.NET Info:

MVID: 7eddd5a4-d52b-4dcf-9007-a8b9da773825

PE Sections:

Sections 3
Raw data 180224

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

.text 155648 bytes · 86.4% of section data
MD5 233c8e9e3940417bef31ed5853b70a74
.data 16384 bytes · 9.1% of section data
MD5 4d6d90d120107ff83d5d5a18e5276285
.reloc 8192 bytes · 4.5% of section data
MD5 d672bb9a4e53c63ca68c7e4a81f5f5c8

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 f6b19e8c0387992c46535dea9bd049f3.
  • 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.