Is windowsdesktop-runtime-6.0.36-win-x64.exe safe?
No engines detected malware, and the verified .NET signature, extensive prevalence, uneventful sandbox verdict, and benign child-file rollup strongly support legitimate runtime software.
None of 74 antivirus engines flagged this executable, including all 17 tier-1 engines, and its .NET signature verifies correctly. Although broad YARA rules and several dual-use techniques appeared, they lack support from engine detections, a malicious sandbox verdict, or a malicious dropped child.
0d20debb26fc8b2bc8…b871127b798941Recommended 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.
None of 74 antivirus engines flagged this executable, including all 17 tier-1 engines, and its .NET signature verifies correctly. Although broad YARA rules and several dual-use techniques appeared, they lack support from engine detections, a malicious sandbox verdict, or a malicious dropped child.
The strongest evidence is the absence of detections across 74 engines, with all 17 tier-1 products reporting no malware finding. The executable carries a verified .NET signature and has no detected brand conflict. It is also widely established, with 3,701 sources and 70,498 submissions, rather than being newly observed or rare. One sandbox recorded mostly installer-common activity and issued no malicious verdict, while none of 10 inspected children was identified as malicious. Six YARA rules and direct-IP traffic warrant acknowledgment, but the listed rules are broad and the host-reputation check was not completed, leaving these signals uncorroborated.
What We Detected
None of 74 antivirus engines flagged the executable, and all 17 tier-1 engines reported no detection. The file has a verified signature under the signer “.NET,” no detected brand mismatch, and substantial prevalence: 3,701 sources and 70,498 submissions.
Threat Behavior
One completed sandbox run recorded 28 installer-common techniques and three offensive-capable techniques: T1134, T1543.003, and T1547.001. The sandbox produced no malicious verdict or persistence indicators, and none of 10 inspected child files was identified as malicious. Six community YARA rules matched, but several are generic metadata or implementation checks, and the anti-ransomware rule itself notes potential false positives. Direct-IP traffic was observed, but no complete contacted-host reputation result is available.
What To Do Now
Use the executable only if its hash and origin match the expected .NET Desktop Runtime distribution. Keep endpoint protection enabled and obtain a fresh copy from the official Microsoft download channel if the source is uncertain.
Where this verdict could be wrong3 caveats
- externalIntel.yaraify.ruleCount=6, including 'DebuggerCheck__API' and 'RansomPyShield_Antiransomware'; however, no antivirus engine supplied a corresponding malware detection.
- behaviour.offensiveTechniques contains T1134, T1543.003, and T1547.001, although the sandbox issued no malicious verdict and recorded no persistence indicators.
- MalwareTips.Synth.DirectIpC2 fired after direct-IP contacts, but contactedHosts=null means no complete reputation cross-check is available.
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/74 antivirus engines detected malware
- All 17 tier-1 engines reported no detection
- Verified '.NET' signature with no brand mismatch
- 3,701 sources and 70,498 submissions indicate broad prevalence
- No malicious sandbox verdict and no malicious child among 10 inspected
- externalIntel.yaraify.ruleCount=6
- Offensive-capable techniques T1134, T1543.003, and T1547.001 were observed
- Direct-IP traffic was observed without a complete host-reputation cross-check
If the file came from Microsoft’s official download channel and the SHA-256 matches the expected release, it can be used normally. Otherwise, replace it with a freshly downloaded official copy while keeping endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete6 signature or behavior rules 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
- 31MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 39filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
windowsdesktop-runtime-6.0.36-win-x64.exe
0d20debb26fc8b2bc84f25fbd9d4596a6364af8517ebf012e8b871127b798941
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\Temp\{93E1532F-40C2-47E7-885B-26541DA7BE54}\.cr\file.exe" -burn.clean.room="C:\Users\<USER>\Desktop\file.exe" -burn.filehandle.attached=788 -burn.filehandle.self=692
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.exe
C:\Windows\Temp\{93E1532F-40C2-47E7-885B-26541DA7BE54}\.cr\file.exe
04Isolated runtime analysis - Written fileObserved
wixstdba.dll
C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\wixstdba.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.154.209.174
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.185.48
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- 52.154.209.174
- 20.99.185.48
- 152.195.19.97
- 151.101.22.172
- 96.7.158.166
- 20.99.186.246
- 20.99.133.109
- 96.7.158.45
- 69.164.40.0
- 23.44.253.134
- C:\Windows\Temp\{93E1532F-40C2-47E7-885B-26541DA7BE54}\.cr\file.exe
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\wixstdba.dll
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\thm.xml
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\thm.wxl
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\bg.png
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\dotnet_hostfxr_6.0.36_win_x64.msi
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\dotnet_host_6.0.36_win_x64.msi
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\dotnet_runtime_6.0.36_win_x64.msi
- C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\windowsdesktop_runtime_6.0.36_win_x64.msi
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
- \Sessions\1\BaseNamedObjects\Global\MSILOG_4d3a81711db3531gol.ism.46x_niw_63.0.6_emitnur_tentod_000_94230121114202_)46x(_63.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
- \Sessions\1\BaseNamedObjects\Global\MSILOG_5cee3d361db3531gol.ism.46x_niw_63.0.6_rxftsoh_tentod_100_94230121114202_)46x(_63.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
- \Sessions\1\BaseNamedObjects\Global\MSILOG_5e969fab1db3531gol.ism.46x_niw_63.0.6_tsoh_tentod_200_94230121114202_)46x(_63.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 9b8b7390579a87b3f6a1…681b15Never scannednever seen before
- 72f2e7b06c562f1dd6cb…54824aNever scannednever seen before
- 9095bf7b6baa0107b40a…141e79Never scannednever seen before
- 4d6a2d306abe77e7dbdb…f64384Never scannednever seen before
- 285e32e649eb71a68f29…0e7633Never scannednever seen before
- 344acd0d3665ba489eb3…8d5557Never scannednever seen before
- 7343b45d45256c78885d…495efbNever scannednever seen before
- 6af5c2bc88b1e5ce188a…f44f22Never scannednever seen before
- ccb99abeb554c8772366…0a1c0dNever scannednever seen before
- db92e057f649d4804d3a…dba8e7Never 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.
- 6rule hits recorded
- 0 / 74engines flagged
- 3,701sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,701 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from .NET.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: windowsdesktop-runtime-6.0.36-win-x64.exe — 0d20debb26fc8b2bc84f25fbd9d4596a6364af8517ebf012e8b871127b798941
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\Temp\{93E1532F-40C2-47E7-885B-26541DA7BE54}\.cr\file.exe" -burn.clean.room="C:\Users\<USER>\Desktop\file.exe" -burn.filehandle.attached=788 -burn.filehandle.self=692
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.exe — C:\Windows\Temp\{93E1532F-40C2-47E7-885B-26541DA7BE54}\.cr\file.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: wixstdba.dll — C:\Windows\Temp\{90419382-2D6A-43C3-968B-E1131CD89684}\.ba\wixstdba.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.154.209.174 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.185.48 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- DebuggerCheck__API
- NET
- pe_detect_tls_callbacks
- PE_Digital_Certificate
- RansomPyShield_Antiransomware
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.
Evidence52.154.209.174 · 20.99.185.48 · 152.195.19.97
0 of 74 engines flagged this file
View all 74 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- windowsdesktop-runtime-6.0.36-win-x64.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: .NET
- Size
- 54.7 MB
- Last analyzed
- Sep 16, 2026, 2:17 PM UTC
0d20debb26fc8b2bc84f25fbd9d4596a6364af8517ebf012e8b871127b798941Safety & 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-6.0.36-win-x64.exe safe?
What is windowsdesktop-runtime-6.0.36-win-x64.exe?
How many antivirus engines detected windowsdesktop-runtime-6.0.36-win-x64.exe?
Is windowsdesktop-runtime-6.0.36-win-x64.exe digitally signed?
What is the SHA-256 hash of windowsdesktop-runtime-6.0.36-win-x64.exe?
Is it safe to run windowsdesktop-runtime-6.0.36-win-x64.exe?
How up to date is this analysis of windowsdesktop-runtime-6.0.36-win-x64.exe?
Community
Member reviews and reports for this exact file hash.