Should I block it?

No, this file is 100% safe to run.

Relationships


PE structurePE file structure

Show functions
Import table
advapi32.dll
RegSetValueExA, RegQueryValueExA, SetSecurityDescriptorDacl, InitializeSecurityDescriptor, RegisterEventSourceA, DeregisterEventSource, ReportEventA, ReportEventW, RegConnectRegistryA, RegOpenKeyExA, RegCloseKey, RegCreateKeyExA
kernel32.dll
WideCharToMultiByte, MultiByteToWideChar, GetVersionExA, ExitProcess, ReadFile, CreateMutexA, WaitForSingleObject, ReleaseMutex, InitializeCriticalSection, DeleteCriticalSection, EnterCriticalSection, LeaveCriticalSection, LoadLibraryA, SetLastError, WriteFile, RtlUnwind, RaiseException, InterlockedDecrement, InterlockedIncrement, GetCommandLineA, GetVersion, HeapAlloc, TlsSetValue, TlsAlloc, TlsFree, TlsGetValue, SetUnhandledExceptionFilter, TerminateProcess, GetCurrentProcess, SetHandleCount, GetStdHandle, GetFileType, GetStartupInfoA, FreeEnvironmentStringsA, FreeEnvironmentStringsW, GetEnvironmentStrings, GetEnvironmentStringsW, GetModuleHandleA, GetEnvironmentVariableA, HeapDestroy, HeapCreate, VirtualFree, VirtualAlloc, HeapReAlloc, IsBadWritePtr, IsBadCodePtr, LCMapStringA, LCMapStringW, GetCPInfo, GetStringTypeA, GetStringTypeW, GetACP, GetOEMCP, GetProcAddress, SetStdHandle, FindFirstFileA, FindClose, CreateFileA, SetFilePointer, CloseHandle, GetModuleFileNameA, FlushFileBuffers, GetLocalTime, SetEndOfFile, GetFileSize, GetLastError, DeleteFileA, GetCurrentThreadId, GetCurrentProcessId, IsBadReadPtr, GetPrivateProfileStringA, IsBadStringPtrW, HeapFree, IsBadStringPtrA
user32.dll
wsprintfA
Export table
gfilog_deflog_error_1_a
gfilog_deflog_error_1_w
gfilog_deflog_error_2_a
gfilog_deflog_error_2_w
gfilog_deflog_error_3_a
gfilog_deflog_error_3_w
gfilog_deflog_info_1_a
gfilog_deflog_info_1_w
gfilog_deflog_info_2_a
gfilog_deflog_info_2_w
gfilog_deflog_info_3_a
gfilog_deflog_info_3_w
gfilog_deflog_warning_1_a
gfilog_deflog_warning_1_w
gfilog_deflog_warning_2_a
gfilog_deflog_warning_2_w
gfilog_deflog_warning_3_a
gfilog_deflog_warning_3_w
gfilog_log_a
gfilog_log_w
gfilog_setcurlogginglevel
gfilog_start_a
gfilog_start_ex_a
gfilog_start_ex_w
gfilog_start_exv_a
gfilog_start_exv_w
gfilog_start_w
gfilog_stop
gfilog_vlog_a
gfilog_vlog_w

gfi_log.dll

By GFI Software Ltd

Remove gfi_log.dll
Version:   1, 0, 0, 192
MD5:   1b4386278f64a98a5904e5869f9e1889
SHA1:   5bdf146cba3a8e95136e960a44476e57bf32c918

Overview

gfi_log.dll is loaded as dynamic link library that runs in the context of a process. It is installed with a couple of know programs including GFI LANguard Network Security Scanner published by GFI Software and GFI LANguard Network Security Scanner published by GFI Software. This particular version is usually found on Microsoft Windows XP (5.1.2600.196608).

DetailsDetails

File name:gfi_log.dll
Publisher:GFI Software Ltd.
Description:GFI C.E.L.I. API
Typical file path:C:\Program Files\gfi\languard network security scanner 7.0\gfi_log.dll
File version:1, 0, 0, 192
Size:100 KB (102,400 bytes)
Build date:10/25/2005 1:52 PM
Digital DNA
PE subsystem:Windows GUI
File packed:No
.NET CLR:No
More details

ResourcesPrograms

The following programs will install this file
GFI Software
3% remove
GFI LanGuard is an award-winning vulnerability and patch management solution trusted by tens of thousands of businesses to protect millions of computers on their networks. GFI LanGuard acts as your virtual security consultant to provide all three of these essential security tools: patch management, vulnerability assessment and network auditing - in a single easy-to-use console. This solution gives you a complete picture of your network ...

Windows OS versionsDistribution by Windows OS

OS versiondistribution
Microsoft Windows XP 100.00%

OEM distributionDistribution by PC manufacturer

PC Manufacturerdistribution
GIGABYTE 100.00%
Should I remove It? Clean your PC of unwanted adware, toolbars and bloatware.

Download it for FREE