Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Windows Antivirus somehow de-activated resulting in infection

Started by daba , Sep 25 2019 06:16 AM

infection antivirus de-activated

Page 6 of 10
4
5
6
7
8

Please log in to reply

#76
RKinner

Posted 08 October 2019 - 04:47 PM

Malware Expert

Expert
24,625 posts

Download the BIOS file and Save it. Make sure you are plugged into AC. Close all programs then right click on it and Run As Admin. Reboot when done.

I don't know about Driver Detect but if you download

Intel Rapid Storage Technology Driver and Management Console it works the same way. Expect the other two that it found will work the same way.

#77
daba

Posted 09 October 2019 - 12:11 AM

Member

Topic Starter
Member
367 posts

Thanks. My concern was to understand the procedure required between manual installation of the BIOS file and the automatic installation of the others. It clearly states BIOS is a manual install. I'm trying to google it. Does it mean that I can - as you described in your last post - simply right click and run as administrator then reboot for each of the others in turn but that for the manual BIOS install something else entirely needs to happen? Do I need to do something like this: https://au.answers.a...dows-vista-or-7. Please advise, thank you very much.

#78
daba

Posted 09 October 2019 - 01:02 AM

Member

Topic Starter
Member
367 posts

Panic over. I installed the BIOS and two of the three other Dell SupportAssist drivers. Despite repeated tries to install Intel Chipset Device Software Driver, SupportAssist still lists it as needing to be installed. I've run it twice and it's still showing this. I don't know if this helps you but I've done a snip on Latency Monitor for the hardpage dafaults and devices. Thank you. I sense light at the end of the tunnel.

#79
daba

Posted 09 October 2019 - 01:49 AM

Member

Topic Starter
Member
367 posts

I forgot about Intel Rapid Storage Technology Driver and Management Console but have now installed it. When I fire up Opera and go to my bookmarked geekstogo thread for example, it hangs for a number of seconds before finally opening.

#80
RKinner

Posted 09 October 2019 - 04:28 AM

Malware Expert

Expert
24,625 posts

CCleaner does not need to be running. Uninstall it. Also uninstall the Intel Driver and Support Assistant.

Did you try the latest Qualcomm update from Dell?

Rerun VEW for both System & Application and post both logs.

#81
daba

Posted 09 October 2019 - 04:43 AM

Member

Topic Starter
Member
367 posts

Thank you. Have deleted CCleaner and Intel Driver Support. Gone. But I see from Revo Uninstaller listing that I still have Dell SupportAssistant and another Intel thing called Intel Computing Improvement Program: should I get rid? Regarding the Qualcomm update from Dell: sorry but I don't know how to know the answer to that.

Vino's Event Viewer v01c run on Windows 7 in English

Report run at 09/10/2019 12:41:52 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Critical Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 08/10/2019 4:55:31 PM

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Error Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 09/10/2019 7:05:03 AM

Type: Error Category: 0

Event: 10010 Source: Microsoft-Windows-DistributedCOM

The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/10/2019 6:45:03 AM

Type: Error Category: 0

Event: 7043 Source: Service Control Manager

The aswbIDSAgent service did not shut down properly after receiving a preshutdown control.

Log: 'System' Date/Time: 09/10/2019 6:39:05 AM

Type: Error Category: 0

Event: 7043 Source: Service Control Manager

The aswbIDSAgent service did not shut down properly after receiving a preshutdown control.

Log: 'System' Date/Time: 09/10/2019 6:28:28 AM

Type: Error Category: 0

Event: 7043 Source: Service Control Manager

The aswbIDSAgent service did not shut down properly after receiving a preshutdown control.

Log: 'System' Date/Time: 09/10/2019 6:16:07 AM

Type: Error Category: 0

Event: 7011 Source: Service Control Manager

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the DDVDataCollector service.

Log: 'System' Date/Time: 09/10/2019 6:15:29 AM

Type: Error Category: 0

Event: 7043 Source: Service Control Manager

The aswbIDSAgent service did not shut down properly after receiving a preshutdown control.

Log: 'System' Date/Time: 08/10/2019 4:56:01 PM

Type: Error Category: 0

Event: 6008 Source: EventLog

The previous system shutdown at 6:42:00 PM on ?10/?8/?2019 was unexpected.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Warning Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 09/10/2019 10:31:15 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DAVIDDELL2\David Jackson SID (S-1-5-21-2490165305-1638453623-257508744-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 09/10/2019 10:06:47 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:50:49 AM

Type: Warning Category: 1014

Event: 1014 Source: Microsoft-Windows-DNS-Client

Name resolution for the name ncc.avast.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/10/2019 9:50:30 AM

Type: Warning Category: 1014

Event: 1014 Source: Microsoft-Windows-DNS-Client

Name resolution for the name clients4.brave.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/10/2019 9:40:55 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:39:44 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

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 DAVIDDELL2\David Jackson SID (S-1-5-21-2490165305-1638453623-257508744-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.387_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.

Log: 'System' Date/Time: 09/10/2019 9:39:36 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:34:47 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:34:44 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:30:55 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

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.

Log: 'System' Date/Time: 09/10/2019 9:30:55 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 9:30:36 AM

Type: Warning Category: 0

Event: 1 Source: rt640x64

Realtek PCIe GBE Family Controller is disconnected from network.

Log: 'System' Date/Time: 09/10/2019 9:30:35 AM

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred. Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express) Primary Bus:Device:Function: 0x0:0x1C:0x5 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_8086&DEV_9D15&SUBSYS_08411028&REV_F1 Secondary Device Name:

Log: 'System' Date/Time: 09/10/2019 9:30:35 AM

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

Log: 'System' Date/Time: 09/10/2019 8:12:36 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 8:06:41 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 8:06:37 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 8:06:35 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 7:53:25 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Log: 'System' Date/Time: 09/10/2019 7:49:51 AM

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

Vino's Event Viewer v01c run on Windows 7 in English

Report run at 09/10/2019 12:43:06 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Critical Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Error Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'Application' Date/Time: 09/10/2019 10:37:42 AM

Type: Error Category: 0

Event: 8193 Source: VSS

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid. .

Operation:

Executing Asynchronous Operation

Context:

Current State: DoSnapshotSet

Log: 'Application' Date/Time: 09/10/2019 10:36:55 AM

Type: Error Category: 0

Event: 8193 Source: VSS

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid. .

Operation:

Executing Asynchronous Operation

Context:

Current State: DoSnapshotSet

Log: 'Application' Date/Time: 09/10/2019 10:34:01 AM

Type: Error Category: 0

Event: 8193 Source: VSS

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid. .

Operation:

Executing Asynchronous Operation

Context:

Current State: DoSnapshotSet

Log: 'Application' Date/Time: 09/10/2019 10:32:55 AM

Type: Error Category: 0

Event: 8194 Source: VSS

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process.

Operation:

Gathering Writer Data

Context:

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Name: System Writer

Writer Instance ID: {c67168a9-c7fb-461b-a10d-8ef64b428595}

Log: 'Application' Date/Time: 09/10/2019 10:00:43 AM

Type: Error Category: 0

Event: 1020 Source: Microsoft-Windows-Perflib

The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 22432 and the required size was 31568.

Log: 'Application' Date/Time: 09/10/2019 9:32:30 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

License Activation (slui.exe) failed with the following error code: hr=0xC004F074 Command-line arguments: RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=58e97c99-f377-4ef1-81d5-4ad5522b5fd8;NotificationInterval=1440;Trigger=NetworkAvailable

Log: 'Application' Date/Time: 09/10/2019 9:32:28 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:44:51 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:44:44 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:36:10 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:35:41 AM

Type: Error Category: 0

Event: 0 Source: SupportAssistAgent

An exception occurred in session change of service start: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Dell.Services.SupportAssist.SupportAssistAgentCore.ISupportAssistProcessor", name = "(none)". Exception occurred while: while resolving. Exception is: InvalidOperationException - The current type, Dell.Services.SupportAssist.SupportAssistAgentCore.ISupportAssistProcessor, is an interface and cannot be constructed. Are you missing a type mapping? ----------------------------------------------- At the time of the exception, the container was: Resolving Dell.Services.SupportAssist.SupportAssistAgentCore.ISupportAssistProcessor,(none) ---> System.InvalidOperationException: The current type, Dell.Services.SupportAssist.SupportAssistAgentCore.ISupportAssistProcessor, is an interface and cannot be constructed. Are you missing a type mapping? at Microsoft.Practices.ObjectBuilder2.DynamicMethodConstructorStrategy.ThrowForAttemptingToConstructInterface(IBuilderContext context) at BuildUp_Dell.Services.SupportAssist.SupportAssistAgentCore.ISupportAssistProcessor(IBuilderContext ) at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context) at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context) at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides) --- End of inner exception stack trace --- at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides) at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides) at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides) at Dell.Services.SupportAssist.Bootstrapper.BootStrapper.SessionChangeAction(SessionChangeDescription changeDescription) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Dell.Services.SupportAssist.SupportAssistAgent.BootStrapperMinimized.SessionChangeAction(SessionChangeDescription changeDescription) at Dell.Services.SupportAssist.SupportAssistAgent.SupportAssistAgent.OnSessionChange(SessionChangeDescription changeDescription)

Log: 'Application' Date/Time: 09/10/2019 7:32:24 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

License Activation (slui.exe) failed with the following error code: hr=0x8007139F Command-line arguments: RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=58e97c99-f377-4ef1-81d5-4ad5522b5fd8;NotificationInterval=1440;Trigger=NetworkAvailable

Log: 'Application' Date/Time: 09/10/2019 7:08:30 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:07:12 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:07:03 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 7:05:03 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

License Activation (slui.exe) failed with the following error code: hr=0x80004005 Command-line arguments: RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=58e97c99-f377-4ef1-81d5-4ad5522b5fd8;NotificationInterval=1440;Trigger=NetworkAvailable

Log: 'Application' Date/Time: 09/10/2019 6:52:45 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 6:48:56 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 6:48:47 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

Log: 'Application' Date/Time: 09/10/2019 6:41:19 AM

Type: Error Category: 0

Event: 8198 Source: Microsoft-Windows-Security-SPP

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Warning Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'Application' Date/Time: 09/10/2019 9:32:21 AM

Type: Warning Category: 0