# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"08/26/2019" Time:"00:00:34.7704458" # Scanned Hardware Computer: BaseBoard Manufacturer:"HP" BIOS Mode:"UEFI" BIOS Version/Date:"HP Q83 Ver. 01.07.00 , 04/17/2019" CD or DVD:"Not Available" Embedded Controller Version:"5.57" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.1" Sound Card:"Intel(R) Display Audio" Sound Card:"Conexant ISST Audio" System Manufacturer:"HP" System Model:"HP ProBook 640 G4" System SKU:"2GL98AV" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"25.20.100.6472" - "Intel(R) UHD Graphics 620" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1,00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) UHD Graphics 620" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=UHD+Graphics+620" CoInstallers:"C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igxpco64.dll, CoDeviceInstall" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"12/10/2018 01:00" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"25.20.100.6472" INF:"oem142.inf" INF Section:"iKBLD_w10_DS" Install Date:"Not Available" Installed Drivers:"igdumdim64,igd10iumd64,igd10iumd64,igd12umd64,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_5917&SUBSYS_83D2103C&REV_07\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"60 Hz" Refresh Rate - Minimum:"60 Hz" Resolution:"1366 X 768" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) UHD Graphics Family" - "Memory" Physical Memory (Available):"3,09 GB" Physical Memory (Installed):"8 GB" Physical Memory (Total):"7,85 GB" - "ChannelA0" Capacity:"4 GB" Channel:"Bottom-Slot 1(left)" Configured Clock Speed:"2400 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Noninterleaved" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"M471A5244CB0-CTD" Serial Number:"978FD945" Status:"Not Available" Type:"Not Available" - "ChannelB0" Capacity:"4 GB" Channel:"Bottom-Slot 2(right)" Configured Clock Speed:"2400 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"M471A5244CB0-CTD" Serial Number:"978FD7DF" Status:"Not Available" Type:"Not Available" - "Motherboard" Availability:"Running or Full Power" BIOS:"Q83 Ver. 01.07.00, HPQOEM - 0" Caption:"Motherboard" Chipset:"Not Available" Date:"04/17/2019 02:00" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"HP" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"83D2" Serial Number:"PGWKH00WBAT055" Status:"OK" Version:"KBC Version 05.39.00" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Intel(R) Ethernet Connection (4) I219-V" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Connection (4) I219-V" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(4)+I219+V" CoInstallers:"Not Available" Default IP Gateway:"172.17.240.254" DHCP Enabled:"Yes" DHCP Lease Expires:"08/27/2019 02:02" DHCP Lease Obtained:"08/26/2019 02:02" DHCP Server:"172.17.240.112" Driver:"e1d65x64.sys" Driver Date:"02/05/2018 12:00" Driver Path:"C:\WINDOWS\system32\drivers\e1d65x64.sys" Driver Provider:"Intel" Driver Version:"12.17.10.7" ETrackID:"Not Available" Index:"0000" INF:"oem120.inf" INF Section:"E15D8.10.0.1" Install Date:"Not Available" Installed:"Yes" IP Address:"172.17.242.70" IP Subnet:"255.255.248.0" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"08/26/2019 08:16" Location:"PCI bus 0, device 31, function 6" MAC Address:"B4:B6:86:FC:22:12" Manufacturer:"Intel" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{893D80B2-3B8C-4252-9DF5-62E9721DF401}" Number of VLANs:"0" NVM Version:"Not Available" Part Number:"FFFFFF-0FF" PNP Device ID:"PCI\VEN_8086&DEV_15D8&SUBSYS_83D2103C&REV_21\3&11583659&0&FE" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Connection (4) I219-V" Service Name:"e1dexpress" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)" *PMARPOffload:Protocol ARP Offload:"Enabled (1)" *PMNSOffload:Protocol NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"256 (256)" *RSS:Receive Side Scaling:"Enabled (1)" *RSSProfile:RSS load balancing profile:"ClosestProcessor (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"512 (512)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)" AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)" EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)" EnablePME:Enable PME:"Enabled (1)" ITR:Interrupt Moderation Rate:"Adaptive (65535)" LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)" LogLinkStateEvent:Log Link State Event:"Enabled (51)" MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)" ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Enabled (1)" SipsEnabled:System Idle Power Saver:"Disabled (0)" ULPMode:Ultra Low Power Mode:"Enabled (1)" WaitAutoNegComplete:Wait for Link:"Auto Detect (2)" WakeOnLink:Wake on Link Settings:"Disabled (0)" - "Realtek RTL8822BE 802.11ac PCIe Adapter" Access Point: Authentication: Availability:"Running or Full Power" Caption:"Realtek RTL8822BE 802.11ac PCIe Adapter" Channel: Cipher: CoInstallers:"Not Available" Connection Mode: Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"rtwlane.sys" Driver Date:"06/04/2019 12:00" Driver Path:"C:\WINDOWS\system32\drivers\rtwlane.sys" Driver Provider:"Realtek Semiconductor Corp." Driver Version:"2024.0.8.104" Index:"0002" INF:"oem113.inf" INF Section:"HP8822be.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"08/26/2019 08:16" Location:"PCI bus 1, device 0, function 0" MAC Address:"FC:01:7C:31:94:5B" Manufacturer:"Realtek Semiconductor Corp." Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{AE53EFA0-1D2A-4023-B9F8-E8B539BEE5E2}" Network Name:"Wi-Fi" Network Type: Number of VLANs:"0" PNP Device ID:"PCI\VEN_10EC&DEV_B822&SUBSYS_831B103C&REV_00\00E04CFFFEB8220100" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Realtek RTL8822BE 802.11ac PCIe Adapter" Profile: Radio Type: Receive Rate: Service Name:"RTWlanE" Signal Strength: State:"disconnected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AH_BcnIntv:Beacon Interval:"100 (100)" ARPOffloadEnable:ARP offload for WoWLAN:"Enabled (1)" b40Intolerant:Fat Channel Intolerant:"Disabled (0)" BW40MHzFor2G:802.11n channel width for 2.4GHz:"Auto (1)" BW40MHzFor5G:802.11n channel width for 5.2GHz:"Auto (1)" Dot11dEnable:802.11d:"Enabled (1)" GTKOffloadEnable:GTK rekeying for WoWLAN:"Enabled (1)" HTMode:HT mode:"VHT mode (4)" MultiChannelFcsMode:Multi-Channel Concurrent:"Enabled + Hotspot (28)" NSOffloadEnable:NS offload for WoWLAN:"Enabled (1)" PreambleMode:Preamble Mode:"Short & long (2)" PreferBand:Preferred Band:"1. No Preference (0)" ProtectionMode:Mixed mode protection:"CTS-to-self Enabled (1)" RegROAMSensitiveLevel:Roaming Aggressiveness:"4. Medium (75)" TxPwrLevel:Transmit power:"5. Highest (0)" WakeOnDisconnect:Sleep on WoWLAN disconnect:"Disabled (1)" WirelessMode:Wireless Mode:"6. 802.11a/b/g (7)" WoWLANS5Support:Realtek S5 WoWLAN:"Enabled (1)" - "TAP-Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-Windows Adapter V9" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tap0901.sys" Driver Date:"04/21/2016 12:00" Driver Path:"C:\WINDOWS\system32\drivers\tap0901.sys" Driver Provider:"TAP-Windows Provider V9" Driver Version:"9.0.0.21" Index:"0007" INF:"oem126.inf" INF Section:"tap0901.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"08/26/2019 08:16" Location:"Not Available" MAC Address:"00:FF:81:F1:DF:D2" Manufacturer:"TAP-Windows Provider V9" Media Type: Net Connection ID:"Ethernet 2" NetCfgInstanceId:"{81F1DFD2-076B-4452-9F5A-CC58FB7E7906}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"TAP-Windows Adapter V9" Service Name:"tap0901" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.6" Boot Device:"\Device\HarddiskVolume1" Internet Browser:"Internet Explorer,11.3085" Locale:"Italy" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Enterprise 2016 LTSB" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"1,25 GB" Physical Memory (Available):"3,09 GB" Physical Memory (Installed):"8 GB" Physical Memory (Total):"7,85 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.14393 Build 14393" Virtual Memory (Available):"1,93 GB" Virtual Memory (Total):"9,10 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [05/06/2019]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [05/06/2019]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [05/06/2019]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [05/06/2019]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544655:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [05/06/2019]" KB2544655:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [05/06/2019]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB4093137:"Update [7/18/2018]" KB4132216:"Update [7/18/2018]" KB4346087:"Update [6/25/2019]" KB4465659:"Security Update [11/22/2018]" KB4485447:"Security Update [2/21/2019]" KB4498947:"Security Update [5/27/2019]" KB4503308:"Security Update [6/24/2019]" KB4503537:"Security Update [6/24/2019]" KB4507460:"Security Update [7/25/2019]" KB4509091:"Security Update [7/25/2019]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [05/06/2019]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [05/06/2019]" - "Processor" - "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 142 Stepping 10" - "Chipset Name":"Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i5+8250U+CPU+" CPU Speed:"1,6 GHz" Current Voltage:"7. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.14393.2969" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"4 x 256 KB" Level 2 Cache:"4 x 1024 KB" Level 3 Cache:"6 MB" Load:"7%" Manufacturer:"GenuineIntel" Model:"142" Name:"Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806EA" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"10" Version:"Not Available" - "Storage" - "KXG50ZNV256G TOSHIBA" Capablities:"Random Access, Supports Writing" Caption:"KXG50ZNV256G TOSHIBA" Cylinder - Total:"31130" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00" Driver Version:"10.0.14393.1613" Error Code:"Device is working properly" Firmware Revision:"AAHA4102" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"KXG50ZNV256G TOSHIBA" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_KXG50ZNV256G_TOS\5&E9A2C86&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"500103450" Serial Number:"0000_0000_0000_0010_0008_0D05_0009_F0FC." Size:"238,47 GB" Size – Available:"148,20 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"7938150" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Windows" Serial Number:"D203ECAF" Size:"235,475582122803 GB" Size – Available:"148,201698303223 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 10 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 9 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 8 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 7 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 6 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 4 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3268905942-3027921619-2595750967-1466914902-3854609825-3774988475-2641930636). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AA65DD7C-83AC-48C0-A6FD-9B61FEBF8800} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {83F5BB7A-6790-11D3-9641-0004AC962A49} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- WLAN Extensibility Module has stopped unexpectedly. Module Path: C:\WINDOWS\system32\Rtlihvs.dll ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3340370847-1338158715-3172123212-1369934592-386104730-627878784-801724534). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated with the following service-specific error: The class is configured to run as a security id different from the caller ------------------------------------------------------------------- The BITS service failed to start. Error 0x80004015. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AA65DD7C-83AC-48C0-A6FD-9B61FEBF8800} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AA65DD7C-83AC-48C0-A6FD-9B61FEBF8800} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AA65DD7C-83AC-48C0-A6FD-9B61FEBF8800} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AA65DD7C-83AC-48C0-A6FD-9B61FEBF8800} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffffa68c57361040, 0xffffbb801a376900). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6f8887ea-1600-483d-ab01-d3b27821df17. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 09:01:08 on ‎29/‎07/‎2019 was unexpected. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2518486777-291500833-2728231582-3756461861-2427241484-155661210-2983208823). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2518486777-291500833-2728231582-3756461861-2427241484-155661210-2983208823). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-184933371-615121162-2526824692-203580010-2537701436-3900376233-1395319050). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-184933371-615121162-2526824692-203580010-2537701436-3900376233-1395319050). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Service service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description. ------------------------------------------------------------------- The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server srvitwgr1dc1$. The target name used was RPC/SRVITWGR1DC2.wamgroup.local. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (WAMGROUP.LOCAL) is different from the client domain (WAMGROUP.LOCAL), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server. ------------------------------------------------------------------- The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server srvitwgr1dc1$. The target name used was cifs/SRVITWGR1DC2.wamgroup.local. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (WAMGROUP.LOCAL) is different from the client domain (WAMGROUP.LOCAL), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated with the following service-specific error: The class is configured to run as a security id different from the caller ------------------------------------------------------------------- The BITS service failed to start. Error 0x80004015. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-1796584566-1979181429-1823634605-227057999-2823052601-1844622377-4149743249). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-1796584566-1979181429-1823634605-227057999-2823052601-1844622377-4149743249). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {FE98DDE9-E725-4492-BAD6-0E9B0C47744F} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {FE98DDE9-E725-4492-BAD6-0E9B0C47744F} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-788023048-3859299433-1585907159-1905911541-2810610705-664398957-3793704635). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-788023048-3859299433-1585907159-1905911541-2810610705-664398957-3793704635). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.wamgroup.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.wamgroup.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Network Inspection Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WdNisSvc service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (00:22:f7:17:b3:a9) failed. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {3185A766-B338-11E4-A71E-12E3F512A338} and APPID {7006698D-2974-4091-A424-85DD0B909E23} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- File [...\Program Files (x86)\HP Universal Camera Driver\SPUVCbv10.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1e3e3f3]). ------------------------------------------------------------------- File [...:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv1.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1e36e76]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1e2d1c5]). ------------------------------------------------------------------- File [...m Files (x86)\HP Universal Camera Driver\SPITProvider_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1e14a20]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPI6708.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1dfe99c]). ------------------------------------------------------------------- File [... Files (x86)\HP Universal Camera Driver\SPITProvider2_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1dd770d]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPI66E8.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1dbef45]). ------------------------------------------------------------------- File [...am Files (x86)\HP Universal Camera Driver\CoInstaller_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1d97c9a]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\CoI66C7.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1d7a6aa]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\SysWOW64\VCamPPage.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254a1d272ca]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\SysWOW64\VCamPPage.dll" by process ? . ------------------------------------------------------------------- File [...\Device\HarddiskVolume3\WINDOWS\System32\config\DRIVERS]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d53254742130ae]). ------------------------------------------------------------------- File [...\Device\HarddiskVolume3\WINDOWS\SysWOW64\VCa91D8.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d532545a494c1f]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\HP Universal Camera Driver\VCa91B6.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d532545a463b51]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\VCa91B7.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d532545a43efde]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\system32\VCamPPage_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d532545a410787]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\system32\VCamPPage_x64.dll" by process ? . ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the RtkBtManServ service to connect. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the Realtek Bluetooth Device Manager Service service to connect. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {3185A766-B338-11E4-A71E-12E3F512A338} and APPID {7006698D-2974-4091-A424-85DD0B909E23} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\riccardo.solieri\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. This may be transient. Group Policy settings, including computer configuration, will not be enforced for this computer. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\wamgroup.local\sysvol\wamgroup.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The digitally signed Privilege Attribute Certificate (PAC) that contains the authorization information for client PCLITWGR1439$ in realm WAMGROUP.LOCAL could not be validated. This error is usually caused by domain trust failures; Contact your system administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server CortanaUI.AppXtpp90jhw9p0njjb85kvhxpppgrqfp117.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffffd40a6de53040, 0xfffff8034ebca900). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b876af03-7dd6-4f88-9ebb-5bbccc6580cd. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 13:13:44 on ‎18/‎06/‎2019 was unexpected. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WlanSvc service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WlanSvc service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WlanSvc service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. ------------------------------------------------------------------- WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter. Code: 2 0xDEADDEED 0xEEEC ------------------------------------------------------------------- WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter. Code: 1 0xC 0x4 ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {3185A766-B338-11E4-A71E-12E3F512A338} and APPID {7006698D-2974-4091-A424-85DD0B909E23} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server CortanaUI.AppXd4tad4d57t4wtdbnnmb8v2xtzym8c1n8.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2744356255-1482552772-271587534-1730681832-843364481-1754330381-4070872504). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2744356255-1482552772-271587534-1730681832-843364481-1754330381-4070872504). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 17:12:05 on ‎15/‎05/‎2019 was unexpected. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 420 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 419 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 418 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 417 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 416 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 415 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 414 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 413 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 412 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 411 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 410 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 409 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 408 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 407 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 406 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 405 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 404 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 403 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 402 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 401 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 400 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 399 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 398 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 397 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 396 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 395 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 394 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 393 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 392 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 391 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 390 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 389 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 388 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 387 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 386 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 385 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 384 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 383 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 382 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 381 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 380 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 379 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 378 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 377 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 376 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 375 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 374 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 373 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 372 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 371 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 370 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 369 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 368 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 367 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 366 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 365 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 364 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 363 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 362 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 361 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 360 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 359 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 358 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 357 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 356 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 355 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 354 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 353 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 352 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 351 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 350 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 349 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 348 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 347 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 346 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 345 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 344 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 343 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 342 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 341 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 340 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 339 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 338 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 337 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 336 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 335 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 334 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 333 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 332 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 331 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 330 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 329 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 328 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 327 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 326 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 325 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 324 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 323 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 322 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 321 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 320 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 319 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 318 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 317 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 316 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 315 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 314 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 313 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 312 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 311 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 310 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 309 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 308 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 307 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 306 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 305 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 304 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 303 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 302 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 301 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 300 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 299 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 298 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 297 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 296 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 295 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 294 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 293 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 292 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 291 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 290 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 289 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 288 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 287 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 286 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 285 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 284 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 283 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 282 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 281 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 280 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 279 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 278 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 277 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 276 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 275 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 274 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 273 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 272 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 271 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 270 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 269 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 268 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 267 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 266 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 265 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 264 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 263 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 262 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 261 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 260 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 259 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 258 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 257 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 256 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 255 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 254 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 253 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 252 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 251 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 250 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 249 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 248 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 247 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 246 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 245 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 244 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 243 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 242 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 241 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 240 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 239 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 238 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 237 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 236 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 235 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 234 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 233 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 232 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 231 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 230 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 229 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 228 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 227 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 226 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 225 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 224 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 223 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 222 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 221 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 220 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 219 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 218 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 217 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 216 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 215 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 214 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 213 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 212 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 211 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 210 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 209 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 208 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 207 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 206 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 205 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 204 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 203 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 202 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 201 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 200 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 199 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 198 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 197 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 196 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 195 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 194 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 193 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 192 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 191 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 190 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 189 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 188 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 187 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 186 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 185 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 184 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 183 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 182 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 181 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 180 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 179 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 178 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 177 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 176 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 175 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 174 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 173 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 172 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 171 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 170 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 169 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 168 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 167 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 166 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 165 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 164 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 163 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 162 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 161 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 160 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 159 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 158 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 157 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 156 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 155 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 154 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 153 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 152 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 151 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 150 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 149 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 148 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 147 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 146 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 145 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 144 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 143 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 142 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 141 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 140 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 139 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 138 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 137 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 136 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 135 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 134 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 133 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 132 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 131 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 130 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 129 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 128 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 127 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 126 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 125 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 124 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 123 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 122 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 121 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 120 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 119 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 118 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 117 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 116 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 115 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 114 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 113 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 112 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 111 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 110 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 109 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 108 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 107 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 106 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 105 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 104 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 103 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 102 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 101 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 100 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 99 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 98 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 97 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 96 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 95 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 94 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 93 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 92 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 91 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 90 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 89 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 88 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 87 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 86 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 85 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 84 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 83 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 82 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 81 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 80 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 79 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 78 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 77 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 76 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 75 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 74 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 73 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 72 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 71 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 70 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 69 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 68 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 67 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 66 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 65 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 64 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 63 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 62 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 61 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 60 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 59 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 58 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 57 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 56 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 55 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 54 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 53 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 52 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 51 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 50 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 49 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 48 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 47 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 46 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 45 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 44 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 43 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 42 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 41 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 40 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 39 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 38 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 37 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 36 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 35 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 34 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 33 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 32 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 31 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 30 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 29 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 28 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 27 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 26 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 25 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 24 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 23 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 22 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 21 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 20 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 19 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 18 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 17 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 16 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 15 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 14 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 13 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 11 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 10 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 9 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 8 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 7 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 6 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 4 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Sophos Message Router service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter. Code: 8 0x0 0x0 ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter. Code: 2 0xDEADDEED 0xEEEC ------------------------------------------------------------------- WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter. Code: 1 0xC 0x4 ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3062543687-3557949439-2772864910-4071932636-2064074283-205886820-778295361). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3062543687-3557949439-2772864910-4071932636-2064074283-205886820-778295361). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3610964089-347037983-2611062729-3681798049-2629947890-2427055950-3739571504). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3610964089-347037983-2611062729-3681798049-2629947890-2427055950-3739571504). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Defender Service service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.242.72. The computer with the IP address 172.17.243.15 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2548241515-2724224360-2588847106-1064544128-4121546831-3352736422-2012298651). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-2548241515-2724224360-2588847106-1064544128-4121546831-3352736422-2012298651). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.243.41. The computer with the IP address 172.17.242.26 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Crash dump initialization failed! ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.243.27. The computer with the IP address 172.17.243.194 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR3. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.242.176. The computer with the IP address 172.17.242.17 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.243.30. The computer with the IP address 172.17.243.130 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\riccardo.solieri\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Crash dump initialization failed! ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\riccardo.solieri\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost. ------------------------------------------------------------------- The Sophos Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain WAMGROUP due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Startup script failed. GPO Name : TBR-LanSweeper GPO File System Path : \\wamgroup.local\SysVol\wamgroup.local\Policies\{7339BD86-CFE6-4703-A11B-4E9058C17777}\Machine Script Name: \\wamgroup.local\netlogon\gpo_files\LSclient.exe ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- File [...\Program Files (x86)\HP Universal Camera Driver\SPUVCbv10.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2dbb2f1a]). ------------------------------------------------------------------- File [...:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv1.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db8ccaf]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db8ccaf]). ------------------------------------------------------------------- File [...m Files (x86)\HP Universal Camera Driver\SPITProvider_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db66a3f]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPI7DA8.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db66a3f]). ------------------------------------------------------------------- File [... Files (x86)\HP Universal Camera Driver\SPITProvider2_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db40812]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPI7D97.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2db1a6fd]). ------------------------------------------------------------------- File [...am Files (x86)\HP Universal Camera Driver\CoInstaller_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2daf430f]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\CoI7D77.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2dace09e]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\SysWOW64\VCamPPage.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4ac2daa89ab]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\SysWOW64\VCamPPage.dll" by process ? . ------------------------------------------------------------------- File [...\Device\HarddiskVolume3\WINDOWS\System32\config\DRIVERS]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4abf4cda46f]). ------------------------------------------------------------------- File [...\Device\HarddiskVolume3\WINDOWS\SysWOW64\VCaA887.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4abe61fbe52]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\HP Universal Camera Driver\VCaA866.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4abe61d5c14]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\VCaA867.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4abe61af9d1]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\system32\VCamPPage_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4abe618a17d]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\system32\VCamPPage_x64.dll" by process ? . ------------------------------------------------------------------- The Intel(R) Audio Service service terminated with the following service-specific error: The operation completed successfully. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The name "WAMGROUP :1d" could not be registered on the interface with IP address 172.17.243.214. The computer with the IP address 172.17.243.67 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The Interactive Services Detection service terminated with the following error: Incorrect function. ------------------------------------------------------------------- The Interactive Services Detection service terminated with the following error: Incorrect function. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {260EB9DE-5CBE-4BFF-A99A-3710AF55BF1E} and APPID {260EB9DE-5CBE-4BFF-A99A-3710AF55BF1E} to the user WAMGROUP\riccardo.solieri SID (S-1-5-21-1987855820-843622220-3211469290-46274) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.14393.2068_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Intel(R) Audio Service service terminated with the following service-specific error: The operation completed successfully. ------------------------------------------------------------------- The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user WAMGROUP\adminpv SID (S-1-5-21-1987855820-843622220-3211469290-43286) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- File [...\Program Files (x86)\HP Universal Camera Driver\SPUVCbv10.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466aee56a]). ------------------------------------------------------------------- File [...:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv1.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466aee56a]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\HP Universal Camera Driver\SPUVCbv.inf]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466aee56a]). ------------------------------------------------------------------- File [...m Files (x86)\HP Universal Camera Driver\SPITProvider_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466ac830d]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPIC6E3.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466aa2094]). ------------------------------------------------------------------- File [... Files (x86)\HP Universal Camera Driver\SPITProvider2_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466a7be31]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\SPIC6C2.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466a55bc9]). ------------------------------------------------------------------- File [...am Files (x86)\HP Universal Camera Driver\CoInstaller_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48466a096ed]). ------------------------------------------------------------------- File [...e3\Program Files (x86)\HP Universal Camera Driver\CoIC6A2.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484669e3479]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\SysWOW64\VCamPPage.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484669bd21c]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\SysWOW64\VCamPPage.dll" by process ? . ------------------------------------------------------------------- File [...me3\Program Files (x86)\Realtek\PCIE Wireless LAN\RtlAC70.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48462a312be]). ------------------------------------------------------------------- File [...:\Program Files (x86)\Realtek\PCIE Wireless LAN\rtl8723de.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484629e4de2]). ------------------------------------------------------------------- File [...me3\Program Files (x86)\Realtek\PCIE Wireless LAN\rtlAC60.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484629e4de2]). ------------------------------------------------------------------- File [...\C:\Program Files (x86)\Realtek\PCIE Wireless LAN\install.exe]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484629988fb]). ------------------------------------------------------------------- File [...me3\Program Files (x86)\Realtek\PCIE Wireless LAN\insAC40.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e48462972698]). ------------------------------------------------------------------- File [...ogram Files (x86)\Realtek\PCIE Wireless LAN\RtlDisableICS.exe]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484628b3c2f]). ------------------------------------------------------------------- File [...me3\Program Files (x86)\Realtek\PCIE Wireless LAN\RtlAB25.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e484626c3b11]). ------------------------------------------------------------------- File [...C:\Program Files (x86)\Realtek\PCIE Wireless LAN\AudioLib.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4846269d887]). ------------------------------------------------------------------- File [...me3\Program Files (x86)\Realtek\PCIE Wireless LAN\AudAB05.tmp]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4846267773b]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\SysWOW64\ISSRemoveSP.exe]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4846260504c]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\SysWOW64\ISSRemoveSP.exe" by process ? . ------------------------------------------------------------------- File [...401ef5f0000c421e822\5f1b0a1f84e4d40189600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f0a1b5f]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\5f1b0a1f84e4d40188600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f0a1b5f]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\5f1b0a1f84e4d40187600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f0a1b5f]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\81ba071f84e4d40186600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f0a1b5f]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\81ba071f84e4d40185600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f07ba81]). ------------------------------------------------------------------- File [...\??\C:\WINDOWS\system32\VCamPPage_x64.dll]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f07ba81]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\81ba071f84e4d40184600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f07ba81]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\81ba071f84e4d40183600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f07ba81]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\81ba071f84e4d40182600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f07ba81]). ------------------------------------------------------------------- File [...401ef5f0000c421e822\2b58051f84e4d40181600000c421e822_manifest]'s scan succeeded following a timeout/busy condition - it is being logged in case it contributed to that condition. Process ?, (start check timestamp [ 1d4e4841f05582b]). ------------------------------------------------------------------- Communication error between on-access driver and service for a modification of file "\Device\HarddiskVolume3\WINDOWS\system32\VCamPPage_x64.dll" by process ? . ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the BTDevManager service to connect. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {260EB9DE-5CBE-4BFF-A99A-3710AF55BF1E} and APPID {260EB9DE-5CBE-4BFF-A99A-3710AF55BF1E} to the user WAMGROUP\adminpv SID (S-1-5-21-1987855820-843622220-3211469290-43286) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.14393.2068_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Network Connectivity Assistant service depends on the IP Helper service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The IP Helper service terminated with the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The IntelAudioService service terminated with the following service-specific error: The operation completed successfully. ------------------------------------------------------------------- The iphlpsvc service terminated with the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The Spooler service terminated with the following error: Ran out of memory ------------------------------------------------------------------- The netprofm service terminated with the following error: The device is not ready. ------------------------------------------------------------------- Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 14. ------------------------------------------------------------------- Not Available ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 8/26/2019, 16:01:49 Machine name: PCLITWGR1439 Machine Id: {25FEDDCB-226F-4A1F-A2AF-D09B420CD439} Operating System: Windows 10 Enterprise 2016 LTSB 64-bit (10.0, Build 14393) (14393.rs1_release.190703-1816) Language: Italian (Regional Setting: Italian) System Manufacturer: HP System Model: HP ProBook 640 G4 BIOS: Q83 Ver. 01.07.00 Processor: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 CPUs), ~1.8GHz Memory: 8192MB RAM Available OS Memory: 8036MB RAM Page File: 7356MB used, 1958MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.14393.2457 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) UHD Graphics 620 Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device Device Key: Enum\PCI\VEN_8086&DEV_5917&SUBSYS_83D2103C&REV_07 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 4145 MB Dedicated Memory: 128 MB Shared Memory: 4017 MB Current Mode: 1366 x 768 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: CMN14C3 Native Mode: 1366 x 768(p) (60.003Hz) Output Type: Internal Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12umd64.dll Driver File Version: 25.20.0100.6472 (English) Driver Version: 25.20.100.6472 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.1 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Hybrid Graphics GPU: Integrated Power P-states: Not Supported Driver Attributes: Final Retail Driver Date/Size: 10/12/2018 02:00:00, 2587528 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-1A57-11CF-C46A-B6A3BCC2D435} Vendor ID: 0x8086 Device ID: 0x5917 SubSys ID: 0x83D2103C Revision ID: 0x0007 Driver Strong Name: oem142.inf:5f63e534f33a69cc:iKBLD_w10_DS:25.20.100.6472:pci\ven_8086&dev_5917&subsys_83d2103c Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported Card name: Intel(R) UHD Graphics 620 Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device Device Key: Enum\PCI\VEN_8086&DEV_5917&SUBSYS_83D2103C&REV_07 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 4145 MB Dedicated Memory: 128 MB Shared Memory: 4017 MB Current Mode: 1600 x 900 (32 bit) (60Hz) Monitor Name: Dell E2011H (Analog - VGA) Monitor Model: DELL E2011H Monitor Id: DEL406B Native Mode: 1600 x 900(p) (59.978Hz) Output Type: Displayport External Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12umd64.dll Driver File Version: 25.20.0100.6472 (English) Driver Version: 25.20.100.6472 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.1 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Hybrid Graphics GPU: Integrated Power P-states: Not Supported Driver Attributes: Final Retail Driver Date/Size: 10/12/2018 02:00:00, 2587528 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-1A57-11CF-C46A-B6A3BCC2D435} Vendor ID: 0x8086 Device ID: 0x5917 SubSys ID: 0x83D2103C Revision ID: 0x0007 Driver Strong Name: oem142.inf:5f63e534f33a69cc:iKBLD_w10_DS:25.20.100.6472:pci\ven_8086&dev_5917&subsys_83d2103c Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported ------------- Sound Devices ------------- Description: Speakers (Conexant ISST Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_14F1&DEV_2008&SUBSYS_103C83D3&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: CHDRT64ISST.sys Driver Version: 9.00.0232.0001 (Italian) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 27/01/2019 00:00:00, 2409848 bytes Other Files: Driver Provider: Conexant HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Internal Microphone (Conexant ISST Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: CHDRT64ISST.sys Driver Version: 9.00.0232.0001 (Italian) Driver Attributes: Final Retail Date and Size: 3/27/2019 16:37:21, 2409848 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: HP HD Camera Location: Front SymbolicLink: \\?\usb#vid_04ca&pid_706d&mi_00#6&273b10e5&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Manufacturer: Liteon HardwareID: USB\VID_04CA&PID_706D&REV_0006&MI_00,USB\VID_04CA&PID_706D&MI_00 DriverDesc: HP HD Camera DriverProvider: SunplusIT DriverVersion: 3.7.8.5 DriverDateEnglish: 5/11/2018 00:00:00 DriverDateLocalized: 11/05/2018 00:00:00 Service: SPUVCbv Class: Image DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: HP HD Camera Parent: USB\VID_04CA&PID_706D\5&15165c90&0&9 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: n/a Stack: \Driver\ksthunk,\Driver\SPUVCbv,\Driver\ACPI,\Driver\usbccgp ContainerCategory: Imaging.Webcam ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: HP Business Slim Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x03F0, 0x304A FF Driver: n/a Device Name: HP Business Slim Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x03F0, 0x304A FF Driver: n/a Device Name: HP Business Slim Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x03F0, 0x304A FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x8305 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x8305 FF Driver: n/a Device Name: HP Wireless Button Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0001, 0x0001 FF Driver: n/a Device Name: Wireless Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x248A, 0x8514 FF Driver: n/a Device Name: Wireless Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x248A, 0x8514 FF Driver: n/a Device Name: Wireless Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x248A, 0x8514 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (xHCI) | Vendor/Product ID: 0x8086, 0x9D2F | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 6/13/2019 07:15:46, 536528 bytes | +-+ Generic USB Hub | | Vendor/Product ID: 0x0424, 0x2134 | | Location: Port_#0004.Hub_#0001 | | Matching Device ID: USB\USB20_HUB | | Service: USBHUB3 | | Driver: USBHUB3.SYS, 6/13/2019 07:15:46, 536528 bytes | | | +-+ USB Composite Device | | | Vendor/Product ID: 0x03F0, 0x304A | | | Location: Port_#0001.Hub_#0003 | | | Matching Device ID: USB\COMPOSITE | | | Service: usbccgp | | | Driver: usbccgp.sys, 7/18/2018 16:18:17, 169304 bytes | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x03F0, 0x304A | | | | Location: 0000.0014.0000.004.001.000.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 7/18/2018 16:18:16, 38400 bytes | | | | Driver: hidclass.sys, 3/6/2019 08:08:54, 156672 bytes | | | | Driver: hidparse.sys, 3/6/2019 08:10:34, 40960 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x03F0, 0x304A | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 7/18/2018 16:18:16, 39424 bytes | | | | | Driver: kbdclass.sys, 7/16/2016 13:41:54, 62304 bytes | | +-+ USB Composite Device | | Vendor/Product ID: 0x248A, 0x8514 | | Location: Port_#0002.Hub_#0001 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 7/18/2018 16:18:17, 169304 bytes | | | +-+ USB Input Device | | | Vendor/Product ID: 0x248A, 0x8514 | | | Location: 0000.0014.0000.002.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 7/18/2018 16:18:16, 38400 bytes | | | Driver: hidclass.sys, 3/6/2019 08:08:54, 156672 bytes | | | Driver: hidparse.sys, 3/6/2019 08:10:34, 40960 bytes | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x248A, 0x8514 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 7/16/2016 13:41:54, 32256 bytes | | | | Driver: mouclass.sys, 7/16/2016 13:41:54, 59232 bytes | | | | +-+ USB Input Device | | | Vendor/Product ID: 0x248A, 0x8514 | | | Location: 0000.0014.0000.002.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 7/18/2018 16:18:16, 38400 bytes | | | Driver: hidclass.sys, 3/6/2019 08:08:54, 156672 bytes | | | Driver: hidparse.sys, 3/6/2019 08:10:34, 40960 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0x248A, 0x8514 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 7/18/2018 16:18:16, 39424 bytes | | | | Driver: kbdclass.sys, 7/16/2016 13:41:54, 62304 bytes | | +-+ USB Input Device | | Vendor/Product ID: 0x03F0, 0x154A | | Location: Port_#0001.Hub_#0001 | | Matching Device ID: USB\Class_03&SubClass_01 | | Service: HidUsb | | Driver: hidusb.sys, 7/18/2018 16:18:16, 38400 bytes | | Driver: hidclass.sys, 3/6/2019 08:08:54, 156672 bytes | | Driver: hidparse.sys, 3/6/2019 08:10:34, 40960 bytes | | | +-+ HID-compliant mouse | | | Vendor/Product ID: 0x03F0, 0x154A | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | Service: mouhid | | | Driver: mouhid.sys, 7/16/2016 13:41:54, 32256 bytes | | | Driver: mouclass.sys, 7/16/2016 13:41:54, 59232 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 7/16/2016 13:41:54, 114176 bytes | Driver: kbdclass.sys, 7/16/2016 13:41:54, 62304 bytes | + Synaptics Pointing Device | Matching Device ID: ACPI\SYN3069 | Upper Filters: SynTP | Service: i8042prt | Driver: SynTP.sys, 3/27/2019 16:49:06, 760872 bytes | Driver: SynTPEnh.exe, 3/27/2019 16:49:06, 4490272 bytes | Driver: SynTPRes.dll, 3/27/2019 16:49:06, 19815464 bytes | Driver: SynTPAPI.dll, 3/27/2019 16:49:06, 282152 bytes | Driver: SynCOM.dll, 3/27/2019 16:49:06, 820776 bytes | Driver: SynTPEnhService.exe, 3/27/2019 16:49:06, 352808 bytes | Driver: mouclass.sys, 7/16/2016 13:41:54, 59232 bytes | Driver: i8042prt.sys, 7/16/2016 13:41:54, 114176 bytes | + Synaptics HID ClickPad | Vendor/Product ID: 0x06CB, 0x0000 | Matching Device ID: HID\SYNA3069&Col01 | Upper Filters: SynTP | Service: mouhid | Driver: SynTP.sys, 3/27/2019 16:49:06, 760872 bytes | Driver: SynTPEnh.exe, 3/27/2019 16:49:06, 4490272 bytes | Driver: SynTPRes.dll, 3/27/2019 16:49:06, 19815464 bytes | Driver: SynTPAPI.dll, 3/27/2019 16:49:06, 282152 bytes | Driver: SynCOM.dll, 3/27/2019 16:49:06, 820776 bytes | Driver: SynTPEnhService.exe, 3/27/2019 16:49:06, 352808 bytes | Driver: mouhid.sys, 7/16/2016 13:41:54, 32256 bytes | Driver: mouclass.sys, 7/16/2016 13:41:54, 59232 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 151.8 GB Total Space: 241.1 GB File System: NTFS Model: KXG50ZNV256G TOSHIBA -------------- System Devices -------------- Name: Mobile Intel(R) Processor Family I/O SMBUS - 9D23 Device ID: PCI\VEN_8086&DEV_9D23&SUBSYS_83D2103C&REV_21\3&11583659&0&FC Driver: n/a Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) Device ID: PCI\VEN_8086&DEV_9D2F&SUBSYS_83D2103C&REV_21\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.14393.3053 (English), 6/13/2019 07:16:01, 381688 bytes Name: Intel(R) Dynamic Platform and Thermal Framework Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_83D2103C&REV_08\3&11583659&0&20 Driver: C:\WINDOWS\system32\DRIVERS\esif_lf.sys, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 403440 bytes Driver: C:\WINDOWS\system32\DRIVERS\dptf_cpu.sys, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 75248 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_uf.exe, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1883112 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\esif_umdf2.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 870048 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\Dptf.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 2335184 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyRfim.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 873128 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyActive.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 892880 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyActive2.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1073616 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyAdaptivePerformance.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1486800 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyCritical.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 832168 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyConfigTdp.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 842704 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPassive.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1081512 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPassive2.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1125024 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPid.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1060000 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPowerBoss.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1752224 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyVirtualSensor.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1038496 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPowerShare.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 1035432 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_wwan.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 174752 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_wifi.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 65696 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_nvme.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 89760 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_battery.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 71328 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\dptf_helper.exe, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 408040 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_cmp.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 134816 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_ws.dll, 8.05.10103.7263 (English), 7/3/2019 17:41:21, 226984 bytes Driver: C:\WINDOWS\ServiceProfiles\LocalService\AppData\Local\Intel\DPTF\dsp.dv, 7/3/2019 17:41:21, 665468 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_9D71&SUBSYS_83D2103C&REV_21\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 9.21.0000.3063 (English), 11/5/2017 19:09:56, 239696 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.14393.0000 (English), 7/16/2016 13:41:52, 97280 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.14393.0000 (English), 7/16/2016 13:41:52, 366592 bytes Name: Intel(R) Serial IO I2C Host Controller - 9D60 Device ID: PCI\VEN_8086&DEV_9D60&SUBSYS_83D2103C&REV_21\3&11583659&0&A8 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2_I2C.sys, 30.100.1823.0001 (English), 6/11/2018 00:23:28, 191024 bytes Name: Intel(R) Host Bridge/DRAM Registers - 5914 Device ID: PCI\VEN_8086&DEV_5914&SUBSYS_83D2103C&REV_08\3&11583659&0&00 Driver: n/a Name: Mobile Intel(R) Processor Family I/O PMC - 9D21 Device ID: PCI\VEN_8086&DEV_9D21&SUBSYS_83D2103C&REV_21\3&11583659&0&FA Driver: n/a Name: BayHubTech Integrated SD controller(SDA Compliant Host) Device ID: PCI\VEN_8086&DEV_9D2D&SUBSYS_83D2103C&REV_21\3&11583659&0&F6 Driver: C:\WINDOWS\system32\DRIVERS\bhtpcrdr.sys, 1.01.0102.1025 (English), 7/4/2019 12:26:29, 199608 bytes Driver: C:\WINDOWS\system32\bhtv5Icon.dll, 1.00.0000.0006 (English), 7/4/2019 12:26:29, 1896896 bytes Driver: C:\WINDOWS\sysWoW64\bhtv5Icon.dll, 1.00.0000.0006 (English), 7/4/2019 12:26:29, 1896896 bytes Name: Intel(R) Serial IO UART Host Controller - 9D27 Device ID: PCI\VEN_8086&DEV_9D27&SUBSYS_83D2103C&REV_21\3&11583659&0&F0 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2_UART2.sys, 30.100.1823.0001 (English), 6/11/2018 00:23:30, 311856 bytes Name: Intel(R) Serial IO I2C Host Controller - 9D61 Device ID: PCI\VEN_8086&DEV_9D61&SUBSYS_83D2103C&REV_21\3&11583659&0&A9 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2_I2C.sys, 30.100.1823.0001 (English), 6/11/2018 00:23:28, 191024 bytes Name: Intel(R) UHD Graphics 620 Device ID: PCI\VEN_8086&DEV_5917&SUBSYS_83D2103C&REV_07\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdkmd64.sys, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 15499824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxs64.vp, 3/27/2019 16:41:24, 4858 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 21354048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd11dxva64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:20, 60780512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12dxva64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:21, 62261304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12umd64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:21, 24969888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdgmm64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 951824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxcmrt64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 219040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfx11cmrt64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 217408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdumdim64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 2587528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd9dxva64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 61065064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdail64.dll, 3/27/2019 16:41:22, 197128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iga64.dll, 3/27/2019 16:41:18, 3179032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igc64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 33668608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\UniversalAdapter64.dll, 3/27/2019 16:41:28, 169248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\common_clang64.dll, 4.03.0000.0000 (English), 3/27/2019 16:41:17, 49928960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdfcl64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 788240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdmd64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 4016904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdde64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 456048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdinfo64.dll, 3/27/2019 16:41:22, 141040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdext64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 400624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10idpp64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 561872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10iumd32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 20079072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd11dxva32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:20, 59027136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12dxva32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:20, 60450272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd12umd32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:21, 24404384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdgmm32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 820240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdumdim32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 2252072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd9dxva32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 59168320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdail32.dll, 3/27/2019 16:41:22, 170016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxcmrt32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 183968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfx11cmrt32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 182944 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iga32.dll, 3/27/2019 16:41:18, 2703696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igc32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 29923008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\UniversalAdapter32.dll, 3/27/2019 16:41:28, 256160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\common_clang32.dll, 4.03.0000.0000 (English), 3/27/2019 16:41:17, 38533472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdfcl32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 824840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdmd32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:23, 3102728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdde32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 374864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdinfo32.dll, 3/27/2019 16:41:22, 122736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdext32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:22, 310768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igd10idpp32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:19, 539688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxo64.vp, 3/27/2019 16:41:24, 43969 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxc64.vp, 3/27/2019 16:41:24, 42640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxg64.vp, 3/27/2019 16:41:24, 43690 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxo64_dev.vp, 3/27/2019 16:41:24, 43269 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxc64_dev.vp, 3/27/2019 16:41:24, 42962 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxg64_dev.vp, 3/27/2019 16:41:24, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxa64.vp, 3/27/2019 16:41:24, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\iglhxa64.cpa, 3/27/2019 16:41:24, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\IntelCpHDCPSvc.exe, 25.20.0100.6472 (English), 3/27/2019 16:41:24, 485856 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\IntelCpHeciSvc.exe, 9.01.0001.1117 (English), 3/27/2019 16:41:24, 489440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\cp_resources.bin, 3/27/2019 16:41:17, 1071820 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\difx64.exe, 1.04.0004.0000 (English), 3/27/2019 16:41:17, 155616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxDH.dll, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 1127432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxDI.dll, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 457224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxLHM.dll, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 2272776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxEM.exe, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 1061344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxCUIServicePS.dll, 3/27/2019 16:41:23, 412160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxCUIService.exe, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 401888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 3/27/2019 16:41:23, 123912 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 3/27/2019 16:41:23, 22536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\GfxUIEx.exe, 6.15.0100.6472 (English), 3/27/2019 16:41:18, 497632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\Gfxv4_0.exe, 8.15.0100.6472 (Italian), 3/27/2019 16:41:18, 1226720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\GfxResources.dll, 8.15.0100.6472 (Italian), 3/27/2019 16:41:18, 9335296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (Italian), 3/27/2019 16:41:25, 645640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxCPL.cpl, 3/27/2019 16:41:23, 286728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxDTCM.dll, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 192008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxext.exe, 6.15.0100.6472 (English), 3/27/2019 16:41:23, 347616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxexps.dll, 6.15.0010.3682 (English), 3/27/2019 16:41:23, 55232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\GfxDownloadWrapper.exe, 8.15.0100.6472 (Italian), 3/27/2019 16:41:17, 141792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxSDK.exe, 3/27/2019 16:41:23, 1126880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 3/27/2019 16:41:23, 99848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\ColorImageEnhancement.wmv, 3/27/2019 16:41:17, 375173 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\ImageStabilization.wmv, 3/27/2019 16:41:24, 403671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\FilmModeDetection.wmv, 3/27/2019 16:41:17, 641530 bytes Driver: C:\WINDOWS\system32\igfxCPL.cpl, 3/27/2019 16:41:23, 286728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igfxexps32.dll, 6.15.0010.3682 (English), 3/27/2019 16:41:23, 52744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\ig9icd64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:18, 15298056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\ig9icd32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:18, 12000768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\OSSCOPYRIGHT, 3/27/2019 16:41:28, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igvk64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:24, 8375080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igvk64.json, 3/27/2019 16:41:24, 137 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\VulkanRT-EULA.txt, 3/27/2019 16:41:28, 895 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igvk32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:24, 7486448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igvk32.json, 3/27/2019 16:41:24, 137 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 987112 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 253408 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 987112 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 253408 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 853992 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 228832 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 853992 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.01.0082.0001 (English), 3/27/2019 16:41:28, 228832 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt, 3/27/2019 16:41:26, 1937 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt, 3/27/2019 16:41:27, 9710 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini, 3/27/2019 16:41:27, 29 bytes Driver: C:\WINDOWS\SysWow64\Intel_OpenCL_ICD32.dll, 2.01.0001.0000 (English), 3/27/2019 16:41:24, 119808 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:27, 186280 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:27, 15802784 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 1050016 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 221096 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl, 3/27/2019 16:41:26, 2729032 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o, 3/27/2019 16:41:26, 392540 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl, 3/27/2019 16:41:26, 1002756 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl, 3/27/2019 16:41:26, 2689332 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o, 3/27/2019 16:41:26, 381572 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl, 3/27/2019 16:41:26, 1004856 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl, 3/27/2019 16:41:26, 1675928 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o, 3/27/2019 16:41:26, 330296 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl, 3/27/2019 16:41:26, 892912 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 2159848 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:28, 7174552 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:27, 6323112 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:28, 6130584 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbbmalloc32.dll, 2018.00.2018.0820 (Italian), 3/27/2019 16:41:27, 105400 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbb32.dll, 2018.00.2018.0820 (Italian), 3/27/2019 16:41:27, 218552 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\clbltfnshared.rtl, 3/27/2019 16:41:26, 1711196 bytes Driver: C:\WINDOWS\system32\Intel_OpenCL_ICD64.dll, 2.01.0001.0000 (English), 3/27/2019 16:41:24, 144904 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:27, 243136 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:27, 20696488 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 1372584 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 287144 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl, 3/27/2019 16:41:26, 2738568 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o, 3/27/2019 16:41:26, 418912 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl, 3/27/2019 16:41:26, 1075524 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl, 3/27/2019 16:41:26, 2698672 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o, 3/27/2019 16:41:26, 402104 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl, 3/27/2019 16:41:26, 1076464 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl, 3/27/2019 16:41:26, 1684764 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o, 3/27/2019 16:41:26, 349392 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl, 3/27/2019 16:41:26, 968920 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll, 7.06.0000.0000 (English), 3/27/2019 16:41:26, 2905504 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:27, 7465384 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:27, 6810536 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll, 3.06.0002.0000 (English), 3/27/2019 16:41:27, 6622112 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbbmalloc64.dll, 2018.00.2018.0820 (Italian), 3/27/2019 16:41:27, 143800 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbb64.dll, 2018.00.2018.0820 (Italian), 3/27/2019 16:41:27, 281016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\IntelOpenCL32.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:24, 1209864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdrcl32.dll, 3/27/2019 16:41:23, 4144648 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\IntelOpenCL64.dll, 25.20.0100.6472 (English), 3/27/2019 16:41:24, 1571336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igdrcl64.dll, 3/27/2019 16:41:23, 4703752 bytes Driver: C:\WINDOWS\SysWow64\libEGL.dll, 3/27/2019 16:41:24, 147464 bytes Driver: C:\WINDOWS\SysWow64\libGLESv1_CM.dll, 3/27/2019 16:41:24, 125960 bytes Driver: C:\WINDOWS\SysWow64\libGLESv2.dll, 3/27/2019 16:41:24, 161312 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 19019792 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.18.0011.0021 (English), 3/27/2019 16:41:25, 11671048 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 2580584 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:26, 2433536 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 2593864 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:26, 2588640 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 2427208 bytes Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 5/28/2018 20:23:30, 1361159 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 3/27/2019 16:41:17, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 3/27/2019 16:41:17, 57143 bytes Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 3/27/2019 16:41:18, 69877 bytes Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 3/27/2019 16:41:26, 65213 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 3/27/2019 16:41:18, 71481 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_32.vp, 3/27/2019 16:41:28, 71044 bytes Driver: C:\Program Files\Intel\Media SDK\vr360sdk32.dll, 3/27/2019 16:41:28, 599736 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 20183536 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.18.0011.0021 (English), 3/27/2019 16:41:25, 21326880 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 3168584 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:26, 2991616 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:26, 3189640 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:26, 3182280 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 2971560 bytes Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 5/28/2018 20:23:30, 1376256 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 3/27/2019 16:41:17, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 3/27/2019 16:41:17, 56359 bytes Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 3/27/2019 16:41:18, 13425 bytes Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 3/27/2019 16:41:26, 13181 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 3/27/2019 16:41:18, 14009 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_64.vp, 3/27/2019 16:41:28, 13860 bytes Driver: C:\Program Files\Intel\Media SDK\vr360sdk64.dll, 3/27/2019 16:41:28, 598712 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 8.18.0008.0030 (English), 3/27/2019 16:41:24, 209024 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 8.18.0008.0030 (English), 3/27/2019 16:41:24, 180704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\libmfxhw64.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 20183536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\mfxplugin64_hw.dll, 1.18.0011.0021 (English), 3/27/2019 16:41:25, 21326880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\libmfxhw32.dll, 8.18.0011.0021 (English), 3/27/2019 16:41:25, 19019792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\mfxplugin32_hw.dll, 1.18.0011.0021 (English), 3/27/2019 16:41:25, 11671048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki130624.inf_amd64_d85487143eec5e1a\igxpco64.dll, 1.03.0025.0000 (English), 3/27/2019 16:41:24, 235016 bytes Name: Mobile Intel(R) Processor Family I/O PCI Express Root Port #9 - 9D18 Device ID: PCI\VEN_8086&DEV_9D18&SUBSYS_83D2103C&REV_F1\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.14393.2938 (English), 4/6/2019 06:52:08, 336120 bytes Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_9D3A&SUBSYS_83D2103C&REV_21\3&11583659&0&B0 Driver: C:\WINDOWS\system32\DRIVERS\TeeDriverW8x64.sys, 1914.12.0000.1256 (English), 4/18/2019 12:43:52, 266128 bytes Name: Intel(R) Ethernet Connection (4) I219-V Device ID: PCI\VEN_8086&DEV_15D8&SUBSYS_83D2103C&REV_21\3&11583659&0&FE Driver: C:\WINDOWS\system32\DRIVERS\e1d65x64.sys, 12.17.0010.0007 (Italian), 5/8/2018 09:03:28, 560640 bytes Driver: C:\WINDOWS\system32\e1d65x64.din, 1/31/2018 02:46:16, 3130 bytes Name: Intel(R) 6th Generation Core Processor Family Platform I/O SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_9D03&SUBSYS_83D2103C&REV_21\3&11583659&0&B8 Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 1094000 bytes Name: Mobile Intel(R) Processor Family I/O PCI Express Root Port #4 - 9D13 Device ID: PCI\VEN_8086&DEV_9D13&SUBSYS_83D2103C&REV_F1\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.14393.2938 (English), 4/6/2019 06:52:08, 336120 bytes Name: Mobile 7th/8th Generation Intel(R) Processor Family I/O LPC Controller (U with iHDCP2.2 Premium) - 9D4E Device ID: PCI\VEN_8086&DEV_9D4E&SUBSYS_83D2103C&REV_21\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.14393.0000 (English), 7/16/2016 13:41:53, 18784 bytes Name: Mobile Intel(R) Processor Family I/O Thermal subsystem - 9D31 Device ID: PCI\VEN_8086&DEV_9D31&SUBSYS_83D2103C&REV_21\3&11583659&0&A2 Driver: n/a Name: Realtek RTL8822BE 802.11ac PCIe Adapter Device ID: PCI\VEN_10EC&DEV_B822&SUBSYS_831B103C&REV_00\00E04CFFFEB8220100 Driver: C:\WINDOWS\system32\DRIVERS\rtwlane.sys, 2024.00.0008.0104 (English), 7/3/2019 17:39:55, 11268296 bytes Driver: C:\WINDOWS\system32\DRIVERS\rtldata.txt, 7/3/2019 17:39:55, 135667 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_1179&DEV_0116&SUBSYS_00011179&REV_00\4&C43A874&0&00E8 Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.14393.2999 (English), 5/21/2019 06:13:14, 82896 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.14393.2248 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.14393.2248 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.14393.0000 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.14393.0000 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.14393.2248 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.14393.0000 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.14393.2608 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.14393.0000 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.14393.0000 DV Muxer,0x00400000,0,0,qdv.dll,10.00.14393.0000 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.14393.2879 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.14393.2035 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.14393.2879 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.14393.2879 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.14393.2848 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.14393.2608 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.14393.2248 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.14393.2848 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.14393.2879 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.14393.2879 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.14393.2879 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.14393.2248 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.14393.2248 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.14393.2248 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.14393.2848 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.14393.2248 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.14393.2879 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.14393.2879 DV Splitter,0x00600000,1,2,qdv.dll,10.00.14393.0000 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.14393.2879 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.14393.2248 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.14393.2879 Video Renderer,0x00800001,1,0,quartz.dll,10.00.14393.2879 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.14393.2848 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.14393.2879 Video Renderer,0x00400000,1,0,quartz.dll,10.00.14393.2879 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.14393.2248 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.14393.2035 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.14393.2248 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.14393.2248 Overlay Mixer2,0x00200000,1,1,, Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.14393.2248 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.14393.2248 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.14393.2248 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.14393.0000 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.14393.2608 Null Renderer,0x00200000,1,0,qedit.dll,10.00.14393.2608 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.14393.2248 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.14393.0206 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.14393.2848 Smart Tee,0x00200000,1,2,qcap.dll,10.00.14393.2248 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.14393.2879 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.14393.2879 Wave Parser,0x00400000,1,1,quartz.dll,10.00.14393.2879 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.14393.2879 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.14393.2879 File stream renderer,0x00400000,1,1,quartz.dll,10.00.14393.2879 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.14393.2273 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.14393.2848 AVI Mux,0x00200000,1,0,qcap.dll,10.00.14393.2248 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.14393.2879 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.14393.2879 File Source (URL),0x00400000,0,1,quartz.dll,10.00.14393.2879 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.14393.2248 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.14393.2515 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.14393.2248 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.14393.2879 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.14393.0000 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.14393.0000 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.14393.0000 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.14393.0000 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.14393.2879 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.14393.2248 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.14393.0000 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.14393.2879 PCM,0x00200000,1,1,quartz.dll,10.00.14393.2879 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.14393.2879 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.14393.2879 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.14393.2879 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.14393.2879 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.14393.2879 Audio Capture Sources: Internal Microphone (Conexant ISST Audio),0x00200000,0,0,qcap.dll,10.00.14393.2248 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.14393.3085 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.14393.3085 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.14393.3085 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.14393.2879 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.14393.2879 WDM Streaming Capture Devices: Conexant ISST Audio capture,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 Conexant ISST Audio capture,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 HP HD Camera,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 WDM Streaming Rendering Devices: Conexant ISST Audio output,0x00200000,2,2,ksproxy.ax,10.00.14393.2273 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.14393.2248 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.14393.2248 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.14393.2248 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.14393.2248 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.14393.2248 Video Capture Sources: HP HD Camera,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.14393.2248 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.14393.2248 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.14393.2248 BDA CP/CA Filters: Decrypt/Tag,0x00600000,1,1,EncDec.dll,10.00.14393.2273 Encrypt/Tag,0x00200000,0,0,EncDec.dll,10.00.14393.2273 PTFilter,0x00200000,0,0,EncDec.dll,10.00.14393.2273 XDS Codec,0x00200000,0,0,EncDec.dll,10.00.14393.2273 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.14393.2273 Audio Renderers: Speakers (Conexant ISST Audio),0x00200000,1,0,quartz.dll,10.00.14393.2879 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.14393.2879 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.14393.2879 DirectSound: Speakers (Conexant ISST Audio),0x00200000,1,0,quartz.dll,10.00.14393.2879 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 8.18.0011.0021 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.14393.2608 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.14393.0000 Microsoft H265 Video Decoder MFT, {420A51A3-D605-430C-B4FC-45274FA6C562}, 0x1, hevcdecoder.dll, 10.00.14393.2999 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.14393.2248 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.14393.2608 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.14393.0000 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.14393.2608 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.14393.1066 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.14393.0000 Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000}, 0x1, MSVP9DEC.dll, 10.00.14393.3085 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.14393.0000 Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 8.18.0011.0021 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 8.18.0011.0021 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.14393.2248 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.14393.0000 Microsoft MF VPX Encoder Transform, {AEB6C755-2546-4881-82CC-E15AE5EBFF3D}, 0x1, MSVPXENC.dll, 10.00.14393.3085 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.14393.0000 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.14393.0000 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.14393.2248 H265 Encoder MFT, {F2F84074-8BCA-40BD-9159-E880F673DD3B}, 0x1, mfh265enc.dll, 10.00.14393.2608 Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.14393.0000 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.14393.0000 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.14393.3085 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.14393.0000 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.14393.0000 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.14393.0351 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.14393.0351 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.14393.0000 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.14393.2248 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.14393.0206 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.14393.3053 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.14393.3053 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.14393.2248 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.14393.0000 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.14393.2457 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.14393.0206 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.14393.0000 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.14393.3053 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.14393.3053 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.14393.0000 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.14393.0000 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.14393.3053 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.14393.0479 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.14393.0479 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.14393.0479 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.14393.3053 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.14393.2457 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.14393.2248 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.14393.0000 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.14393.2248 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.14393.0000 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.14393.0000 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.14393.0000 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.14393.0206 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.14393.0000 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.14393.0000 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.14393.2608 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.14393.2608 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred httpnd:, {2EEEED04-0908-4CDB-AF8F-AC5B768A34C9}, Drm Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53564548-0000-0010-8000-00AA00389B71}, Microsoft H265 Video Decoder MFT, {420A51A3-D605-430C-B4FC-45274FA6C562} MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} {43564548-0000-0010-8000-00AA00389B71}, Microsoft H265 Video Decoder MFT, {420A51A3-D605-430C-B4FC-45274FA6C562} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {30395056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000} {30385056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000} MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT {00001600-0000-0100-0800-000aa00389b71}, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: HID\VID_248A&PID_8514&REV_0100&MI_00&Col03 P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: PnPGenericDriverFound Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: HID\VID_248A&PID_8514&REV_0100&MI_00&Col03 P3: P4: P5: P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: PnPGenericDriverFound Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: HID\VID_248A&PID_8514&REV_0100&MI_00&Col02 P3: P4: P5: P6: P7: P8: P9: P10: +++ WER3 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\VID_248A&PID_8514&REV_0100&MI_00 P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10: +++ WER4 +++: Fault bucket , type 0 Event Name: PnPGenericDriverFound Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\VID_248A&PID_8514&REV_0100&MI_00 P3: P4: P5: P6: P7: P8: P9: P10: +++ WER5 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\VID_248A&PID_8514&REV_0100&MI_01 P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: PnPGenericDriverFound Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\VID_248A&PID_8514&REV_0100&MI_01 P3: P4: P5: P6: P7: P8: P9: P10: +++ WER7 +++: Fault bucket 129241414467, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: SLDWORKS.exe P2: 24.5.0.58 P3: 10.0.14393.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER8 +++: Fault bucket 129164677035, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: dllhost.exe P2: 10.0.14393.0 P3: 10.0.14393.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER9 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: HID\VID_248A&PID_8514&REV_0100&MI_00&Col04 P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10: ...#SSU#...