File scan report
Verdict Safe
Is windowsdesktop- runtime- 6. 0. 16- win- x64. exe safe? Yes, no threats found.
No antivirus engine detected malware, while the verified .NET signature, extensive prevalence, and consistent signer-matched history support a legitimate Windows Desktop Runtime…
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
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 56 flagged
- Flagged 0
- No detection 56
- No result 19
- Code signing .NET
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The sample has no detections across 75 antivirus engines and carries a verified .NET signature. It is widely established, and four signer-matched files received consistent benign assessments; the installer-like sandbox activity produced no malicious runtime verdict.
All 56 antivirus engines that checked it returned without a malware detection, including ten major antivirus engines that explicitly reported no detection. The executable has a verified .NET signature, and all four historical samples associated with that signer were benign. Its 5,878 submissions from 3,487 sources since April 2023 indicate established commodity software rather than a newly introduced payload. One completed sandbox run observed installation-related system activity, including and T1543.003, but produced no malicious verdict and no inspected child was identified as malware. Host-reputation checking covered only two of the 17 observed domains and IP addresses, so it cannot establish complete network cleanliness, but no independent malicious signal offsets the strong signature, prevalence, and engine evidence.
What We Detected
The executable was not flagged by any of 75 antivirus engines. It carries a verified signature from .NET, has been submitted 5,878 times by 3,487 sources since April 2023, and is not packed or marked by high-entropy code analysis. Four prior files matching the verified signer—including other Windows Desktop Runtime releases—also received benign assessments.
Threat Behavior
One completed sandbox run showed typical installer operations such as temporary extraction, package-cache writes, uninstall registration, and Microsoft service contacts. It recorded T1134 and T1543.003, but the sandbox issued no malicious verdict, found no persistence indicators, and none of ten inspected files it created was identified as malicious. Reputation checking covered only two of the 17 distinct observed network hosts, so a complete host-reputation conclusion is unavailable.
What To Do Now
The evidence is consistent with a legitimate .NET Windows Desktop Runtime installer. Confirm that the file came from Microsoft or another trusted software distribution channel and keep security software enabled during installation.
Where this verdict could be wrong3 caveats
- The completed sandbox run recorded offensive techniques and T1543.003, although it issued no malicious verdict and the surrounding activity resembles software installation.
- The cross-check of 2 hosts does not cover all 17 distinct domains and IP addresses observed during execution, so host-reputation coverage is incomplete.
- Two communityComments assign a high threat score, but a community comment appeared to contain instructions aimed at automated analysis and neither annotation names a malware family or provides independent engine corroboration.
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/56 antivirus engines reported a malicious or suspicious result.
- The '.NET' code signature is verified.
- The file has 5,878 submissions from 3,487 sources since April 2023.
- Four of four signer-matched historical files received benign assessments.
- No malicious sandbox verdict or malicious file it created was found.
- Sandbox data included offensive-use techniques and T1543.003.
- Host-reputation checking covered only 2 of 17 distinct observed network hosts.
- The signer-history record contains only four historical samples and does not meet auto-trust thresholds.
6 sources checked · 5 complete · 1 partial. 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- 30sandbox rule tags
- 14spawned processes
- 7network contacts
- 40filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
30MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1007
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1036
- T1057· Lists programs
- T1059· Runs commands
- T1070.004· Covers its tracks
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1087
- T1091· USB spreading
- T1105· Network file transfer
- T1112
- T1120
- T1129· Loads modules
- T1134
- T1222
- T1489· Stops services
- T1497.001· Sandbox evasion
- T1518.001· Checks your AV
- T1543.003· Service install
- T1564· Hides artifacts
- T1564.003· Hides artifacts
- T1569.002
- T1574.002· Execution hijack
- T1614.001
Observed activity
Processes started
14Programs the file ran, with their command lines.
windowsdesktop-runti.exe"C:\Users\<USER>\AppData\Local\Temp\windowsdesktop-runti.exe"windowsdesktop-runti.exe"C:\Windows\Temp\{49E33E68-6B4C-4DE7-ADF2-EA24E72F65ED}\.cr\windowsdesktop-runti.exe" -burn.clean.room="C:\Users\<USER>\AppData\Local\Temp\windowsdesktop-runti.exe" -burn.filehandle.attached=664 -burn.filehandle.self=780windowsdesktop-runtime-6.0.16-win-x64.exe"C:\Windows\Temp\{E5CBD673-6414-420F-9D79-640D3F6167B7}\.be\windowsdesktop-runtime-6.0.16-win-x64.exe" -q -burn.elevated BurnPipe.{3D13B512-A5FE-48D0-AE20-9007DA988BDD} {E3F05BAC-36B2-4B43-901F-913F3FBA5E49} 4608windowsdesktop-runtime-6.0.16-win-x64.exe%SAMPLEPATH%\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{8C134603-B260-4F22-A122-244B36B3BF53}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{F666FEA7-3FA7-45F5-8E50-F92D7BDF4C9F}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exe
Show all 14 entries for processes started
windowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{A788BA16-9A55-4114-95DA-C1891B30CD85}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{66DA5715-E3E6-4967-81D4-1BD6C2F877DC}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{317745D7-CAFB-4ECF-B167-FBE3CA049C39}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{41E263D0-CDBE-4396-AD95-D99A49E10A44}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{74ACEB7F-D946-44C4-88C1-456F194CE5F8}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{6162A56A-13F5-447E-9EC1-A5B656FAEEF5}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{42B4EF78-BBE6-4315-93D1-473D26CC9ADF}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exewindowsdesktop-runtime-6.0.16-win-x64.exeC:\Windows\Temp\{4007ADC7-1994-4596-8D3D-FE9EFCC866B8}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exe
Network contacts
77 hosts, listed as 7 addresses. Links show the host and path only.
- IP address
20.96.52.198 - IP address
104.86.182.8 - IP address
104.96.203.18 - IP address
104.86.182.50 - IP address
20.22.113.133 - IP address
104.124.1.136
Show all 7 entries for network contacts
- IP address
23.198.146.35
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Package Cache\{8d173101-98c1-4e92-97c6-47c6840745a7}\windowsdesktop-runtime-6.0.16-win-x64.exe - Written
C:\Windows\Temp\{729F9F39-F121-44E7-AE6E-D03D86CC31DE}\.cr\windowsdesktop-runtime-6.0.16-win-x64.exe - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\wixstdba.dll - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\thm.xml - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\bg.png
Show all 30 entries for files
- Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1028\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1029\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1031\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1033\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1036\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1040\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1041\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1042\thm.wxl - Written
C:\Windows\Temp\{121DEA32-8892-4031-86E9-117C4A83C361}\.ba\1045\thm.wxl - Deleted
C:\Windows\Temp\{E5CBD673-6414-420F-9D79-640D3F6167B7}\dotnet_hostfxr_6.0.16_win_x64.msi - Deleted
C:\Windows\Temp\{E5CBD673-6414-420F-9D79-640D3F6167B7}\dotnet_host_6.0.16_win_x64.msi - Deleted
C:\Windows\Temp\{E5CBD673-6414-420F-9D79-640D3F6167B7}\dotnet_runtime_6.0.16_win_x64.msi - Deleted
C:\Windows\Temp\{E5CBD673-6414-420F-9D79-640D3F6167B7}\windowsdesktop_runtime_6.0.16_win_x64.msi - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFBA.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1066.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER10A5.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER248B.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER249C.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER249D.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER73E.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER838.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER878.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9C.tmp.WERInternalMetadata.xml
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8d173101-98c1-4e92-97c6-47c6840745a7}\BundleCachePath - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8d173101-98c1-4e92-97c6-47c6840745a7}\BundleUpgradeCode - Set
HKU\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_LOCAL_MACHINE\Software\Classes\Installer\Dependencies\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\{8d173101-98c1-4e92-97c6-47c6840745a7}\Dependents
Show all 15 entries for registry and auto-start
- Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\{8d173101-98c1-4e92-97c6-47c6840745a7}\Dependents\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\dotnet_runtime_48.67.58427_x64\Dependents - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\dotnet_runtime_48.67.58427_x64\Dependents\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Dotnet_CLI_HostFxr_48.67.58427_x64\Dependents - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Dotnet_CLI_HostFxr_48.67.58427_x64\Dependents\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Dotnet_CLI_SharedHost_48.3.31210_x64\Dependents - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies\Dotnet_CLI_SharedHost_48.3.31210_x64\Dependents\{8d173101-98c1-4e92-97c6-47c6840745a7} - Set
HKEY_CURRENT_USER\Software\Microsoft\RestartManager - Set
HKEY_CURRENT_USER\Software\Microsoft\RestartManager\Session0000
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Global\SyncRootManager\Sessions\1\BaseNamedObjects\Local\ZonesCacheCounterMutex\Sessions\1\BaseNamedObjects\Local\ZonesLockedCacheCounterMutex\Sessions\1\BaseNamedObjects\Global\MSILOG_893002481d96c9fgol.ism.46x_niw_61.0.6_emitnur_tentod_000_33001111403202_)46x(_61.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C\Sessions\1\BaseNamedObjects\Global\_MSIExecute\Sessions\1\BaseNamedObjects\Global\MSILOG_a645ce7f1d96c9fgol.ism.46x_niw_61.0.6_rxftsoh_tentod_100_33001111403202_)46x(_61.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Global\MSILOG_ad60efcd1d96c9fgol.ism.46x_niw_61.0.6_tsoh_tentod_200_33001111403202_)46x(_61.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C\Sessions\1\BaseNamedObjects\Global\MSILOG_b09053901d96c9fgol.ism.46x_niw_61.0.6_emitnur_potksedswodniw_300_33001111403202_)46x(_61.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_s…\BaseNamedObjects\Local\SM0:4188:304:WilStaging_02\BaseNamedObjects\Global\MSILOG_893002481d96c9fgol.ism.46x_niw_61.0.6_emitnur_tentod_000_33001111403202_)46x(_61.0.6_-_emitnuR_potkseD_swodniW_tfosorciM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
Sandbox background — not the file
16The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM host
query.prod.cms.rt.microsoft.com - VM host
www.microsoft.com - VM host
20.99.186.246 - VM host
192.229.211.108 - VM host
23.216.147.64
Show all 16 entries for sandbox background — not the file
- VM host
23.216.147.76 - VM host
20.99.185.48 - VM host
20.99.133.109 - VM host
20.99.184.37 - VM host
104.86.182.43 - VM host
20.69.140.28 - VM host
192.168.0.10 - VM host
23.216.81.152 - VM host
192.168.0.36 - VM host
23.198.171.50
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- b2e1b2dbecc4e3a9179e…dbf957Not checkedno saved verdict
- 3d35623534d14e2e5737…d811cbNot checkedno saved verdict
- 72f2e7b06c562f1dd6cb…54824aNot checkedno saved verdict
- 9095bf7b6baa0107b40a…141e79Not checkedno saved verdict
- 4d6a2d306abe77e7dbdb…f64384Not checkedno saved verdict
- 41a8787fdc9467f56343…c16104Not checkedno saved verdict
- d80c99407063c50e10d4…07225fNot checkedno saved verdict
- 7378a203b11b1fe53ded…810485Not checkedno saved verdict
- 285e32e649eb71a68f29…0e7633Not checkedno saved verdict
- 344acd0d3665ba489eb3…8d5557Not checkedno saved verdict
Chapter 04
Technical details
None of the 56 antivirus engines that checked it flag it; signed by .NET.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 9, 2026, 2:17 AM UTC
- SHA-256
1c1e90c6732a6389c9ebddd73bdca565d2f35671c2e7113e1704cb0a183e744a- SHA-1
b5158efdf04bc521d4d4f061882bccb8ae6bbbea- MD5
32acae733a473abb73467865fbd55ed0
About this file
windowsdesktop-runtime-6.0.16-win-x64.exe is a Win32 EXE file of 57.5 MB.
- Type and size
- Win32 EXE · 57.5 MB
- Signer
- .NETValid code signature.
- First seen
- Apr 11, 2023On VirusTotal.
- Submitted by
- 3,487 distinct sources
- Packer
- None detected
- Entropy
- 6.10 of 8
First scanned
Antivirus consensus
0 of 56 engines flagged this file
19 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-110 engines0flagged
- Tier-231 engines0flagged
- Low-trust15 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealNo result
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetNo result
- DeepInstinctClean
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetNo result
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaNo result
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSNo result
- TrendMicroNo result
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32No result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is windowsdesktop-runtime-6.0.16-win-x64.exe safe?
What is windowsdesktop-runtime-6.0.16-win-x64.exe?
How many antivirus engines detected windowsdesktop-runtime-6.0.16-win-x64.exe?
Is windowsdesktop-runtime-6.0.16-win-x64.exe digitally signed?
What is the SHA-256 hash of windowsdesktop-runtime-6.0.16-win-x64.exe?
Is it safe to run windowsdesktop-runtime-6.0.16-win-x64.exe?
How up to date is this analysis of windowsdesktop-runtime-6.0.16-win-x64.exe?
Community
Member reviews and reports for this exact file hash.