Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Wireless keyboard stopped working


  • Please log in to reply

#1
Jdpowell

Jdpowell

    Member

  • Member
  • PipPip
  • 75 posts

I have a wireless Logitech Keyboard and mouse.  The mouse works fine and the keyboard will only work when the computer boots up and I sign in to Windows.  After that they keyboard won't work.  

Tried to get Logitech to help and they couldn't so they sent another keyboard and mouse.  Nothing changed.  Tried to get Microsoft to help and they want $100 to start.

 

Any ideas?


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Driver not signed correctly and is not allowed to run by Windows.  What version of Windows?


  • 0

#3
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts

Windows 10 home.  The keyboard worked for a long time before not.  I uninstalled the few programs i have installed since then too.  This began on May 29.  I have had the computer a little over a year.


  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Can you:

 

 
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)
 
Search for 
 
device manager
 
hit Enter
 
 View, Show Hidden Drivers.  Now look for yellow flagged devices.  Right click on one and select properties then click on the Details tab.  Change Property to Hardware IDs.  Click on the top one then right click and copy.  Paste that into a reply.  Repeat for all yellow flagged devices.

  • 0

#5
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 15/06/2017 3:06:29 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/06/2017 4:05:57 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.
 
Log: 'System' Date/Time: 30/04/2017 11:58:19 AM
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.
 
Log: 'System' Date/Time: 25/01/2017 1:24:14 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.
 
Log: 'System' Date/Time: 23/01/2017 2:53:03 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.
 
Log: 'System' Date/Time: 20/12/2016 8:48:10 AM
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.
 
Log: 'System' Date/Time: 20/12/2016 8:19:05 AM
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.
 
Log: 'System' Date/Time: 19/12/2016 9:04:07 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.
 
Log: 'System' Date/Time: 18/12/2016 7:41:36 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.
 
Log: 'System' Date/Time: 18/12/2016 6:48:49 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.
 
Log: 'System' Date/Time: 18/12/2016 5:52:20 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.
 
Log: 'System' Date/Time: 18/12/2016 5:38:22 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.
 
Log: 'System' Date/Time: 18/12/2016 5:29:02 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: 10/06/2017 12:56:22 PM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 12:56:13 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 12:02:50 PM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 9:49:44 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:44:16 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:44:05 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:42:43 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:41:55 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:41:21 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:37:55 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:37:46 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:36:57 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024001E: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:36:53 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {0002DF02-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:36:53 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:26:23 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:20:03 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:19:52 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:18:41 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:18:41 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:18:27 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 15/06/2017 3:35:15 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:35:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name oem.twimg.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:35:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-ckdatabase.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:20 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-bookmarks.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:18 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-ckdatabase.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:14 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name linksyssmartwifi.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:11 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name sn3301.storage.live.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-bookmarks.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:00 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name disc401-prod.do.dsp.mp.microsoft.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:30:48 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ssw.live.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 2:56:08 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name cdn.content.prod.cms.msn.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 6:16:11 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 4:29:39 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 3-edge-chat.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 4:28:44 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 14/06/2017 11:01:32 PM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy26'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 8:52:01 PM
Type: Warning Category: 0
Event: 47 Source: Microsoft-Windows-Time-Service
Time Provider NtpClient: No valid response has been received from manually configured peer 129.6.15.28,0x8 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable. 
 
Log: 'System' Date/Time: 14/06/2017 10:59:45 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 10:59:32 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 10:59:31 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 5:13:14 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name apps.facebook.com timed out after none of the configured DNS servers responded.
 
 
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 15/06/2017 3:10:50 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/06/2017 3:39:00 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: microsoftedgecp.exe, version: 11.0.14393.953, time stamp: 0x58ba5911 Faulting module name: edgehtml.dll, version: 11.0.14393.1198, time stamp: 0x59028772 Exception code: 0xc0000005 Fault offset: 0x0000000000970b3c Faulting process id: 0x35e0 Faulting application start time: 0x01d2e1eabf4bb36f Faulting application path: C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe Faulting module path: C:\WINDOWS\SYSTEM32\edgehtml.dll Report Id: ffaff259-ba25-4d3c-8f9c-4aabb11b6071 Faulting package full name: Microsoft.MicrosoftEdge_38.14393.1066.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge
 
Log: 'Application' Date/Time: 15/06/2017 3:05:45 PM
Type: Error Category: 0
Event: 20227 Source: RasClient
CoId={FADA288C-0C5E-4A51-9FFD-784267B6BCEB}: The user SYSTEM dialed a connection named Broadband Connection which has failed. The error code returned on failure is 651.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 10:59:09 AM
Type: Error Category: 0
Event: 513 Source: Microsoft-Windows-CAPI2
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
 
Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
 
System Error:
Access is denied. .
 
Log: 'Application' Date/Time: 13/06/2017 11:00:13 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:13 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 12/06/2017 11:00:07 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 12/06/2017 11:00:07 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 12/06/2017 11:00:07 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 12/06/2017 11:00:07 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 12/06/2017 11:00:07 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 14/06/2017 7:26:27 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 14/06/2017 7:26:00 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 14/06/2017 7:25:57 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 14/06/2017 11:03:02 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe' (pid 13220) cannot be restarted - Application SID does not match Conductor SID..
 
Log: 'Application' Date/Time: 14/06/2017 11:03:02 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe' (pid 12236) cannot be restarted - Application SID does not match Conductor SID..
 
Log: 'Application' Date/Time: 13/06/2017 11:10:26 AM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 13/06/2017 11:10:24 AM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 13/06/2017 11:10:22 AM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 12/06/2017 8:14:28 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 12/06/2017 8:14:26 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 12/06/2017 8:14:23 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 11/06/2017 12:23:26 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 11/06/2017 12:23:24 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 11/06/2017 12:23:22 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 10/06/2017 1:18:29 PM
Type: Warning Category: 0
Event: 59 Source: Outlook
Outlook disabled the following add-in(s):
 
 
 
ProgID: DYMO.LabelWriterAddIn
GUID: {00000000-0000-0000-0000-000000000000}
Name: DYMO LabelWriter Add-In
Description: DYMO LabelWriter Add-In for Microsoft Outlook
Load Behavior: 3
HKLM: 0
Location: c:\program files (x86)\dymo\dymo label software\outlook07dymoaddin.vsto|vstolocal
Threshold Time (Milliseconds): 1000
Time Taken (Milliseconds): 1031
Disable Reason: This add-in caused Outlook to start slowly.
Policy Exception (Allow List): 0 
 
Log: 'Application' Date/Time: 10/06/2017 12:59:17 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 10/06/2017 12:59:14 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 10/06/2017 12:59:14 PM
Type: Warning Category: 0
Event: 1402 Source: HP Active Health
Channel 'HP Software Framework' does not exist, ignoring.
 
Log: 'Application' Date/Time: 10/06/2017 12:59:13 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 10/06/2017 12:56:13 PM
Type: Warning Category: 0
Event: 1030 Source: nssm
Registry key AppDirectory is unset for service ExpressVpnService. Assuming startup directory C:\Program Files (x86)\ExpressVPN\xvpnd.
 
 
 
 
There are no yellow flagged devices in Device manager

  • 0

#6
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Uninstall 

 

HP Active Health (not working)

 

(Intel) True Key  (I think this is the cause of the InstallerService errors I see.  This is foistware usually installed when you update Adobe Flash)

 

McAfee Security Scan Plus (if installed  usually comes with True Key)

 

Copy the following line:

DISM /Online /Cleanup-Image /RestoreHealth
Open an elevated command prompt:
 
 
If you open an elevated command prompt it will by default open in c:\Windows\system32
 
Once you have an elevated command prompt:
 
right click and Paste (or Edit then Paste) and the copied line should appear.
 
Hit Enter.
 
DSIM should run and should take about 15 minutes to complete.
 
the process will seem stuck at 20% or 40%, but it's normal behavior. After a few minutes, the operation should finish as expected and say
The restore operation Completed Successfully.
The operation completed successfully
Does it?
 
Once the prompt returns type (or copy and paste as above)
 
sfc  /scannow

And hit Enter.  This will take another 10-15 minutes and should finish with one of three results:

 

 
Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)
 
 
Which do you get?
 
Reboot
 
Run VEW again as before and post both logs.

  • 0

#7
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts

I did not see "elevated command prompt" so I ran a command prompt as administrator.  I don't think anything changed.

 

The operation completed successfully

 

Windows did not find any integrity violations

 

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

Report run at 16/06/2017 2:55:36 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/06/2017 4:05:57 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.
 
Log: 'System' Date/Time: 30/04/2017 11:58:19 AM
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.
 
Log: 'System' Date/Time: 25/01/2017 1:24:14 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.
 
Log: 'System' Date/Time: 23/01/2017 2:53:03 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.
 
Log: 'System' Date/Time: 20/12/2016 8:48:10 AM
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.
 
Log: 'System' Date/Time: 20/12/2016 8:19:05 AM
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.
 
Log: 'System' Date/Time: 19/12/2016 9:04:07 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.
 
Log: 'System' Date/Time: 18/12/2016 7:41:36 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.
 
Log: 'System' Date/Time: 18/12/2016 6:48:49 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.
 
Log: 'System' Date/Time: 18/12/2016 5:52:20 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.
 
Log: 'System' Date/Time: 18/12/2016 5:38:22 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.
 
Log: 'System' Date/Time: 18/12/2016 5:29:02 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: 10/06/2017 12:56:22 PM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 12:56:13 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 12:02:50 PM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 9:49:44 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:44:16 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:44:05 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:42:43 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:41:55 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:41:21 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:37:55 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:37:46 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:36:57 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024001E: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:36:53 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {0002DF02-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:36:53 AM
Type: Error 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  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from 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: 10/06/2017 8:26:23 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1703.
 
Log: 'System' Date/Time: 10/06/2017 8:20:03 AM
Type: Error 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  {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.
 
Log: 'System' Date/Time: 10/06/2017 8:19:52 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The InstallerService service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 10/06/2017 8:18:41 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:18:41 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/06/2017 8:18:27 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 15/06/2017 11:03:43 PM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy27'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 15/06/2017 3:35:15 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:35:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name oem.twimg.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:35:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-ckdatabase.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:20 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-bookmarks.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:18 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-ckdatabase.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:14 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name linksyssmartwifi.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:11 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name sn3301.storage.live.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:07 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name p52-bookmarks.icloud.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:31:00 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name disc401-prod.do.dsp.mp.microsoft.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 3:30:48 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ssw.live.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 2:56:08 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name cdn.content.prod.cms.msn.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 6:16:11 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 4:29:39 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 3-edge-chat.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/06/2017 4:28:44 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 14/06/2017 11:01:32 PM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy26'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 8:52:01 PM
Type: Warning Category: 0
Event: 47 Source: Microsoft-Windows-Time-Service
Time Provider NtpClient: No valid response has been received from manually configured peer 129.6.15.28,0x8 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable. 
 
Log: 'System' Date/Time: 14/06/2017 10:59:45 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 10:59:32 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Log: 'System' Date/Time: 14/06/2017 10:59:31 AM
Type: Warning Category: 0
Event: 4 Source: Microsoft-Windows-FilterManager
File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy25'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.
 
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 16/06/2017 2:58:17 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 15/06/2017 11:00:17 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 15/06/2017 3:39:00 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: microsoftedgecp.exe, version: 11.0.14393.953, time stamp: 0x58ba5911 Faulting module name: edgehtml.dll, version: 11.0.14393.1198, time stamp: 0x59028772 Exception code: 0xc0000005 Fault offset: 0x0000000000970b3c Faulting process id: 0x35e0 Faulting application start time: 0x01d2e1eabf4bb36f Faulting application path: C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe Faulting module path: C:\WINDOWS\SYSTEM32\edgehtml.dll Report Id: ffaff259-ba25-4d3c-8f9c-4aabb11b6071 Faulting package full name: Microsoft.MicrosoftEdge_38.14393.1066.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge
 
Log: 'Application' Date/Time: 15/06/2017 3:05:45 PM
Type: Error Category: 0
Event: 20227 Source: RasClient
CoId={FADA288C-0C5E-4A51-9FFD-784267B6BCEB}: The user SYSTEM dialed a connection named Broadband Connection which has failed. The error code returned on failure is 651.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 11:00:14 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 14/06/2017 10:59:09 AM
Type: Error Category: 0
Event: 513 Source: Microsoft-Windows-CAPI2
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
 
Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
 
System Error:
Access is denied. .
 
Log: 'Application' Date/Time: 13/06/2017 11:00:13 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:13 PM
Type: Error Category: 0
Event: 1023 Source: Microsoft-Windows-Perflib
Windows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 13/06/2017 11:00:12 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/06/2017 9:20:19 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 15/06/2017 9:20:18 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 15/06/2017 9:20:15 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 14/06/2017 7:26:27 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 14/06/2017 7:26:00 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 14/06/2017 7:25:57 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 14/06/2017 11:03:02 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe' (pid 13220) cannot be restarted - Application SID does not match Conductor SID..
 
Log: 'Application' Date/Time: 14/06/2017 11:03:02 AM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe' (pid 12236) cannot be restarted - Application SID does not match Conductor SID..
 
Log: 'Application' Date/Time: 13/06/2017 11:10:26 AM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 13/06/2017 11:10:24 AM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 13/06/2017 11:10:22 AM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 12/06/2017 8:14:28 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 12/06/2017 8:14:26 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 12/06/2017 8:14:23 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 11/06/2017 12:23:26 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 11/06/2017 12:23:24 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 
Log: 'Application' Date/Time: 11/06/2017 12:23:22 PM
Type: Warning Category: 0
Event: 6 Source: HP Active Health
Invalid SerialNumber for manufacture date
 
Log: 'Application' Date/Time: 10/06/2017 1:18:29 PM
Type: Warning Category: 0
Event: 59 Source: Outlook
Outlook disabled the following add-in(s):
 
 
 
ProgID: DYMO.LabelWriterAddIn
GUID: {00000000-0000-0000-0000-000000000000}
Name: DYMO LabelWriter Add-In
Description: DYMO LabelWriter Add-In for Microsoft Outlook
Load Behavior: 3
HKLM: 0
Location: c:\program files (x86)\dymo\dymo label software\outlook07dymoaddin.vsto|vstolocal
Threshold Time (Milliseconds): 1000
Time Taken (Milliseconds): 1031
Disable Reason: This add-in caused Outlook to start slowly.
Policy Exception (Allow List): 0 
 
Log: 'Application' Date/Time: 10/06/2017 12:59:17 PM
Type: Warning Category: 0
Event: 2901 Source: HP Active Health
Error getting Windows updates: System.Threading.ThreadAbortException: Thread was being aborted.    at Interop.WUApiLib.IUpdateSearcher.Search(String criteria)    at HP.ActiveHealth.Agents.WindowsUpdates.WindowsUpdatesAgent.GetWindowsUpdates()
 
Log: 'Application' Date/Time: 10/06/2017 12:59:14 PM
Type: Warning Category: 0
Event: 2903 Source: HP Active Health
Unable to get WindowsUpdate information in able time
 

  • 0

#8
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

The link I gave you showed that an elevated command prompt is a Command Prompt (admin).

 

Still getting

 

Event: 2901 Source: HP Active Health

 

Did you not uninstall it?  You can probably get a new one from HP if you relly want it.

 

The WMI errors are probably not significant but you can try the procedure here: 

 

https://threesquarem...pl-dll"-failed-

 

See if it will work for you.  Make sure you use an elevated command prompt.  

 

 

 

Go into device manager again and open Human Interface Devices by clicking on the arrow in front of it.   Right click on one and select properties then click on the Details tab.  Change Property to Hardware IDs.  Click on the top one then right click and copy.  Paste that into a reply.  Repeat for each device under Human Interface Device then do the same for Keyboards.  

 

Under Network Adapters may be an entry for bluetooth.  Get the same info for it.  

 

Also tell me the model number of your keyboard.  


  • 0

#9
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts

I have uninstalled adobe flash player, but cannot find the other two.


  • 0

#10
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Not sure what you are talking about.

 

Go into device manager again and open Human Interface Devices by clicking on the arrow in front of it.   Right click on one and select properties then click on the Details tab.  Change Property to Hardware IDs.  Click on the top one then right click and copy.  Paste that into a reply.  Repeat for each device under Human Interface Device then do the same for Keyboards.  
 
Under Network Adapters may be an entry for bluetooth.  Get the same info for it.  
 
Also tell me the model number of your keyboard.  

  • 0

Advertisements


#11
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts
USB\VID_051D&PID_0002&REV_0090
HID\VID_046D&PID_C52B&REV_1203&MI_01&Col02
HID\VID_046D&PID_C52B&REV_1203&MI_01&Col03
HID\VID_046D&PID_C52B&REV_1203&MI_01&Col04
HID\VID_046D&PID_C52B&REV_1203&MI_02&Col03
HID\VID_046D&PID_C52B&REV_1203&MI_02&Col01
HID\VID_046D&PID_C52B&REV_1203&MI_02&Col02
USB\VID_046D&PID_C52B&REV_1203&MI_00
USB\VID_046D&PID_C52B&REV_1203&MI_02
USB\VID_046D&PID_C52B&REV_1203&MI_01
 
 
keyboards
HID\VID_046D&PID_C52B&REV_1203&MI_00
 
don't see anything for bluetooth
 
 
 Logitech  K350

  • 0

#12
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Looking at the info on your Keyboard it does not use bluetooth.  Looks like it uses a weak 2.4 GHz WiFi so make sure the PC is not too close to the WiFi router.  It may also be a good idea to get a USB extender cable  which Logitech offers in 

https://support.logi.../faq#link_21706

 

This might explain what happens.  Prior to log in the PC does not send out any WiFi or at least not much.  At logon it probably checks for updates and such so the WiFi is very busy.  If the WiFi is on the same frequency as the keyboard it may interfere with the keyboard.  The router determines the frequency to use by picking from 12 Channels.  Routers are by default set  to choose the best WiFi Channel automatically so this frequency can change without warning.  It is possible to tell the router to always use a certain channel so that might be a work-around.  What make & model is the router?  What happens if you disable the WiFi then reboot?

 

Does your PC have any USB 3.0 ports?

 

What make & model is the PC?

 

In Device Manager under Human Interface Devices or HID, how many devices do you see?  Did you give me the top line from each so that you have a total of 10 or did you copy all the lines?

 

I would right click on each device under HID and Keyboard and Uninstall then reboot.  (Do not allow Windows to remove the drivers if it asks)  Windows should discover and reinstall the drivers.

 

Do you have Logitech Unifying Software installed?  Does it see the keyboard?


  • 0

#13
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts

The computer is a CyberPowerPC  and I don't know of a model number.  It does have a few usb ports.  I tried using a keyboard that plugged in to a usb port and it did not work either.

 

There are 10 devices.  Yes, I gave you the top line of each.

 

The router is a Linksys AC1900.  I have only had that a couple of days.  Before that it was a Netgear R6300 

 

Don't have any unifying software


  • 0

#14
Jdpowell

Jdpowell

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts

I found the unifying software on the Logitech website.  Tried 3 times to pair the keyboard then switched the receiver to another usb port and it still would not pair the device.


  • 0

#15
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,624 posts
  • MVP

Right click on each device under HID and Keyboard and Uninstall then reboot.  (Do not allow Windows to remove the drivers if it asks)  Windows should discover and reinstall the drivers.

 

After it reboots how many do you have under HID?


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP