Is windowsdesktop-runtime-10.0.12-win-x64.exe safe?
No engine detected malware, the verified .NET signature and broad prevalence support legitimacy, and the installer-style runtime activity produced no malicious sandbox finding.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, and the executable carries a verified .NET signature. Its broad distribution, two matching signer precedents, unpacked structure, and installer-style execution outweigh the low-severity direct-IP signal, though that IP lacks a completed reputation check.
55a67d8476cde95a9c…21d4908174ae84Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, and the executable carries a verified .NET signature. Its broad distribution, two matching signer precedents, unpacked structure, and installer-style execution outweigh the low-severity direct-IP signal, though that IP lacks a completed reputation check.
The sample received no malicious or suspicious detection from 75 engines, with all 17 participating tier-1 engines reporting no detection. Its signature verifies under .NET, and two prior files matched by signer were also assessed as clean commodity software. Broad prevalence across 1,935 sources and 2,087 submissions further supports an established runtime installer rather than an isolated payload. One sandbox observed WiX installer processes and returned no malicious finding, while no inspected child was identified as malicious. Three offensive-use techniques and one direct-IP contact are counter-signals, but the IP was not reputation-checked and those observations lack independent malware corroboration.
What We Detected
No malicious or suspicious result appeared among 75 antivirus engines, and all 17 participating tier-1 engines reported no detection. The executable has a verified signature from .NET, is not packed, and has no high-entropy code indicator. It is also broadly distributed, with 1,935 sources accounting for 2,087 submissions, while two previous verified files matched by signer received clean assessments.
Threat Behavior
One completed sandbox run launched WiX Burn installer components and produced no malicious sandbox finding. It recorded T1134, T1543.003, and T1547.001, but these techniques can overlap with privileged installation, service creation, and startup configuration. A low-severity heuristic also noted direct communication with 162.159.36.2. No complete host-reputation check is available for that address, so the no complete contacted-host reputation result was available.
What To Do Now
Use a copy obtained directly from Microsoft's official .NET download channel and verify that its digital signature remains valid before installation. Keep endpoint protection enabled, especially if the file came from an unofficial mirror, email attachment, or download bundle.
Where this verdict could be wrong4 caveats
- behaviour.offensiveTechniques includes T1134, T1543.003, and T1547.001, although these appeared alongside installer activity and no malicious sandbox verdict.
- MalwareTips.Synth.DirectIpC2 fired at low severity for 162.159.36.2, but contactedHosts=null means the IP-reputation cross-check is unavailable.
- droppedChildren inspected 10 files, but all 10 have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false.
- signing.signerStats.totalSamples=2 provides only a small historical sample and does not meet auto-trust thresholds.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported malicious or suspicious results.
- 17 tier-1 engines reported no detection.
- The .NET digital signature is verified.
- The file appeared across 1,935 sources and 2,087 submissions.
- Two signer-matched historical samples received safe verdicts.
- Runtime observation included T1134, T1543.003, and T1547.001.
- A low-severity direct-IP heuristic fired for 162.159.36.2.
- No complete reputation result is available for the observed IP contact.
- All 10 inspected dropped children lack individual verdicts.
Prefer the official Microsoft .NET download channel and confirm the .NET signature before running this installer. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 23MITRE ATT&CK techniques
- 6spawned processes
- 1network contacts
- 16filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
- C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\2052\thm.wxl
- C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\1028\thm.wxl
- C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\1029\thm.wxl
- C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\1031\thm.wxl
- C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\3082\thm.wxl
- Global\WindowsUpdateTracingMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 09c51c910f7142ab7f73…c689d3Never scannednever seen before
- cd2e8ed1fbb308d9d166…19e01bNever scannednever seen before
- 43e1e134d0591532323d…c47aadNever scannednever seen before
- ecdd5f7b7ed65bef8e3e…10efdeNever scannednever seen before
- 2f174b5eed2a84e43396…363534Never scannednever seen before
- 0da13bd67e88529919a3…c25111Never scannednever seen before
- 75cf03762aea3f3ef6ae…1e0751Never scannednever seen before
- c536f3f85936f6b38782…12b184Never scannednever seen before
- dfee8e2d075087227f19…a521beNever scannednever seen before
- 61a2cbd12868cb9b359e…961a18Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 1,935sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from .NET.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 2,087 times from 1,935 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: windowsdesktop-runtime-10.0.12-win-x64.exe — 55a67d8476cde95a9cc43a95803b4f54446e7c9251ed22aa6421d4908174ae84
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\windowsdesktop-runtime-10.0.12-win-x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\wixstdba.exe" -burn.ba.apiver 569705357157400576 -burn.ba.pipe BurnPipe.{2E20D4B6-A94A-41E0-B22E-D9AD72DF10D3} {AE6B0EAE-1439-431E-811E-438B50783A1D}
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: thm.wxl — C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\2052\thm.wxl
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: thm.wxl — C:\Users\<USER>\AppData\Local\Temp\{1F63AABF-AD47-4C72-8301-EC9A4AFB873A}\.ba\1028\thm.wxl
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- windowsdesktop-runtime-10.0.12-win-x64.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: .NET
- Size
- 57.3 MB
- Last analyzed
- Sep 24, 2026, 11:05 PM UTC
55a67d8476cde95a9cc43a95803b4f54446e7c9251ed22aa6421d4908174ae84Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is windowsdesktop-runtime-10.0.12-win-x64.exe safe?
What is windowsdesktop-runtime-10.0.12-win-x64.exe?
How many antivirus engines detected windowsdesktop-runtime-10.0.12-win-x64.exe?
Is windowsdesktop-runtime-10.0.12-win-x64.exe digitally signed?
What is the SHA-256 hash of windowsdesktop-runtime-10.0.12-win-x64.exe?
Is it safe to run windowsdesktop-runtime-10.0.12-win-x64.exe?
How up to date is this analysis of windowsdesktop-runtime-10.0.12-win-x64.exe?
Community
Member reviews and reports for this exact file hash.