File scan report
Verdict Safe
Is Security Health Setup. exe safe? Yes, no threats found.
Microsoft-signed Windows Security Health installer with zero detections across 75 engines, thousands of submitters over more than two years, and a clean sandbox run.
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
This matches the genuine Microsoft Windows Security installer; verify the Microsoft signature in the file properties before running, and keep your security software enabled.
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 Windows Publisher
- Test run Completed
- First seen 2y ago
Chapter 02
Why we think so
1 point 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 this file, and it carries a verified Microsoft Windows Publisher signature. It has been seen from over 3,400 sources since early 2024, and its single sandbox run finished clean. It matches the official installer used to restore the Windows Security app.
None of the 70 antivirus engines that checked it flagged the file, including all 17 major antivirus engines that returned a result. The code signature is verified and belongs to Microsoft Windows Publisher, matching our curated trusted-publisher list, with no brand mismatch. The file is widely distributed, with more than 3,400 independent submitters over about 955 days, which rules out a rare lookalike impersonating security software. The one sandbox run returned clean; the service-creation and token techniques it mapped are consistent with an installer registering a Windows service, and every contacted host checked against our cache came back without malicious or suspicious hits.
What We Detected
None of the 70 antivirus engines that checked it flagged this file. It is signed with a verified Microsoft Windows Publisher certificate and has been submitted by more than 3,400 independent sources since March 2024. Its name and signer are consistent with the official Windows Security Health setup package.
Threat Behavior
One sandbox run completed and returned clean. The run mapped service creation and token-related techniques, which are expected for a system installer that registers a Windows service. Updater processes seen in the run appear to belong to the analysis environment. All contacted hosts we checked had no malicious or suspicious record, and the network traffic matched Microsoft infrastructure and the VM's background activity.
What To Do Now
If you downloaded this to repair a missing Windows Security app, it matches the genuine Microsoft-signed package. Confirm the digital signature shows Microsoft before running it, and keep your antivirus protection enabled.
Where this verdict could be wrong2 caveats
- The sandbox run mapped token manipulation and service creation and recorded injection into updater processes, but these match an installer registering a system service and the VM's own updater activity, and the run itself returned clean.
- A third-party community annotation gave a high threat score, but the comments block contained instruction-like text and was downweighted; no engine corroborates it.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged the file
- Verified Microsoft Windows Publisher code signature on our trusted-publisher list
- Widely distributed, with over 3,400 independent submitters over more than two years
- The sandbox run finished with a clean result
- Hosts contacted during analysis had no malicious or suspicious reputation in our records
- The sandbox run recorded service creation and token-related techniques, which are expected for a system installer but are worth noting.
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- 15sandbox rule tags
- 3spawned processes
- 3network contacts
- 30filesystem & 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
15MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1007
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1134
- T1497.001· Sandbox evasion
- T1518· Checks your AV
- T1543.003· Service install
- T1614
Observed activity
Processes started
3Programs the file ran, with their command lines.
software.exe"C:\Users\<USER>\Desktop\software.exe"securityhealthsetup.exe%SAMPLEPATH%\securityhealthsetup.exe85ed8506f3ea081c12a0eab17edfbd8f900af0fbaa43a42ca46d8e5ad8c2e8b5.exe%SAMPLEPATH%\85ed8506f3ea081c12a0eab17edfbd8f900af0fbaa43a42ca46d8e5ad8c2e8b5.exe
Network contacts
33 hosts, listed as 3 addresses. Links show the host and path only.
- IP address
23.62.209.152 - IP address
23.55.185.172 - IP address
23.32.75.15
Files
30Files the file created, changed or deleted.
- Written
C:\Users\user\Desktop\-install\ar-SA - Written
C:\Users\user\Desktop\-install\bg-BG - Written
C:\Users\user\Desktop\-install\ca-ES - Written
C:\Users\user\Desktop\-install\cs-CZ - Written
C:\Users\user\Desktop\-install\da-DK - Written
C:\Users\user\Desktop\-install\de-DE
Show all 30 entries for files
- Written
C:\Users\user\Desktop\-install\el-GR - Written
C:\Users\user\Desktop\-install\en-GB - Written
C:\Users\user\Desktop\-install\en-US - Written
C:\Users\user\Desktop\-install\es-ES - Written
C:\Users\user\Desktop\-install\es-MX - Written
C:\Users\user\Desktop\-install\et-EE - Written
C:\Users\user\Desktop\-install\fi-FI - Written
C:\Users\user\Desktop\-install\fr-CA - Written
C:\Users\user\Desktop\-install\fr-FR - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2555.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2630.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2670.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C0D.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C1E.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C2E.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C17.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CC3.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D03.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5204.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5214.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER5225.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER615.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E0.tmp.csv
Registry and auto-start
4Settings the file changed, including ways to start again after a restart.
- Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService126.0.6441.0\Start - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService126.0.6441.0\ImagePath - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService127.0.6490.0\Start - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService127.0.6490.0\ImagePath
Sandbox background — not the file
46The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM process
updater.exeC:\Program Files (x86)\Google3888_119029711\bin\updater.exe - VM process
updater.exeC:\Program Files (x86)\Google3792_1594481762\bin\updater.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google3500_1083599128\bin\updater.exe - VM process
updater.exeC:\Program Files\Google968_2140063707\bin\updater.exe
Show all 46 entries for sandbox background — not the file
- VM process
updater.exeC:\Program Files\Google3008_300809459\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3724_379928063\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3608_434233257\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3748_595854826\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3140_242745720\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3956_1841428777\bin\updater.exe - VM injection target
\\?\C:\Windows\system32\wbem\WMIADAP.EXE - VM injection target
C:\Program Files (x86)\Google3888_119029711\bin\updater.exe - VM injection target
C:\Program Files (x86)\Google3792_1594481762\bin\updater.exe - VM injection target
C:\Program Files\Google3500_1083599128\bin\updater.exe - VM injection target
C:\Program Files\Google968_2140063707\bin\updater.exe - VM injection target
C:\Program Files\Google3008_300809459\bin\updater.exe - VM injection target
C:\Program Files\Google3724_379928063\bin\updater.exe - VM injection target
C:\Program Files\Google3608_434233257\bin\updater.exe - VM injection target
C:\Program Files\Google3748_595854826\bin\updater.exe - VM injection target
C:\Program Files\Google3140_242745720\bin\updater.exe - VM injection target
C:\Program Files\Google3956_1841428777\bin\updater.exe - VM injection target
C:\Program Files\Google356_220700203\bin\updater.exe - VM injection target
C:\Program Files\Google4064_1956406388\bin\updater.exe - VM injection target
C:\Program Files\Google3020_1256284946\bin\updater.exe - VM injection target
C:\Program Files\Google912_80658064\bin\updater.exe - VM host
www.microsoft.com - VM host
res.public.onecdn.static.microsoft - VM host
20.99.184.37 - VM host
192.229.211.108 - VM host
20.99.186.246 - VM host
23.216.147.76 - VM host
20.99.133.109 - VM host
23.216.81.152 - VM host
23.216.147.64 - VM host
192.168.0.51 - VM host
20.99.185.48 - VM host
184.25.191.235 - VM host
192.168.0.21 - VM host
23.55.140.42 - VM host
192.168.0.63 - VM host
52.154.209.174 - VM host
52.185.73.156 - VM host
192.168.0.22 - VM host
192.168.0.157
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; signed by Microsoft Windows Publisher.
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 16, 2026, 1:56 PM UTC
- SHA-256
85ed8506f3ea081c12a0eab17edfbd8f900af0fbaa43a42ca46d8e5ad8c2e8b5- SHA-1
e16941e14861a6d24750ecdf05c548189b33182a- MD5
96258c71f00cc9528f18049f60ed7360
About this file
SecurityHealthSetup.exe is a Win32 EXE file of 19.0 MB.
- Type and size
- Win32 EXE · 19.0 MB
- Signer
- Microsoft Windows PublisherValid code signature.
- First seen
- Mar 5, 2024On VirusTotal.
- Submitted by
- 3,425 distinct sources
- Packer
- None detected
- Entropy
- 7.58 of 8
First scanned Updated
Antivirus consensus
0 of 70 engines flagged this file
5 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-235 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
- ClamAVNo result
- 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
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 SecurityHealthSetup.exe safe?
What is SecurityHealthSetup.exe?
How many antivirus engines detected SecurityHealthSetup.exe?
Is SecurityHealthSetup.exe digitally signed?
What is the SHA-256 hash of SecurityHealthSetup.exe?
Is it safe to run SecurityHealthSetup.exe?
How up to date is this analysis of SecurityHealthSetup.exe?
Community
Member reviews and reports for this exact file hash.