Cumulative Update KB4074588 Windows 10 v1709 Build 16299.248 - Feb. 13

Page 12 of 15 FirstFirst ... 21011121314 ... LastLast

  1. Posts : 1,079
    10 + Linux
       #110

    System spec is same here: HP desktop.
    I've been there too, and delete the keyboard driver is the easiest way to recover keyboard. Keyboard troubleshooter is also among easiest steps to try.
    Settings>Udate & Security>troubleshoot>Keyboard>Run the troubleshooter.
      My Computer


  2. Posts : 31,622
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #111

    Ah @IronZorg89, you meant Reset Windows Update in Windows 10
    Yes, that's a good first step.
      My Computers


  3. Posts : 2,557
    Windows 10 pro x64-bit
       #112

    Bree said:
    Ah @IronZorg89, you meant Reset Windows Update in Windows 10
    Yes, that's a good first step.
    Now we are on the same track..
      My Computers


  4. Posts : 2,557
    Windows 10 pro x64-bit
       #113

    MikeMecanic said:
    System spec is same here: HP desktop.
    I've been there too, and delete the keyboard driver is the easiest way to recover keyboard. Keyboard troubleshooter is also among easiest steps to try.
    Settings>Udate & Security>troubleshoot>Keyboard>Run the troubleshooter.
    But as @TeriB mentioned, he (she) had recovered the full functionality of the keyboard after uninstalling the update. That means the problem, in all likelihood, is more related to the update and not the keyboard driver. That was my point. I would have agreed with you only if after uninstalling the update, the same problem kept on occurring.
      My Computers


  5. Posts : 22
    Windows 10
       #114

    Thanks guys! I will look into resetting windows update but would never do a repair/eset windows just because of the keyboard now that I know it was the update that screwed it up. Repair /reset windows is too much like using 'recovery' and no thank you...lol. I have never had to do anything like that with any version of windows. Never had an issue before with XP/7 or 10.

    The irony is that we all know that eventually this update is going to install itself again no matter what I do. I don't 'need' anything in that particular update in the first place but Windows wants what Windows wants.

    As for keyboard drivers...I did delete the keyboard from device manager a couple of times as part of my diagnosis but nothing came of it. I searched for drivers on my tablet (so I could type...grr) for my Logitech keyboard but there really aren't any....setpoint is all that is needed and its not really a driver.
      My Computer


  6. Posts : 1,079
    10 + Linux
       #115

    TerriB said:
    Thanks guys! I will look into resetting windows update but would never do a repair/eset windows just because of the keyboard now that I know it was the update that screwed it up. Repair /reset windows is too much like using 'recovery' and no thank you...lol. I have never had to do anything like that with any version of windows. Never had an issue before with XP/7 or 10.

    The irony is that we all know that eventually this update is going to install itself again no matter what I do. I don't 'need' anything in that particular update in the first place but Windows wants what Windows wants.

    As for keyboard drivers...I did delete the keyboard from device manager a couple of times as part of my diagnosis but nothing came of it. I searched for drivers on my tablet (so I could type...grr) for my Logitech keyboard but there really aren't any....setpoint is all that is needed and its not really a driver.
    It is KB4074588 that causes the issue and deleting the driver would tell that update screw up the keyboard or not.

    Now we know that the update screw up the keyboard.

    Run maintenance is also among the easiest methods to try.

    Control panel>Security and Maintenance>Maintenance>Start maintenance.

    Edit: If you still have the same issue after resetting WU, try deleting the keyboard driver and shut down after. Recover keyboard few weeks ago that way.
    Last edited by MikeMecanic; 23 Feb 2018 at 18:48.
      My Computer


  7. Posts : 2,557
    Windows 10 pro x64-bit
       #116

    TerriB said:
    Thanks guys! I will look into resetting windows update but would never do a repair/eset windows just because of the keyboard now that I know it was the update that screwed it up. Repair /reset windows is too much like using 'recovery' and no thank you...lol. I have never had to do anything like that with any version of windows. Never had an issue before with XP/7 or 10.
    I am glad we could help in some manner, but one last point I want to make is that there is a big difference between "reset Windows" and "repair install windows". In the former, you will lose your files data or not (depending on your choice) which you can reinstall from a backup, but your applications will be gone; when in the latter, you won't lose anything (all your files data as well as your installed apps are kept). Your PC will be back just the way it was before after taking care of the bug preventing it from installing updates normally.

    If I were in your shoes, I would try the repair install (in-place upgrade) just to make sure future Windows Updates are installed seamlessly. But the decision is yours..:)
    Last edited by IronZorg89; 23 Feb 2018 at 17:17.
      My Computers


  8. Posts : 170
    Win 10 Pro 2004
       #117
      My Computers


  9. Posts : 1,091
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       #118

    Sometimes it might help to uninstall the update and then reinstall the update using the standalone installer as in my experience, the one that Windows Update downloaded somehow would not allow me to move a folder after it's copied as it keeps saying folder in use as it's locked by the System Process but deleting the folder works fine. Uninstalling and reinstalling the update fixed the problem.

    Update:
    Still have the same problem.
    Last edited by Almighty1; 27 Feb 2018 at 19:52.
      My Computer


  10. Posts : 22
    Windows 10
       #119

    MikeMecanic said:
    System spec is same here: HP desktop.
    I've been there too, and delete the keyboard driver is the easiest way to recover keyboard. Keyboard troubleshooter is also among easiest steps to try.
    Settings>Udate & Security>troubleshoot>Keyboard>Run the troubleshooter.
    I removed the device but no change and my Logitech keyboard doesn't have a 'real' driver. Setpoint is all there is. WHen I accessed driver info it said there was no driver available and I searched for one but it gave me nothing. Went to Logitech on my tablet and it only provided Setpoint but downloading that did nothing.

    Found this today thru Reddit reply to my issue but MS saying they are aware and working on solution does not give me any peace of mind whatsoever.

    USB devices may stop working after installing the February 13, 2018 update(KB4074588) - https://support.microsoft.com/en-us/...ry-13-2018-upd
      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 06:12.
Find Us




Windows 10 Forums