Should I block it?
No, this file is 100% safe to run.
Additional versions
(Note, the developer publishes each variation of this file with the same version, but the hashes are unique.)
 PE file structure
|
Show functions |
Import table
kernel32.dll
InterlockedExchange, InterlockedCompareExchange, TerminateProcess, GetCurrentProcess, UnhandledExceptionFilter, SetUnhandledExceptionFilter, IsDebuggerPresent, DisableThreadLibraryCalls, QueryPerformanceCounter, GetTickCount, GetCurrentThreadId, GetCurrentProcessId, GetSystemTimeAsFileTime, Sleep
msvcp90.dll
DllMain
msvcr90.dll
DllMain
Export table
_ID3Field_AddASCII@8
_ID3Field_AddUNICODE@8
_ID3Field_Clear@4
_ID3Field_FromFile@8
_ID3Field_GetASCII@12
_ID3Field_GetASCIIItem@16
_ID3Field_GetBINARY@12
_ID3Field_GetINT@4
_ID3Field_GetNumTextItems@4
_ID3Field_GetUNICODE@12
_ID3Field_GetUNICODEItem@16
_ID3Field_SetASCII@8
_ID3Field_SetBINARY@12
_ID3Field_SetEncoding@8
_ID3Field_SetINT@8
_ID3Field_SetUNICODE@8
_ID3Field_Size@4
_ID3Field_ToFile@8
_ID3Frame_Clear@4
_ID3Frame_Delete@4
_ID3Frame_GetCompression@4
_ID3Frame_GetField@8
_ID3Frame_GetID@4
_ID3Frame_New@0
_ID3Frame_NewID@4
_ID3Frame_SetCompression@8
_ID3Frame_SetID@8
_ID3Tag_AddFrame@8
_ID3Tag_AddFrames@12
_ID3Tag_AttachFrame@8
_ID3Tag_Clear@4
_ID3Tag_CreateConstIterator@4
_ID3Tag_CreateIterator@4
_ID3Tag_Delete@4
_ID3Tag_FindFrameWithASCII@16
_ID3Tag_FindFrameWithID@8
_ID3Tag_FindFrameWithINT@16
_ID3Tag_FindFrameWithUNICODE@16
_ID3Tag_GetMp3HeaderInfo@4
_ID3Tag_HasChanged@4
_ID3Tag_HasTagType@8
_ID3Tag_Link@8
_ID3Tag_LinkWithFlags@12
_ID3Tag_New@0
_ID3Tag_NumFrames@4
_ID3Tag_Parse@12
_ID3Tag_RemoveFrame@8
_ID3Tag_SetExtendedHeader@8
_ID3Tag_SetPadding@8
_ID3Tag_SetUnsync@8
_ID3Tag_Strip@8
_ID3Tag_Update@4
_ID3Tag_UpdateByTagType@8
_ID3TagConstIterator_Delete@4
_ID3TagConstIterator_GetNext@4
_ID3TagIterator_Delete@4
_ID3TagIterator_GetNext@4
libid3tag.dll
| MD5: | decd1eeed9a0d0d559fa788d0fb41825 |
| SHA1: | 7b87d5bd0bb757d171ce07859995fa33064c7c31 |
Overview
libid3tag.dll is loaded as dynamic link library that runs in the context of a process. This is typically installed with the program Music Manager published by Google Inc.
Details
| File name: | libid3tag.dll |
| Typical file path: | C:\Documents and Settings\user\Application data\programs\google\musicmanager\libid3tag.dll |
| Size: | 247.5 KB (253,440 bytes) |
| Digital DNA |
| PE subsystem: | Windows GUI |
| File packed: | No |
| Code language: | Microsoft Visual C++ 9.0 |
| .NET CLR: | No |
More details
Programs
The following program will install this file
“The Google Play Music Manager is a desktop application that allows you to upload your music to the cloud and download your entire library from the cloud to your computer. Once you’ve uploaded songs to Google Play, you can listen to your music anywhere that you have internet access. Upload music from your iTunes library, Windows Media Player library, My Music folder, or folders of your choosing to Google Play. Download any of the songs t...”
Distribution by Windows OS
| OS version | distribution |
| Windows 7 Home Premium |
33.33% |
|
| Microsoft Windows XP |
22.22% |
|
| Windows 7 Ultimate |
16.67% |
|
| Windows 8 Pro |
11.11% |
|
| Windows 7 Professional |
5.56% |
|
| Windows Vista Home Premium |
5.56% |
|
| Windows 8 Pro with Media Center |
5.56% |
|
Distribution by country
United States installs about 83.33% of libid3tag.dll.
Distribution by PC manufacturer
| PC Manufacturer | distribution |
| Dell |
35.29% |
|
| Sony |
11.76% |
|
| ASUS |
11.76% |
|
| Hewlett-Packard |
11.76% |
|
| Toshiba |
11.76% |
|
| Intel |
11.76% |
|
| Acer |
5.88% |
|
