File scan report
Verdict Safe
Is Windows11
None of the 71 antivirus engines that checked it flagged this unsigned Windows context-menu utility, and its sandbox activity looks like an ordinary .NET desktop application…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This file shows no signs of malware. Obtain it from the developer's official source and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 7mo ago
Chapter 02
Why we think so
1 point against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 71 antivirus engines that checked it flagged this file, including 17 major antivirus engines that reported it clean. In the sandbox it extracted standard graphics and text-rendering libraries, which is normal for a .NET desktop app, and it showed no high-risk techniques. It is unsigned, so the publisher cannot be confirmed.
Detection coverage is strong, and no engine flagged the file. The sandbox recorded only techniques common in legitimate software. The dropped files are SkiaSharp and HarfBuzzSharp rendering libraries unpacked by the Costura embedding tool, which is typical of .NET GUI programs. No malware databases or community malware rules list the file, and about 61 different users have submitted it over roughly seven months. The missing signature lowers confidence slightly, but nothing in the evidence suggests hostile behaviour.
What We Detected
None of the 71 antivirus engines that checked it flagged this 64-bit Windows program, and 17 major antivirus engines reported it clean. It has no listing in public malware databases, no malware-specific rule matches and no packer. Its structure matches a natively compiled .NET application.
Threat Behavior
In the sandbox runs, the program unpacked bundled graphics and text-rendering libraries into a temporary folder. This is standard for .NET desktop interfaces. No high-risk techniques, persistence, injected processes or network contacts by the sample were recorded. A generic injection mapping appeared without any target process, and that pattern is common on clean software. No complete reputation check of contacted hosts is available.
What To Do Now
The file shows no signs of malware. Because it is unsigned, download it only from the developer's official project page, and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- The file is unsigned, so its author cannot be verified from a signature.
- No complete reputation check of contacted hosts is available, although no network contacts by the sample were recorded.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 71 antivirus engines that checked it flagged the file.
- 17 major antivirus engines reported it clean.
- No high-risk techniques or injected processes were observed in the sandbox.
- No matches in public malware databases or malware-specific rules.
- Steady submissions from about 61 users over seven months.
- The file has no digital signature, so its publisher cannot be verified.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 9sandbox rule tags
- 2spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
Includes 9 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Apr 24, 2026, 10:15 AM UTC
- SHA-256
462971f3f033dadff698db140d9c55bb09e1e786f0ae9b228f99e84902870efe- SHA-1
4ad91c75278a10ffd7dbdaead22785722161948a- MD5
c8c86135a9fc0907ac4da01f395720e8
About this file
Windows11ContextMenuManager.dll is a Win32 EXE file of 28.6 MB.
- Type and size
- Win32 EXE · 28.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Mar 26, 2026On VirusTotal.
- Submitted by
- 61 distinct sources
- Packer
- None detected
- Entropy
- 7.07 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (76), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Windows11ContextMenuManager.dll safe?
What is Windows11ContextMenuManager.dll?
How many antivirus engines detected Windows11ContextMenuManager.dll?
What is the SHA-256 hash of Windows11ContextMenuManager.dll?
Is it safe to run Windows11ContextMenuManager.dll?
How up to date is this analysis of Windows11ContextMenuManager.dll?
Community
Member reviews and reports for this exact file hash.
