GridinSoft Threat Intelligence
FMService64.exe file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2020-08-07 14:46:52 (5 years ago); latest analysis 2021-01-10 23:45:21 (5 years ago).
Company metadata: Fortemedia. Product metadata: Fortemedia APO Control Service.
Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
FMService64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Fortemedia APO Control Service. The reported company name is Fortemedia. The current detection status is Clean, based on the latest analysis from 2021-01-10 23:45:21 (5 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Fortemedia APO Control Service |
| Company Name: | Fortemedia |
| MD5: | db307daf4a2202560c7eb2d5c14d26e9 |
| Size: | 356 KB |
| First Published: | 2020-08-07 14:46:52 (5 years ago) |
| Latest Published: | 2021-01-10 23:45:21 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-10 23:45:21 (5 years ago) |
Overview
| Signed By: | Microsoft Windows Hardware Compatibility Publisher |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-3345049087-2262454278-399833233-1001\driver updater\downloads\e972203d-6394-472a-a612-cdf5ddcfd97d |
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-3345049087-2262454278-399833233-1001\driver updater\downloads\36 |
| %commonappdata%\reviversoft\driver reviver\downloads\35646135-7f58-4c7d-b76a-c4b7d40cda45 |
| %commonappdata%\reviversoft\driver reviver\downloads\2 |
ThreatInfo has observed FMService64.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen FMService64.exe across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Mexico with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for FMService64.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
FMService64.exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
619c04f0f3c9cdd617974fc84c2c7177
18bc54516dc7c8466654060f10b5fd84
783bcdc04f366aec689a1ac0e14cbbf7
3ed36c644ee6ed3c79e7255bb80631cd
6262121adccf744a94ebe4f4512d1fa9
54fa0d4eadf98aa26fd392705d52f26d
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.