File scan report
Verdict Safe
Is vs_
A verified Microsoft signature, zero detections across 75 engines, and five matching signer precedents outweigh uncorroborated sandbox technique mappings.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Microsoft Corporation
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
2 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 70 antivirus engines that checked it flagged it.
No antivirus engine flagged the sample: the result is 0 of 75, including no major detections. Its signature verifies to Microsoft Corporation, a curated trusted publisher, and 15 of 16 historical samples associated with that signer were rated safe. Five signer-matched prior files also received safe decisions, strengthening the commercial-installer interpretation. One sandbox mapped activity to T1055, T1485, and surfaced the Windows password store-related activity, but it did not issue a malicious sandbox finding and no inspected child was identified as malicious.
What We Detected
The file is a signed Windows executable named vs_setup.exe. Its Authenticode signature verifies to Microsoft Corporation, the recognised-publisher check is true, and 0 of the 70 antivirus engines that checked it reported a detection. Five previous signer-matched files received safe decisions, while the signer's recorded history is 15 safe results out of 16 samples.
Threat Behavior
These are concerning mappings, but the sandbox did not issue a malicious finding, and none of 10 inspected dropped files was identified as malicious; their individual verdicts remain unknown. The executable also contacted 162.159.36.2 directly, but no complete host-reputation result is available because the contacted-host check was not saved.
What To Do Now
Use the file only if it came from Microsoft's official download channel and Windows still shows a valid Microsoft Corporation signature. Keep security software enabled, and redownload the installer if its origin or signature cannot be verified.
Where this verdict could be wrong5 caveats
- The sandbox's offensive-technique list includes T1055, T1485, and T1486, and one of our behaviour rules associated observed process activity with the Windows password store.
- The file is rare and newly seen: this exact hash was submitted once and first observed on Sep 8, 2026.
- The sample contacted 162.159.36.2 directly, but the missing contacted-host reputation result means no completed reputation cross-check is available.
- droppedChildren inspected 10 files without identifying a malicious child, but all 10 individual child verdicts are unknown.
- The signer-history record includes 1 malicious result among 16 Microsoft-signed historical samples.
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 of the 70 antivirus engines that checked it reported a detection.
- The Microsoft Corporation signature is verified.
- Microsoft matched the curated trusted-publisher list.
- Five of five signer-matched prior decisions were safe.
- No malicious sandbox verdict or malicious file it created was recorded.
- The exact hash is and has only one recorded submission.
- Sandbox mappings included T1055, T1485, and T1486.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 16sandbox rule tags
- 2spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
Includes 16 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; signed by Microsoft Corporation.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 10, 2026, 9:04 PM UTC
- SHA-256
abfc7e8ea00913fa526096de5a3fa9855d16538b3be955f83b39bafd6cd79ccd- SHA-1
2585ddb3177f565f72c8d7427342ed958fd4b5d4- MD5
85cc59c47dd8f8d247657fa3ace93afd
About this file
vs_setup.exe is a Win32 EXE file of 5.7 MB.
- Type and size
- Win32 EXE · 5.7 MB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Sep 8, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is vs_setup.exe safe?
What is vs_setup.exe?
How many antivirus engines detected vs_setup.exe?
Is vs_setup.exe digitally signed?
What is the SHA-256 hash of vs_setup.exe?
Is it safe to install vs_setup.exe?
How up to date is this analysis of vs_setup.exe?
Community
Member reviews and reports for this exact file hash.