File scan report
Verdict Safe
Is dot Net Fx40_ Full_ setup. exe safe? Yes, no threats found.
Microsoft-signed .NET Framework 4.0 installer with zero engine detections and strong historical signer reputation.
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
Treat as a legitimate Microsoft .NET Framework 4.0 installer; no further security action needed.
Good practice2 tips
We found nothing harmful in this file.
Install 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 4
- Code signing Microsoft Corporation
- Test run Completed
- First seen 16y ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Zero of the 71 antivirus engines that checked it flagged the file. It is signed by Microsoft Corporation, matches a trusted-publisher record, and shows 4 of 5 similar hashes previously rated safe under the same signer. The file is a common, old .NET redistributable installer.
The complete absence of malicious detections across 75 engines, including 17 major antivirus engines, combined with verified Microsoft code-signing, places the sample firmly in the benign-signed-installer pattern. Historical signer data shows 8/9 prior samples rated safe, and four of five similar-hash matches under the same signer also returned safe verdicts with the same reason code. Prevalence data (widely seen and long established, nearly 90 k submissions) further supports legitimate commodity software. Sandbox artefacts that triggered rule-based rules are consistent with a .NET bootstrapper touching the Windows password store and system services during installation; no malicious files it created or sandbox verdicts were recorded.
What We Detected
75-engine scan returned zero malicious or suspicious labels. The executable is signed by Microsoft Corporation with a verified certificate issued 19 March 2010. Our trusted-publisher list explicitly includes Microsoft, and the file matches the expected .NET Framework 4.0 redistributable (dotNetFx40_Full_setup.exe).
Threat Behavior
One sandbox recorded typical installer behaviour: extraction of bitmap resources, creation of temporary files, and service-process interaction. Four MITRE techniques flagged by rules (T1005, T1055, T1543.003, T1562.001) map to expected bootstrapper actions rather than attacker tradecraft. no complete contacted-host reputation result was available, IPs, or programs it started were observed.
What To Do Now
The file can be executed or distributed without elevated concern. Keep Windows Defender and other security software enabled; no additional action is required.
Where this verdict could be wrong2 caveats
- The signer-history record shows 1/9 malicious historical sample for Microsoft Corporation — single outlier against 8/9 safe.
- triggeredHeuristics fired 'one of our behaviour rules' and 'one of our behaviour rules' on the Windows password store and svchost activity — sandbox artefacts from legitimate .NET installer bootstrapper.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Microsoft Corporation code signature verified
- 0/71 engines flagged malicious
- widely seen and long established prevalence with nearly 90 k submissions
- 4 of 5 similar signer-matched hashes previously rated safe
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- 23sandbox rule tags
- 8spawned processes
- 4network 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
23MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1005
- T1010
- T1018
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1106
- T1129· Loads modules
- T1222
- T1518.001· Checks your AV
- T1543.003· Service install
- T1562.001· Disables security
- T1564.001· Hides artifacts
- T1573
- T1574.001· Execution hijack
Observed activity
Processes started
8Programs the file ran, with their command lines.
executable.exe"C:\Users\<USER>\Desktop\executable.exe"Setup.exeC:\64a030f465b63e86a21d3070bd\\Setup.exe /x86 /x64 /ia64 /webdotNetFx40_Full_setup.exe%SAMPLEPATH%\dotNetFx40_Full_setup.exeSetup.exeD:\ce76a7a93bd6dce598a82dd535f708\Setup.exeSetup.exeD:\e22e1f9739f2b7f3804d29\Setup.exeSetup.exeD:\850a82b39511a7a1baa453a9e228\Setup.exe
Show all 8 entries for processes started
Setup.exeD:\9427d699768dace83788d5ee8f\Setup.exeSetup.exeD:\d0d40ca1514c8608fc\Setup.exe
Network contacts
44 hosts, listed as 4 addresses. Links show the host and path only.
- IP address
23.59.190.208 - IP address
8.240.39.126 - IP address
72.21.81.240 - IP address
168.62.240.75
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\dd_executable_decompression_log.txt - Written
C:\64a030f465b63e86a21d3070bd\header.bmp - Written
C:\64a030f465b63e86a21d3070bd\SplashScreen.bmp - Written
C:\64a030f465b63e86a21d3070bd\watermark.bmp - Written
C:\64a030f465b63e86a21d3070bd\DisplayIcon.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Print.ico
Show all 30 entries for files
- Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate1.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate2.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate3.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate4.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate5.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate6.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate7.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Rotate8.ico - Written
C:\64a030f465b63e86a21d3070bd\Graphics\Save.ico - Deleted
C:\Users\<USER>\AppData\Local\Temp\HFID92A.tmp.html - Deleted
C:\Users\<USER>\AppData\Local\Temp\Setup_20260118_035519045.html - Deleted
%USERPROFILE%\AppData\Local\Temp\HFI7CC.tmp.html - Deleted
%USERPROFILE%\AppData\Local\Temp\HFI2537.tmp.html - Deleted
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42 - Deleted
%USERPROFILE%\AppData\Local\Temp\HFI1B63.tmp.html - Deleted
%USERPROFILE%\AppData\Local\Temp\HFIEFC0.tmp.html - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER27B7.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C0.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E1.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER297D.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER297E.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER298E.tmp.txt - Deleted
%USERPROFILE%\AppData\Local\Temp\HFIF713.tmp.html
Registry and auto-start
5Settings the file changed, including ways to start again after a restart.
- Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Object List
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
Global\NetFxSetupMutexLocal\Shell.CMruPidlListCTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Show all 10 entries for mutexes
CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.TimListCache.FMPDefaultS-1-5-21-1482476501-1645522239-1417001333-500MUTEX.DefaultS-1-5-21-1482476501-1645522239-1417001333-500MSCTF.Shared.MUTEX.EBHSHIMLIB_LOG_MUTEX
Sandbox background — not the file
23The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
Show all 23 entries for sandbox background — not the file
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM host
a83f:8110:5766:7048:dc3d:45a4:1e57:1947 - VM host
192.168.0.85 - VM host
192.168.0.11 - VM host
13.107.4.50 - VM host
a83f:8110:0:0:700:700:2800:4000 - VM host
23.216.147.64 - VM host
a83f:8110:89:8424:3001:0:488d:152d - VM host
a83f:8110:0:0:4c88:21:0:0 - VM host
a83f:8110:0:0:1400:1400:2800:3800 - VM host
a83f:8110:cce1:d301:10:0:0:0 - VM host
23.216.147.76 - VM host
a83f:8110:5ec:26:4f:0:7:192 - VM host
20.80.129.13 - VM host
192.168.0.58 - VM host
a83f:8110:0:0:0:0:1:0 - VM host
a83f:8110:0:0:2800:0:0:0
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.
- d273460aa4d42f0b5764…55d8beNot checkedno saved verdict
- 19abcedf93d790e19fb3…9943e4Not checkedno saved verdict
- 02a7fe932029c6fa24d1…b3d1f6Not checkedno saved verdict
- ae041c8764f56fd89277…71c6e5Not checkedno saved verdict
- ab18374b3aab10e5979e…e2d33aNot checkedno saved verdict
- 5fb03593071a99c7b380…19723cNot checkedno saved verdict
- 7e682bdf51fac1b3991e…70888aNot checkedno saved verdict
- 8d82ff7970c9a67da813…c698abNot checkedno saved verdict
- 6b67c8a77c1a637b7273…3ffa66Not checkedno saved verdict
- 61d8339e89a9e48f8ae2…47c8a3Not checkedno saved verdict
Chapter 04
Technical details
None of the 71 antivirus engines that checked it flag it; signed by Microsoft Corporation.
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
- Aug 26, 2026, 7:53 PM UTC
- SHA-256
fa1afff978325f8818ce3a559d67a58297d9154674de7fd8eb03656d93104425- SHA-1
06becadb92a5fcca2529c0b93687c2a0c6d0d610- MD5
53406e9988306cbd4537677c5336aba4
About this file
dotNetFx40_Full_setup.exe is a Win32 EXE file of 889.4 kB.
- Type and size
- Win32 EXE · 889.4 kB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Apr 13, 2010On VirusTotal.
- Submitted by
- 3,687 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Antivirus consensus
0 of 71 engines flagged this file
4 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-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Community YARA rules matched, but all of them are generic capability, anti-debug or compiler rules that ordinary software also matches. Worth noting, not on their own cause for alarm.
- DebuggerCheck__APIgeneric
- NETgeneric
- PE_Digital_Certificategeneric
- SHA512_Constantsgeneric
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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 dotNetFx40_Full_setup.exe safe?
What is dotNetFx40_Full_setup.exe?
How many antivirus engines detected dotNetFx40_Full_setup.exe?
Is dotNetFx40_Full_setup.exe digitally signed?
What is the SHA-256 hash of dotNetFx40_Full_setup.exe?
Is it safe to install dotNetFx40_Full_setup.exe?
How up to date is this analysis of dotNetFx40_Full_setup.exe?
Community
Member reviews and reports for this exact file hash.