Is Windows Movie Maker 6.0 (x64, Vista).msi safe?
No engine detected malware, and this long-circulating installer has substantial prevalence, no malicious sandbox verdict, and no known malicious dropped child.
All 75 engines returned without a malicious or suspicious detection, including 17 tier-1 products. The installer has circulated since 2011 across thousands of submissions, while one runtime analysis produced no malicious sandbox verdict; however, it is unsigned and several behavior mappings warrant obtaining it from a trusted archive.
3240f2d30e0057215f…77444bc0b2fa4bRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 engines returned without a malicious or suspicious detection, including 17 tier-1 products. The installer has circulated since 2011 across thousands of submissions, while one runtime analysis produced no malicious sandbox verdict; however, it is unsigned and several behavior mappings warrant obtaining it from a trusted archive.
The strongest evidence is the absence of detections across 75 engines, including all 17 tier-1 products. The sample has also circulated widely since 2011, which makes an undetected long-running malware campaign unlikely. One completed sandbox run did not issue a malicious verdict, and none of the ten inspected child hashes was known to be malicious, although their individual verdicts remain unresolved. The T1055, T1543.003, T1547.001, and T1548 mappings are noteworthy, but installer activity can generate broad behavioral mappings and the available runtime evidence does not independently establish abuse. Because the package is unsigned and no complete contacted-host reputation result exists, provenance should still be verified before installation.
What We Detected
No malicious or suspicious result was reported by any of the 75 engines. Avast, BitDefender, ESET-NOD32, Kaspersky, Microsoft, and the other tier-1 products all returned without a detection. The file has been known since 2011 and has 2,682 submissions from 2,184 sources, providing substantial long-term prevalence.
Threat Behavior
One completed sandbox run launched the MSI through Windows Installer and registered Movie Maker DLLs. The evidence maps some activity to T1055, T1543.003, T1547.001, and T1548, but the sandbox did not issue a malicious verdict. Ten dropped child hashes were inspected with no known malicious child found, although all ten lack conclusive individual verdicts. No domains, IP addresses, or URLs were observed in the saved run; contacted-host reputation was not separately checked or saved.
What To Do Now
The package is unsigned, so its publisher cannot be authenticated cryptographically. Obtain this legacy installer only from a trusted archive, verify that its SHA-256 is 3240f2d30e0057215f26b2ab66e14c5f77769295c98eea62f077444bc0b2fa4b, and keep endpoint protection enabled while installing.
Where this verdict could be wrong4 caveats
- signing.signed=false despite signing.applicable=true, so publisher identity cannot be authenticated.
- behaviour.offensiveTechniques includes T1055, T1543.003, T1547.001, and T1548; these mappings can indicate injection, service installation, startup modification, or elevation, though no sandbox produced a malicious verdict.
- droppedChildren.rollup.unknown=10, meaning the child-file check found no known malicious child but did not establish that the children were clean.
- contactedHosts=null, so no completed host-reputation cross-check is available.
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/75 engines reported a malicious or suspicious result
- All 17 tier-1 engines returned without detection
- Known since 2011 with 2,184 sources and 2,682 submissions
- No malicious sandbox verdict in one completed run
- No known malicious child among ten inspected hashes
- Unsigned Windows Installer despite signing being applicable
- Runtime mappings include T1055, T1543.003, T1547.001, and T1548
- All ten dropped-child verdicts remain unknown
- No completed contacted-host reputation cross-check is available
- Legacy software may contain unpatched vulnerabilities
Use only a trusted archival source and verify the SHA-256 before installation. Keep endpoint protection enabled, particularly because the installer is unsigned and the software is obsolete.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 20MITRE ATT&CK techniques
- 14spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Windows Movie Maker 6.0 (x64, Vista).msi
3240f2d30e0057215f26b2ab66e14c5f77769295c98eea62f077444bc0b2fa4b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\AppData\Local\Temp\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ProgramData
C:\ProgramData
04Isolated runtime analysis - Written fileObserved
Templates
C:\ProgramData\Microsoft\Windows\Templates
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Windows\Fonts
- C:\Program Files (x86)
- C:\Program Files (x86)\Microsoft
- C:\Windows\Installer\MSI4DC8.tmp
- C:\Windows\Installer\MSI4F30.tmp
- C:\Config.Msi\CMP52F8.tmp
- C:\Config.Msi
- C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Caches\{AFBF9F1A-8EE8-4C77-AF34-C647E37CA0D9}.1.ver0x0000000000000000.db
- Global\_MSIExecute
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- cversions.3.m
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 73771967ee9175f9a52d…cd53b1Never scannednever seen before
- 5efc3db97e3be33ec8c8…0dece9Never scannednever seen before
- 671a1976d23b301804e3…47e75eNever scannednever seen before
- 8312f1eac2efd5c68607…73b353Never scannednever seen before
- 6b2a92a1ef0e8242efe7…b852ffNever scannednever seen before
- 205fa2386c88b07b4d9e…7a4f50Never scannednever seen before
- aec73bfb142e9133e69d…16c96fNever scannednever seen before
- 617a3b77a55ef02d9a63…6c5320Never scannednever seen before
- 4bb45b8ae21dbfb52adf…5a643fNever scannednever seen before
- 3b6349b036405861c247…1483bbNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 2,184sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 2,184 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: Windows Movie Maker 6.0 (x64, Vista).msi — 3240f2d30e0057215f26b2ab66e14c5f77769295c98eea62f077444bc0b2fa4b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\AppData\Local\Temp\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ProgramData — C:\ProgramData
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Templates — C:\ProgramData\Microsoft\Windows\Templates
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\system32\svchost.exe -k DcomLaunch -p
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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.
Fingerprint and provenance
- File name
- Windows Movie Maker 6.0 (x64, Vista).msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 11.0 MB
- Last analyzed
- Sep 23, 2026, 4:49 PM UTC
3240f2d30e0057215f26b2ab66e14c5f77769295c98eea62f077444bc0b2fa4bSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Windows Movie Maker 6.0 (x64, Vista).msi safe?
What is Windows Movie Maker 6.0 (x64, Vista).msi?
How many antivirus engines detected Windows Movie Maker 6.0 (x64, Vista).msi?
What is the SHA-256 hash of Windows Movie Maker 6.0 (x64, Vista).msi?
Is it safe to install Windows Movie Maker 6.0 (x64, Vista).msi?
How up to date is this analysis of Windows Movie Maker 6.0 (x64, Vista).msi?
Community
Member reviews and reports for this exact file hash.