GridinSoft Threat Intelligence

Windows.winmd file report

Under review File reputation report
MD5 4a28878717558bef85036cf92246146a
Latest seen 2026-04-25 23:01:08 (a month ago)
First seen 2020-06-05 20:05:43 (5 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2020-06-05 20:05:43 (5 years ago); latest analysis 2026-04-25 23:01:08 (a month ago).

Digital signature

Signed by DIGITAL PROTECTION SERVICES S.R.L.. 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.

Windows.winmd is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2026-04-25 23:01:08 (a month ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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.

MD5: 4a28878717558bef85036cf92246146a
Size: 1 MB
First Published: 2020-06-05 20:05:43 (5 years ago)
Latest Published: 2026-04-25 23:01:08 (a month ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-04-25 23:01:08 (a month ago)
Signed By: DIGITAL PROTECTION SERVICES S.R.L.
Status: Valid

The signature on Windows.winmd 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 Windows.winmd 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 95.4%
Windows 7 2.5%
Windows 8.1 2.0%

The most common operating system signal for Windows.winmd is Windows 10 with 95.4% 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.

Windows.winmd 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: e992a3f3-cf41-4a7f-a552-38c791565c1d

PE Sections:

Sections 1
Raw data 1436160

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

.text 1436160 bytes ยท 100.0% of section data
MD5 50ab89d595d3d7a56eefec304fcf0f44

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 4a28878717558bef85036cf92246146a.
  • 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. Use the PUP category to compare similar reports.