After KB4074588 something bricked USB3 support on HP AIO c220 based system

You should be able to uninstall the KB cumulative updates individually. Go to Apps and Features and select Programs and Features and the View installed updates. Select one and then uninstall.

If you think it was a driver update then you can select to not install driver updates but that will affect all drivers. If your device is supported by HP for Windows 10 then only use their drivers. In Control Panel select System and then Advanced system settings. Select the Hardware tab and then Device installation settings change the settings to No.

This is not an isolated issue! 

KB4074588 bricked USB device support on my system killing my keyboard and making everything difficult.  At least my mouse still worked so I could use the onscreen keyboard.

My system is a custom build dual Xeon E5-2670 Asus Z9PA.

Going back to 2/14 Restore did nothing just moved me from not being able to use my USB keyboard to now getting BSoD with Windows Stop Code 0xc000021a. 

Spent 45 mins with a tech support agent on chat, after a 45min wait to speak to them, only to have them have connectivity issues to the chat and round we go again to having 65 people ahead of me now. Got a call back, then routed to a technician.  After 25 mins on hold, gave up.

Microsoft used to be great for support. 

I managed to get the system to restore by going back to 2/4 restore point, no thanks to Microsoft. 

KB4074588 has bricked my USB-Ports as well (v2.0 and v3.0)!

My machine is an elder ASUS X72VSeries  (X72Vn) notebook, that I used since 2010 (8 years!) now. It is modified with a Samsung SSD and a Sony BlueRay burner. ... I am a former software developer, who had developed tools for Win95-WinXP. - So I think, I am not a rookie.

Everything worked without problems, until last year: November/December 2017. - First I got a "boot-hanger" blue-screen, because of one of Microsofts KB-updates, Then in January 2018 the same, because of another regular update. - I needed to uninstall the update manually and very complicated - and if I did not have Acronis Backup, I could reinstall Windows 10 every month from the beginning! ;-) - Now with KB4074588 this is for me the 3rd time I need to restore a complete partition C: backup from Acronis, for to get access to my cryptocurrency USB-stick again!

I think, the next things I will do are: 1.) Selling all Microsoft shares I have, 2.) Buying at the first time, since 1986, not a new PC, but an Apple Mac. 3.) Changing everything substantial for my working into MacOS software, which will not fail every month! ... I am 51 years old now. I don't think that I ever will return to Microsoft or Windows!

Bye! :-(

This is true, and I am only commenting to support the issues everyone else is having, in hopes it may expedite a further patch. 
Currently, I am still and just now getting INACCESSIBLE_BOOT_DEVICE issues, forcing me to image several laptops at a time, in a healthcare organization where downtime cannot be an option. 

Additionally, KB4074588 is the single-handed culprit in disabling USB/HID devices. 

Once uninstalled, these devices return to functioning normally. 

I don't mind so much that these problems arise, as patches tend to come fairly quickly, but I do mind being unable to control whether I want to receive updates or not, as it appears I am stuck fixing the same issue when it happens (these are happening AT RANDOM, and sometimes solo, and sometimes in waves). 

FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED

Reboot 1st before trying these methods. Some methods may have to be performed remotely because your friggin USB ports aren't working. Method 4 is the method for when nothing else can be done.

Method 1:

Windows Key + R

appwiz.cpl

View installed updates

Look for update KB4074588 (OS Build 16299.248)

Right Click it. Uninstall it. DO NOT REBOOT YET.

Windows Key + R

ms-settings:

Click OK

Click Windows Update

Scroll way down to the bottom

There are possibly 3 options

Change them all to the max number of days

365 days for top option

30 days for security updates option

Pause updates (slider bar to turn it on)

None of this is recommended by Microsoft for Security purposes

All of it is recommended by MILE Technologies (us) for functionality and business continuity.

Reboot

Method 2: (if Method 1 does not work)

Windows Key + R

rstrui

Click OK

Restore to a date before the Windows Update

Windows Key + R

ms-settings:

Click OK

Click Windows Update

Scroll way down to the bottom

There are possibly 3 options

Change them all to the max number of days

365 days for top option

30 days for security updates option

Pause updates (slider bar to turn it on)

None of this is recommended by Microsoft for Security purposes

All of it is recommended by MILE Technologies (us) for functionality and business continuity.

Reboot

Method 3: (if Method 1 or 2 doesn't appeal or work)

Windows Key

cmd  (just type cmd without thinking and the following will happen)

Command Prompt will become visible (Right Click it and choose Run As Administrator)

dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

Press Enter (Return)

It will ask you to reboot ANSWER NO for now.

Windows Key + R

ms-settings:

Click OK

Click Windows Update

Scroll way down to the bottom

There are possibly 3 options

Change them all to the max number of days

365 days for top option

30 days for security updates option

Pause updates (slider bar to turn it on)

None of this is recommended by Microsoft for Security purposes

Reboot

Method 4: (last resort if all heck breaks loose)

Crash the computer a few times on purpose

Get to the Windows Automatic Repair screen

Advanced options

Command Prompt

dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

Press Enter (Return)

It will ask you to reboot ANSWER Yes

After reboot, you may have to remove the update again using Method 1

This is almost the same fix for INACCESSIBLE BOOT DEVICE from another package name Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.214.1.17 as well and January issues from another package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 Use these using Method 4 and substitute these package names for the one listed in Method 4.

There have been an instance that repeats the issue another user had called STOP 0xc000021a where a system restore caused this issue. I think that was caused by running a system restore PRIOR to a completion of a successful patch update. That's why the reboot first option is best.

Having the same issue, 2 PCs today lost mouse and/or keyboard functionality as a result of KB4074588. 1 Dell, 1 HP. The only common denominator that I know of currently is that both have Samsung 850 EVO SSD's. 

This is the second Windows 10 buggy update in a few weeks that has crippled multiple PCs, the other being KB4056892. Did they just stop testing updates over there?

UPDATE: Restoring the system to pre-KB4074588 brought USB functionality back. In both cases I then reinstalled KB4074588 via Windows Update and did not experience the issue again.

UPDATE2: It happened on a 3rd PC, same HP model as before but this one has a Hitachi HTS723232A7A365 HDD, so nothing to do with the Samsung SSDs. I removed KB4074588 and rebooted only to get the INACCESSIBLE_BOOT_DEVICE error. I had to do a system restore to several days ago to get it to boot. Once booted Windows Update reinstalled updates, including KB4074588. Mouse/keyboard were working normally after that.

UPDATE3: 4th PC affected. Uninstalled KB4074588 and rebooted successfully. Reinstalled updates including KB4074588 and USB ports were working again.

Just an FYI, on this not being an isolated incident. I had this problem last week. It specifically nuked my external USB keyboard and mouse. The system is a Lenovo T530 laptop. Other USB devices (e.g. cameras, IPad, 4 port hub) all worked correctly. I swapped out the keyboard and the mouse with different hardware (Keyboard switched from Saitek->HP, mouse switched from Logitech->Dell) and went through a pretty exhaustive cycle of trying to update device drivers which was fruitless. Ultimately, uninstalling KB4074588 fixed the problem.

I also am finding the lack of user control over this process to be pretty unfortunate. Since I can't elect to not update, I'm now forced into realistically thinking about Windows as a ticking time bomb which I cannot rely on to function correctly on any given morning. I can't even turn of the broken thing which I uninstalled, it's already dying to apply itself again. I will eventually run out of options for delaying it. The bright side, if you want to call it that, is that I will know exactly how to remove it again instead of spending an entire day trying to get my system working correctly. Ubuntu is definitely on my short list as a more permanent solution if this type of nonsense keeps happening.

Solution for me, without having to uninstall the KB update, was found at this link:  

https://www.askwoody.com/forums/topic/report-of-the-win10-1709-cumulative-update-kb-4074588-disabling-usb-devices/#post-169133

I used a workaround to get the keyboard/mouse functioning again without uninstalling the KB 4074588.

Go into the Device-Manager and select manual driver update of the problematic device, then use the following path a source for the driverlocation: "%windir%\WinSxS"
 
After a few minutes the wizard installs a compatible HID-driver and the device works again.

This workaround is reboot/shutdown/userswitch persistent and works now for me since at least 24h.