How to remove fc_setup.exe
fc_setup.exe
The module fc_setup.exe has been detected as Adware.VGen
fc_setup.exe is a Windows file recorded in the ThreatInfo database. The reported company name is Marek Jasinski . The current detection status is Adware.VGen, based on the latest analysis from 2025-02-15 23:01:21 (a year ago).
If fc_setup.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Adware.VGen.
File Details
| Company Name: | Marek Jasinski |
| MD5: | 53dceef77a719a5410eef546103ff125 |
| Size: | 1 MB |
| First Published: | 2018-01-11 17:13:28 (8 years ago) |
| Latest Published: | 2025-02-15 23:01:21 (a year ago) |
| Status: | Adware.VGen (on last analysis) | |
| Analysis Date: | 2025-02-15 23:01:21 (a year ago) |
Common Places:
| %sysdrive%\archive\utility\file mgt |
| %sysdrive%\truong\truong reseau\save_w2k\bureau |
| %sysdrive%\moje dokumenty\użytki\programy\narzędzia\manager plików |
| %sysdrive%\system volume information\_restore{83cda435-ce22-42b0-b9a2-8b3b30652ada} |
ThreatInfo has observed fc_setup.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.
Geography:
| 50.0% | ||
| 25.0% | ||
| 25.0% |
The strongest geographic signal for this file is France 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:
| Windows 10 | 75.0% | |
| Windows 7 | 25.0% |
The most common operating system signal for fc_setup.exe is Windows 10 with 75.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
fc_setup.exe is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x00400000 |
| Entry Address: | 0x0000c650 |
PE Sections:
| Name | Size of data | MD5 |
| CODE | 48640 | 1ca8b08cda2e6625f7530bc480f8de56 |
| DATA | 6144 | 8f099b67e90ca0613e81ccc37ab2e16f |
| BSS | 0 | 00000000000000000000000000000000 |
| .idata | 2560 | f5a0b241c721acdfe6e7a89f09d56172 |
| .tls | 0 | 00000000000000000000000000000000 |
| .rdata | 512 | c233c0ea7d984808a57c6681c85abaad |
| .reloc | 0 | 00000000000000000000000000000000 |
| .rsrc | 10240 | 7ebf4054d9bb7ddf6c756354e9964c86 |
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.
More information:
