Should I block it?

No, this file is 100% safe to run.

VersionsAdditional versions

6.2.9200.16384 (win8_rtm.120725-1247) 11.69%
6.2.9200.16384 (win8_rtm.120725-1247) 1.30%
6.1.7601.17514 (win7sp1_rtm.101119-1850) 27.27%
6.1.7601.17514 (win7sp1_rtm.101119-1850) 29.87%
6.1.7600.16385 (win7_rtm.090713-1255) 1.30%
6.0.6002.18005 (lh_sp2rtm.090410-1830) 7.79%
5.01.1111 6.49%
5.01.1110 12.99%
5.01.1108 1.30%

Relationships


PE structurePE file structure

Show functions
Import table
advapi32.dll
TraceMessage, RegCloseKey, RegConnectRegistryW, GetLengthSid, IsValidSid, GetTraceEnableFlags, GetTraceEnableLevel, GetTraceLoggerHandle, RegisterTraceGuidsW, UnregisterTraceGuids, SetSecurityDescriptorDacl, AddAccessAllowedAce, InitializeAcl, SetSecurityDescriptorGroup, SetSecurityDescriptorOwner, GetTokenInformation, InitializeSecurityDescriptor, OpenProcessToken, RegDeleteKeyW, RegOpenKeyExW, RegQueryValueExW, RegSetValueExW, RegEnumValueW, AddAccessDeniedAce, LookupAccountNameW, MakeSelfRelativeSD, ReportEventW, RegisterEventSourceW, StartServiceCtrlDispatcherW, RegisterServiceCtrlHandlerW, SetServiceStatus, RegCreateKeyExW
comsvcs.dll
CoLeaveServiceDomain, CoEnterServiceDomain
kernel32.dll
DeleteCriticalSection, InitializeCriticalSection, ResetEvent, SetThreadPriority, LocalFree, GetCurrentProcess, InterlockedDecrement, InterlockedIncrement, LeaveCriticalSection, GetVersion, VirtualQuery, GetModuleHandleW, GetProcAddress, VirtualAlloc, VirtualProtect, ReleaseSemaphore, CreateSemaphoreW, GetSystemInfo, CreateThread, CreateEventW, HeapSetInformation, FormatMessageW, LocalAlloc, GetQueuedCompletionStatus, GetLocalTime, ExpandEnvironmentStringsW, UnhandledExceptionFilter, TerminateProcess, GetSystemTimeAsFileTime, GetCurrentProcessId, GetCurrentThreadId, QueryPerformanceCounter, GetModuleHandleA, SetUnhandledExceptionFilter, OutputDebugStringA, InterlockedCompareExchange, InterlockedExchange, WideCharToMultiByte, MultiByteToWideChar, SetEvent, WaitForSingleObject, ResumeThread, CreateIoCompletionPort, Sleep, PostQueuedCompletionStatus, GetComputerNameW, GetTickCount, GetLastError, EnterCriticalSection, CloseHandle, CancelIo, ExitProcess, SetThreadStackGuarantee
mqrt.dll
MQCloseCursor, MQCloseQueue, MQCreateCursor, MQReceiveMessageByLookupId, MQPathNameToFormatName, MQOpenQueue, MQCreateQueue, MQReceiveMessage
mqsec.dll
MQSec_GetLocalSystemSid
msvcrt.dll
DllMain
ntdll.dll
RtlAllocateHeap, RtlFreeHeap, RtlImageNtHeader
ole32.dll
CLSIDFromProgID, CoUninitialize, CoCreateInstance, CoInitializeEx, CLSIDFromString, CoGetObjectContext, CoInitializeSecurity, OleRun
user32.dll
CharUpperW, CharLowerW

MQTGSVC.exe

Message Queuing Trigger Service by Microsoft

Remove MQTGSVC.exe
Version:   5.01.1110
MD5:   7f955ff3b1bb93376ebe75d5accdc6db
SHA1:   4d48d006c9b8192e14abf7327db13c6bb22aaff5
SHA256:   8cc01adc27747f45ec1198c671eaec4e8e36ade10ba440c7a6aeea37eff66beb
This is a Windows system installed file with Windows File Protection (WFP) enabled.

What is MQTGSVC.exe?

Microsoft Message Queuing or MSMQ is a Message Queue implementation. MSMQ is essentially a messaging protocol that allows applications running on separate servers/processes to communicate in a failsafe manner. A queue is a temporary storage location from which messages can be sent and received reliably, as and when conditions permit.

Overview

mqtgsvc.exe runs as a service under the name Message Queuing-Trigger (MSMQTriggers) with extensive SYSTEM privileges (full administrator access). The assembly utilizes the .NET run-time framework (which is required to be installed on the PC).

DetailsDetails

File name:mqtgsvc.exe
Publisher:Microsoft Corporation
Product name:Message Queuing Trigger Service
Description:Microsoft® Windows® Operating System
Typical file path:C:\Windows\System32\mqtgsvc.exe
File version:5.01.1110
Size:114.5 KB (117,248 bytes)
Digital DNA
File packed:No
Code language:Microsoft Visual C# / Basic .NET
.NET CLR:Yes
.NET NGENed:No
More details

BehaviorsBehaviors

Services
Runs under 'SYSTEM\CurrentControlSet\Services' by the Service Controller (services.exe)
  • 'MSMQTriggers' (Message Queuing-Trigger)
  • MSMQTriggers

ResourcesResource utilization

(Note: statistics below are averages based on a minimum sample size of 200 unique participants)
Averages
 
CPU
Total CPU:0.00126614%
0.028634%
Kernel CPU:0.00033018%
0.013761%
User CPU:0.00093596%
0.014873%
Kernel CPU time:9,391 ms/min
100,923,805ms/min
Context switches:1/sec
284/sec
Memory
Private memory:1.43 MB
21.59 MB
Private (maximum):3.92 MB
Private (minimum):3.91 MB
Non-paged memory:1.43 MB
21.59 MB
Virtual memory:34.02 MB
140.96 MB
Virtual memory (peak):35.89 MB
169.69 MB
Working set:3.91 MB
18.61 MB
Working set (peak):3.92 MB
37.95 MB
Page faults:1,255/min
2,039/min
I/O
I/O read transfer:27 Bytes/sec
1.02 MB/min
I/O read operations:1/sec
343/min
I/O write transfer:0 Bytes/sec
274.99 KB/min
I/O write operations:1/sec
227/min
I/O other transfer:4 Bytes/sec
448.09 KB/min
I/O other operations:1/sec
1,671/min
Resource allocations
Threads:9
12
Handles:123
600
GUI GDI count:4
103
GUI USER count:1
49

BehaviorsProcess properties

Integrety level:Undefined
Platform:32-bit
Command line:C:\Windows\System32\mqtgsvc.exe
Owner:SYSTEM
Windows Service
Service name:MSMQTriggers
Display name:Message Queuing-Trigger
Description:“Bietet eine Regel-basierte Überwachung von Nachrichten an, die in einer Message Queuing-Warteschlange empfangen werden, und, falls die Bedingungen einer Regel erfüllt werden, eine COM-Komponente oder ein eigenständiges ausführbares Programm aufrufen, um die Nachricht zu verarbeiten.”
Type:Win32OwnProcess
Parent process:services.exe (Services and Controller app by Microsoft)

ResourcesThreads

Averages
 
mqtgsvc.exe (main module)
Total CPU:0.00016900%
0.272967%
Kernel CPU:0.00006965%
0.107585%
User CPU:0.00009934%
0.165382%
Memory:128 KB
1.16 MB
ADVAPI32.dll
Total CPU:0.00009934%
Kernel CPU:0.00000000%
User CPU:0.00009934%
Memory:620 KB

Windows OS versionsDistribution by Windows OS

OS versiondistribution
Windows 7 Home Premium 50.82%
Windows 7 Professional 9.84%
Windows 7 Ultimate 9.84%
Windows 8 Pro 9.84%
Windows Vista Home Premium 6.56%
Windows 8 3.28%
Windows 8 Pro with Media Center 3.28%
Windows 7 Starter 3.28%
Windows Vista Home Basic 3.28%

Distribution by countryDistribution by country

United States installs about 54.10% of Message Queuing Trigger Service.

OEM distributionDistribution by PC manufacturer

PC Manufacturerdistribution
ASUS 33.85%
Hewlett-Packard 30.77%
Dell 12.31%
Toshiba 12.31%
Acer 7.69%
Samsung 3.08%
Should I remove It? Clean your PC of unwanted adware, toolbars and bloatware.

Download it for FREE