File scan report
Verdict Safe
Is SETUP.
No engines flagged this established Microsoft-signed installer, while its clean sandbox result and extensive prevalence outweigh one uncorroborated ransomware-oriented YARA match.
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.
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.
Antivirus results
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing Microsoft Corporation
- Test run Completed
- First seen 2y 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 executable carries a verified Microsoft Corporation signature, and none of the 71 antivirus engines that checked it flagged it. It is widely encountered, produced no offensive techniques in the completed sandbox, and contacted hosts were fully checked without malicious or suspicious matches; one ransomware-oriented community rule appears to be an isolated false positive.
The strongest identity evidence is the verified Microsoft Corporation signature and curated publisher match. None of the 71 antivirus engines that checked it flagged the executable, including all 17 reporting major antivirus engines. The file has been submitted 4,152 times by 2,939 sources, making a newly introduced impersonation scenario unlikely. One completed sandbox returned clean and mapped no offensive techniques, while the complete host-reputation check found no malicious or suspicious host among 18 observed contacts. The VECT ransomware rule is meaningful dissent, but it stands alone against the engine results, runtime findings, lack of packing, and five prior benign signer matches. Comments contained instruction-like contamination and were therefore excluded from the decision.
What We Detected
None of the 71 antivirus engines that checked it flagged the executable. It has a verified digital signature from Microsoft Corporation, which matches the curated trusted publisher identity, and 31 of 32 historical samples associated with this signer were benign. The file is also well established, with 4,152 submissions from 2,939 sources.
Threat Behavior
One completed sandbox run returned clean and recorded no offensive MITRE techniques, persistence indicators, written files, or files it created. The host-reputation check covered all 18 distinct observed contacts and found no malicious or suspicious matches. Although injection targets were listed, this was not accompanied by an offensive technique or a malicious sandbox assessment.
Conflicting Evidence
A community YARA rule named VECT_Ransomware matched the sample, alongside two generic rules. This single malware-specific match is not corroborated by any antivirus detection, packing evidence, offensive activity in the test run, malicious child, or hostile network destination, so it most likely represents an overly broad rule match.
What To Do Now
The file can be used if it came through an expected Microsoft installation or update channel. Keep security software enabled and verify that the signature still shows Microsoft Corporation before execution if the file was obtained from an unfamiliar source.
Where this verdict could be wrong3 caveats
- One malware-specific community rule named VECT ransomware matched, but no antivirus engine corroborated it and the completed sandbox observed no offensive techniques.
- The sandbox reports injection targets including WMIADAP.EXE and updater processes; however, it returned a clean verdict and recorded no offensive MITRE techniques.
- The publisher history contains one previously malicious sample among 32, so the signature is strong legitimacy evidence rather than an absolute guarantee.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The executable has a verified Microsoft Corporation digital signature and matches the curated Microsoft publisher identity.
- None of the 71 antivirus engines that checked it flagged the file.
- A completed sandbox run returned clean and observed no offensive techniques.
- All 18 observed network hosts were covered by the reputation check, with no malicious or suspicious matches.
- The file is well established, with 4,152 submissions from 2,939 sources.
- One community-authored rule associated the file with VECT ransomware, although no other source corroborated that match.
- The sandbox listed interactions with WMIADAP.EXE and several updater processes, but did not classify the activity as offensive.
- One of 32 historical samples associated with the signer received a malicious result.
6 sources checked · all complete. 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- 8sandbox rule tags
- 4spawned processes
- 2network contacts
- 12filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
8MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1070· Covers its tracks
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
Observed activity
Processes started
4Programs the file ran, with their command lines.
executable.exe"C:\Users\<USER>\Desktop\executable.exe"C__$WINDOWS.~BT_setup.exe%SAMPLEPATH%\C__$WINDOWS.~BT_setup.exeSETUP.EXE%SAMPLEPATH%\SETUP.EXE72a0bcac2d4de630ad094bfc312bd4431aa5c286c683de7e0650c1675e5fc7c5.exe%SAMPLEPATH%\72a0bcac2d4de630ad094bfc312bd4431aa5c286c683de7e0650c1675e5fc7c5.exe
Network contacts
22 hosts, listed as 2 addresses. Links show the host and path only.
- IP address
23.64.157.53 - IP address
23.48.190.24
Files
10Files the file created, changed or deleted.
- Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF378.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF443.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF463.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB1A.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB2A.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB2B.tmp.txt
Show all 10 entries for files
- Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\Windows\System32\wbem\Performance\WmiApRpl.h - Deleted
C:\Windows\System32\wbem\Performance\WmiApRpl.ini - Deleted
%USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Microsoft.Windows.Setup.Autorun-F2F632C7-AC94-4B7A-D06B-97D56ED9DC8B\Sessions\1\BaseNamedObjects\Microsoft.Windows.Setup.Autorun-F2F632C7-AC94-4B7A-D06B-97D56ED9DC8B
Sandbox background — not the file
49The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google724_1030626854\bin\updater.exe - VM process
updater.exeC:\Program Files\Google2480_1143751753\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3192_831462237\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3532_1743341110\bin\updater.exe
Show all 49 entries for sandbox background — not the file
- VM process
updater.exeC:\Program Files\Google2212_705684124\bin\updater.exe - VM process
updater.exeC:\Program Files\Google2392_1448918954\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3012_702997170\bin\updater.exe - VM process
updater.exeC:\Program Files\Google604_1775115625\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3624_1609573874\bin\updater.exe - VM injection target
\\?\C:\Windows\system32\wbem\WMIADAP.EXE - VM injection target
C:\Program Files\Google724_1030626854\bin\updater.exe - VM injection target
C:\Program Files\Google2480_1143751753\bin\updater.exe - VM injection target
C:\Program Files\Google3192_831462237\bin\updater.exe - VM injection target
C:\Program Files\Google3532_1743341110\bin\updater.exe - VM injection target
C:\Program Files\Google2212_705684124\bin\updater.exe - VM injection target
C:\Program Files\Google2392_1448918954\bin\updater.exe - VM injection target
C:\Program Files\Google3012_702997170\bin\updater.exe - VM injection target
C:\Program Files\Google604_1775115625\bin\updater.exe - VM injection target
C:\Program Files\Google3624_1609573874\bin\updater.exe - VM injection target
C:\Program Files\Google2908_1786364515\bin\updater.exe - VM injection target
C:\Program Files\Google1568_443694268\bin\updater.exe - VM injection target
C:\Program Files\Google3680_138845824\bin\updater.exe - VM injection target
C:\Program Files\Google3828_652723960\bin\updater.exe - VM injection target
C:\Program Files\Google2916_1014928843\bin\updater.exe - VM host
www.microsoft.com - VM host
res.public.onecdn.static.microsoft - VM host
bg.microsoft.map.fastly.net - VM host
svc.ha-teams.office.com - VM host
teams-mrc-ww-perf.tm-4.office.com - VM host
20.99.133.109 - VM host
192.229.211.108 - VM host
20.99.184.37 - VM host
192.168.0.79 - VM host
23.216.81.152 - VM host
131.253.33.203 - VM host
192.168.0.1 - VM host
a83f:8110:2d00:4600:4300:3500:4100:3200 - VM host
192.168.0.4 - VM host
20.99.186.246 - VM host
192.168.0.57 - VM host
192.168.0.39 - VM host
192.168.0.38 - VM host
52.154.209.174 - VM host
23.192.210.9 - VM host
151.101.22.172 - VM host
23.213.37.172 - VM host
192.168.0.16
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 · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 15, 2026, 4:12 AM UTC
- SHA-256
72a0bcac2d4de630ad094bfc312bd4431aa5c286c683de7e0650c1675e5fc7c5- SHA-1
e65e779cd8a04cd7f6e8137faafb8b794ad76cc4- MD5
6219d2192604c34e31ea8521d77dcb13
About this file
SETUP.EXE is a Win32 EXE file of 99.9 kB.
- Type and size
- Win32 EXE · 99.9 kB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Apr 4, 2024On VirusTotal.
- Submitted by
- 2,939 distinct sources
- Packer
- None detected
- Entropy
- 4.24 of 8
First scanned
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.
- VECT_Ransomwaregeneric
- PE_Digital_Certificategeneric
- Sus_Obf_Enc_Spoof_Hide_PEgeneric
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 SETUP.EXE safe?
What is SETUP.EXE?
How many antivirus engines detected SETUP.EXE?
Is SETUP.EXE digitally signed?
What is the SHA-256 hash of SETUP.EXE?
Is it safe to install SETUP.EXE?
How up to date is this analysis of SETUP.EXE?
Community
Member reviews and reports for this exact file hash.