AdvancedWindowsManager.exe threat report
ThreatInfo file report
AdvancedWindowsManager.exe
This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for AdvancedWindowsManager.exe. ThreatInfo currently classifies this sample as PUP.Microleaves.
GridinSoft Anti-Malware detection
GridinSoft already detects this file
The latest ThreatInfo record shows AdvancedWindowsManager.exe detected as PUP.Microleaves. You can download GridinSoft Anti-Malware to scan the system and remove this detection if the file is present on your device.
- Detection name
- PUP.Microleaves
- Last analysis
- 2022-02-27 23:15:16 (4 years ago)
- File hash
- 26f21ed76944ed83382851d9f2453b0e
AdvancedWindowsManager.exe is a Windows file recorded in the ThreatInfo database. It is associated with Advanced Windows Manager. The reported company name is Advanced Windows Manager. The current detection status is PUP.Microleaves, based on the latest analysis from 2022-02-27 23:15:16 (4 years ago).
If AdvancedWindowsManager.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 PUP.Microleaves.
File Details
| Product Name: | Advanced Windows Manager |
| Company Name: | Advanced Windows Manager |
| MD5: | 26f21ed76944ed83382851d9f2453b0e |
| Size: | 471 KB |
| First Published: | 2021-06-16 20:06:32 (4 years ago) |
| Latest Published: | 2022-02-27 23:15:16 (4 years ago) |
| Status: | PUP.Microleaves (on last analysis) | |
| Analysis Date: | 2022-02-27 23:15:16 (4 years ago) |
Detection screenshot
The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.
Overview
| Signed By: | Microleaves LTD |
| Status: | Valid |
The signature on AdvancedWindowsManager.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
| %programfiles%\advancedwindowsmanager |
ThreatInfo has observed AdvancedWindowsManager.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:
| 26.4% | ||
| 13.2% | ||
| 13.2% | ||
| 13.2% | ||
| 11.3% | ||
| 11.3% | ||
| 9.4% | ||
| 1.9% |
The strongest geographic signal for this file is Brazil with 26.4% 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 | 100.0% |
The most common operating system signal for AdvancedWindowsManager.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
AdvancedWindowsManager.exe is identified as pe for 64 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.
| Subsystem: | Windows CUI |
| PE Type: | pe |
| OS Bitness: | 64 |
| Image Base: | 0x0000000000400000 |
| Entry Address: | 0x000014e0 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 32768 | b6007d16b1d8fb33df78e884c8bbfd25 |
| .data | 1024 | 422355e18def0a89a834f8da7d429b2d |
| .rdata | 5632 | bf51be5fd863efac1209f0291e9fc05e |
| .pdata | 1536 | 207db5b29dd001ff15d2766732f387f4 |
| .xdata | 1536 | a58b9aa061c0f7843869047dc265ac2f |
| .bss | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .idata | 4096 | 6a8f2af11fdcded0e37cf22462defdc9 |
| .CRT | 512 | f25b469bde7c5813d18c6ad29c30d730 |
| .tls | 512 | bf619eac0cdf3f68d496ea9344137e8b |
| .rsrc | 371712 | 1702cf98c78ec83c3aaa9e4a3a7ceca9 |
| /4 | 512 | 962a3afeebcf7ee59095b3587b6e905e |
| /19 | 8192 | b2551f44f782054780d9d5fe5d4e6b14 |
| /31 | 512 | 5d291f74219487bffd06356d36f3a0e4 |
| /45 | 1024 | f51b0890cacd3e08c42990379cb14d87 |
| /57 | 512 | 9ed505e8c49a74151a1e6abfd3dc70c1 |
| /70 | 512 | 406b70665a5983d1f1682455c669f732 |
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: