File scan report
Verdict Safe
Is Store
No engines flagged this verified Microsoft-signed installer, and its established history, sandbox results, host checks, and inspected files it created show no corroborated threat.
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.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Microsoft Corporation
- Test run Completed
- First seen 2y ago
Chapter 02
Why we think so
0 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 70 antivirus engines that checked it flagged the executable, and its Microsoft Corporation signature verified successfully. Its publisher history contains 38 safe samples and no malicious ones; completed observation from the test run, comprehensive host checks, and inspected file it created results provide no corroborated harmful evidence.
The executable has a valid Microsoft Corporation signature and matches the curated Microsoft publisher entry. None of the 70 antivirus engines that checked it flagged it, including the participating major antivirus engines. The combined sandbox verdict was clean, with no named process-injection target or other high-risk technique supported by a concrete artefact. The host-reputation check covered all 33 distinct observed contacts and found no malicious or suspicious hosts, while no inspected child was malicious. The file is also widely submitted and was first seen on Oct 30, 2024, which is consistent with established commodity software. Mixed outcomes for files built with the same import table are weak context because those files do not share this file's verified signer.
What We Detected
None of the 70 antivirus engines that checked it flagged this executable. Its code signature verified as Microsoft Corporation, the publisher matched the curated Microsoft entry, and the available publisher history contains 38 safe samples with no malicious samples.
Threat Behavior
The combined sandbox verdict was clean. Two automated technique mappings appeared, but neither had the concrete artefact it described: no injected process was identified and no supported defence-tampering action was recorded. The reputation check covered all 33 distinct observed contacts and found no malicious or suspicious hosts. No inspected file it created was malicious, and four were known-software reference entries.
What To Do Now
The evidence supports normal use when the file came from the expected distribution channel. Keep security software enabled and obtain another copy from the official source if the file arrived unexpectedly or its origin cannot be verified.
Where this verdict could be wrong2 caveats
- The sandbox summary mapped and T1562.001, but recorded neither a named injection target nor the artefacts those mappings describe.
- Similar files sharing the import-table fingerprint have mixed prior outcomes, including two malicious results, but none shares this file's signer and the match can arise from common build frameworks.
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 carries a valid Microsoft Corporation signature.
- None of the 70 antivirus engines that checked it flagged the file.
- The publisher history contains 38 safe samples and no malicious samples.
- The combined sandbox verdict was clean and recorded no named injection target.
- All 33 distinct observed contacts were covered by the reputation check, with no malicious or suspicious results.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 6 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 6isolated sandbox runs
- 20sandbox rule tags
- 9spawned processes
- 28network contacts
- 39filesystem & mutex artifacts
Includes the sandbox verdicts, 20 mapped techniques, every process, file, registry and network entry and 8 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 · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Nov 4, 2026, 4:03 AM UTC
- SHA-256
509c3e05cc31ebad6853b84b93655aab19780b924b4f9601b0bc3e88b76efb5f- SHA-1
29208a0b188f935f18c1321a646c55c3ee918a4b- MD5
4ac2e6bed084acf9ad010006acc4e24e
About this file
StoreInstaller.exe is a Win32 EXE file of 1.1 MB.
- Claims to be
- Store InstallerFrom the file's own version information, written by whoever built it.
- Original name
- StoreInstaller.exeMatches the shared file name.
- Type and size
- Win32 EXE · 1.1 MB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Oct 30, 2024On VirusTotal.
- Submitted by
- 178 distinct sources
- Packer
- None detected
- Entropy
- 6.83 of 8
First scanned
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 StoreInstaller.exe safe?
What is StoreInstaller.exe?
How many antivirus engines detected StoreInstaller.exe?
Is StoreInstaller.exe digitally signed?
What is the SHA-256 hash of StoreInstaller.exe?
Is it safe to run StoreInstaller.exe?
How up to date is this analysis of StoreInstaller.exe?
Community
Member reviews and reports for this exact file hash.