Windows 10 - Logitech K800 keyboard (& USB keyboard) stops responding


  1. Posts : 2
    Windows 10 Pro x64
       #1

    Windows 10 - Logitech K800 keyboard (& USB keyboard) stops responding


    I upgraded from Windows 8.1 (and I never had this problem), to Windows 10 and I noticing that my keyboard would stop responding in windows explorer, calculator, search, etc. The keyboard had no issues working in a browser like Chrome, but it wouldn't respond in something like Adobe Premiere Pro.

    To clarify - the keyboard works fine initially when I restart my computer. And then randomly, it decides not to work in explorer. That's when I start testing various applications to see if it works. What I found was that Adobe CC programs, windows explorer and anything native to Windows (programs such as calculator, search, etc.) doesn't respond to keyboard inputs.

    But it gets more confusing - my keyboard still works fine. For example, if I hold down, ctrl+shift+esc, Task Manager does show up. If I hit the calculator shortcut on my keyboard, calculator does come. If I toggle Caps Lock, the little notification appears on my screen telling me that Caps Lock is on or off.

    Within Chrome, the biggest issue I found was if I use the period in the numeric keypad side, it acts as "delete" instead of a period, whereas the numbers all work perfectly (hitting '1' gives me '1', not 'end').

    I'm at wits end because I even clean installed Windows 10, in case of an bug during the upgrade, and I'm experiencing the exact same thing. Drivers were the latest from Logitech's site, but the still am using the old unifying receiver (if that makes a difference).

    Also, I have set my power settings to have my computer go to sleep if idle for a few hours. Depending on the "time" (for example, if I put my computer to sleep after a fresh restart, it works fine. But if my computer sleeps sometimes later, it wouldn't respond), my computer wouldn't respond.

    I have a Logitech Performance MX, and that works perfectly even when the keyboard isn't working properly. Haven't experienced any issues with it, only the keyboard.

    If I unpair it via the unifying software (during the keyboard problem), I can re-pair it, but in the box that asks to type a few things to make sure it works, nothing can be typed. But it still types in Google Chrome...

    In the unifying software, there is an advanced option that shows when the devices are being used. I tried to see what the reaction would be during one of these events, and it looks like it still is "responding" (as in orange unifying icon pops up whenever I move the mouse or type something on the keyboard)

    I've also tried with other Logitech Keyboards and the same thing happens.
    Other USB keyboards during this event also doesn't work.

    I should mention - it does go away and start to respond shortly after, but the fact that it is happening is bothersome.
    Any suggestions?
      My Computer


  2. Posts : 441
    Windows 10
       #2

    Serenity23 said:
    I upgraded from Windows 8.1 (and I never had this problem), to Windows 10 and I noticing that my keyboard would stop responding in windows explorer, calculator, search, etc. The keyboard had no issues working in a browser like Chrome, but it wouldn't respond in something like Adobe Premiere Pro.

    To clarify - the keyboard works fine initially when I restart my computer. And then randomly, it decides not to work in explorer. That's when I start testing various applications to see if it works. What I found was that Adobe CC programs, windows explorer and anything native to Windows (programs such as calculator, search, etc.) doesn't respond to keyboard inputs.

    But it gets more confusing - my keyboard still works fine. For example, if I hold down, ctrl+shift+esc, Task Manager does show up. If I hit the calculator shortcut on my keyboard, calculator does come. If I toggle Caps Lock, the little notification appears on my screen telling me that Caps Lock is on or off.

    Within Chrome, the biggest issue I found was if I use the period in the numeric keypad side, it acts as "delete" instead of a period, whereas the numbers all work perfectly (hitting '1' gives me '1', not 'end').

    I'm at wits end because I even clean installed Windows 10, in case of an bug during the upgrade, and I'm experiencing the exact same thing. Drivers were the latest from Logitech's site, but the still am using the old unifying receiver (if that makes a difference).

    Also, I have set my power settings to have my computer go to sleep if idle for a few hours. Depending on the "time" (for example, if I put my computer to sleep after a fresh restart, it works fine. But if my computer sleeps sometimes later, it wouldn't respond), my computer wouldn't respond.

    I have a Logitech Performance MX, and that works perfectly even when the keyboard isn't working properly. Haven't experienced any issues with it, only the keyboard.

    If I unpair it via the unifying software (during the keyboard problem), I can re-pair it, but in the box that asks to type a few things to make sure it works, nothing can be typed. But it still types in Google Chrome...

    In the unifying software, there is an advanced option that shows when the devices are being used. I tried to see what the reaction would be during one of these events, and it looks like it still is "responding" (as in orange unifying icon pops up whenever I move the mouse or type something on the keyboard)

    I've also tried with other Logitech Keyboards and the same thing happens.
    Other USB keyboards during this event also doesn't work.

    I should mention - it does go away and start to respond shortly after, but the fact that it is happening is bothersome.
    Any suggestions?
    No guarantee but open a cmd as admin and run sfc /scannow
      My Computer


  3. Posts : 2
    Windows 10 Pro x64
    Thread Starter
       #3

    Bazz said:
    No guarantee but open a cmd as admin and run sfc /scannow
    I ran it and got this error at the end:
    Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log%WinDir%\Logs\CBS\CBS.log.
    The log file is too large to upload here, so I added it to Mediafire (
    http://www.mediafire.com/download/m8...hs4ira/CBS.log).

    But here is the "repair part" of the log?
    2015-08-14 20:06:47, Info CSI 00004f7a [SR] Verify complete
    2015-08-14 20:06:47, Info CSI 00004f7b [SR] Repairing 1 components
    2015-08-14 20:06:47, Info CSI 00004f7c [SR] Beginning Verify and Repair transaction
    2015-08-14 20:06:47, Info CSI 00004f7d Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-_dataperfcou.._shared12_neutral_h_b03f5f7f11d50a3a_4.0.10240.16384_none_d9bd4db7edc80d94\_dataperfco unters_shared12_neutral.h do not match actual file [l:72{36}]"_dataperfcounters_shared12_neutral.h" :
    Found: {l:20 b:Lry1Tmwzghl3AKyDzxoNOFfV5+k=} Expected: {l:20 b:Rfp/xL8wA6B0O1mA915yFbbS1Ws=}
    Found: {l:32 b:BnPX7YFa/T9jQSEb4E01KFQAXRVnAiUD2GobYj59lWY=} Expected: {l:32 b:kZtPbwBwwJCsYyALFQU/Lg3/hlh0NIqs5fwGalognZc=}
    2015-08-14 20:06:47, Info CSI 00004f7e [SR] Cannot repair member file [l:72{36}]"_dataperfcounters_shared12_neutral.h" of NetFx4-_dataperfcounters_shared12_neutral_h, Version = 4.0.10240.16384, pA = amd64, , PublicKeyToken = {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch
    2015-08-14 20:06:47, Info CSI 00004f7f@2015/8/15:03:06:47.962 Primitive installers committed for repair
    2015-08-14 20:06:47, Info CSI 00004f80 Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-_dataperfcou.._shared12_neutral_h_b03f5f7f11d50a3a_4.0.10240.16384_none_d9bd4db7edc80d94\_dataperfco unters_shared12_neutral.h do not match actual file [l:72{36}]"_dataperfcounters_shared12_neutral.h" :
    Found: {l:20 b:Lry1Tmwzghl3AKyDzxoNOFfV5+k=} Expected: {l:20 b:Rfp/xL8wA6B0O1mA915yFbbS1Ws=}
    Found: {l:32 b:BnPX7YFa/T9jQSEb4E01KFQAXRVnAiUD2GobYj59lWY=} Expected: {l:32 b:kZtPbwBwwJCsYyALFQU/Lg3/hlh0NIqs5fwGalognZc=}
    2015-08-14 20:06:47, Info CSI 00004f81 [SR] Cannot repair member file [l:72{36}]"_dataperfcounters_shared12_neutral.h" of NetFx4-_dataperfcounters_shared12_neutral_h, Version = 4.0.10240.16384, pA = amd64, , PublicKeyToken = {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch
    2015-08-14 20:06:47, Info CSI 00004f82 [SR] This component was referenced by [l:248{124}]"Microsoft-Windows-NetFx-Shared-Perfcounters-Client~31bf3856ad364e35~amd64~~10.0.10240.16384.NetFx-Shared-Perfcounters-Client"
    2015-08-14 20:06:47, Info CSI 00004f83 Hashes for file member \??\C:\Windows\Inf\.NET Data Provider for SqlServer\_dataperfcounters_shared12_neutral.h do not match actual file [l:72{36}]"_dataperfcounters_shared12_neutral.h" :
    Found: {l:20 b:Lry1Tmwzghl3AKyDzxoNOFfV5+k=} Expected: {l:20 b:Rfp/xL8wA6B0O1mA915yFbbS1Ws=}
    Found: {l:32 b:BnPX7YFa/T9jQSEb4E01KFQAXRVnAiUD2GobYj59lWY=} Expected: {l:32 b:kZtPbwBwwJCsYyALFQU/Lg3/hlh0NIqs5fwGalognZc=}
    2015-08-14 20:06:47, Info CSI 00004f84 Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-_dataperfcou.._shared12_neutral_h_b03f5f7f11d50a3a_4.0.10240.16384_none_d9bd4db7edc80d94\_dataperfco unters_shared12_neutral.h do not match actual file [l:72{36}]"_dataperfcounters_shared12_neutral.h" :
    Found: {l:20 b:Lry1Tmwzghl3AKyDzxoNOFfV5+k=} Expected: {l:20 b:Rfp/xL8wA6B0O1mA915yFbbS1Ws=}
    Found: {l:32 b:BnPX7YFa/T9jQSEb4E01KFQAXRVnAiUD2GobYj59lWY=} Expected: {l:32 b:kZtPbwBwwJCsYyALFQU/Lg3/hlh0NIqs5fwGalognZc=}
    2015-08-14 20:06:47, Info CSI 00004f85 [SR] Could not reproject corrupted file [ml:104{52},l:102{51}]"\??\C:\Windows\Inf\.NET Data Provider for SqlServer"\[l:72{36}]"_dataperfcounters_shared12_neutral.h"; source file in store is also corrupted
    2015-08-14 20:06:47, Info CSI 00004f86@2015/8/15:03:06:47.962 Primitive installers committed for repair
    2015-08-14 20:06:47, Info CSI 00004f87 [SR] Repair complete
    2015-08-14 20:06:47, Info CSI 00004f88 [SR] Committing transaction
    2015-08-14 20:06:47, Info CSI 00004f89 Creating NT transaction (seq 2), objectname [6]"(null)"
    2015-08-14 20:06:47, Info CSI 00004f8a Created NT transaction (seq 2) result 0x00000000, handle @0x4f0
    2015-08-14 20:06:47, Info CSI 00004f8b@2015/8/15:03:06:47.977 Beginning NT transaction commit...
    2015-08-14 20:06:47, Info CSI 00004f8c@2015/8/15:03:06:47.993 CSI perf trace:
    CSIPERF:TXCOMMIT;8089
    2015-08-14 20:06:47, Info CSI 00004f8d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:14.
Find Us




Windows 10 Forums