-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Operating Systems and Recovery
- Re: no USB driver after windows update

Create an account on the HP Community to personalize your profile and ask a question
03-16-2018 06:32 PM
Unfortunately, I have no way of getting into Windows to download the update or remove the bad update because my USB ports are disabled.....no keyboard or mouse???
Solved! Go to Solution.
Accepted Solutions
03-20-2018 07:03 PM
"md",
You are awesome! I FINALLY GO IT RIGHT, and it worked. Now I am trying to get my computer caught up on Windows Updates. Thank you and everyone else on the Forum for their patience and consideration.
BenM3
03-16-2018 11:18 PM
You are not the first person to report those symptoms.
See: Mouse & Keyboard stop working after Windows Update (February 2018)
which includes a Microsoft-recommended "workaround".
Immediately after doing the workaround, run Windows Update -- Microsoft issued an update on March 13, 2018 to prevent a reoccurrence.
-----------
Welcome to this forum.
Please click the purple/white "Thumbs Up" icon for every response that is helpful.
Also, please click "Accept As Solution" for the best response.
03-16-2018 11:29 PM
Your keyboard should work to boot into Recovery Environment. Immediately after powering on start tapping the Esc key. From the menu tap F11 for Recovery. At the recovery screen, select Troubleshoot, then Advanced Options, and then Command Prompt.
Use Method 2 here to use Command prompt:
**Click Accept as Solution on a Reply that solves your issue**
***Click the "YES" button if you think this response was helpful.***
03-18-2018 08:09 PM - edited 03-18-2018 08:16 PM
You did use the string under "For 64-bit versions of Windows"? You might also replace C with D in case your Windows partition is actually designated as D when booting into recovery environment.
You could also try a System Restore from the Advanced Options menu. Choose a date before the latest update messed up your usb ports.
**Click Accept as Solution on a Reply that solves your issue**
***Click the "YES" button if you think this response was helpful.***
03-19-2018 03:06 AM - edited 03-19-2018 03:14 AM
> The Microsoft workaround using the C prompt failed. I got an error message ....."An error occurred trying to open - Package_for_RollupFix~....Error:14098
Computers are picky. The syntax of what Microsoft tells you to type is very strict.
Get it slightly wrong, and the computer will complain.
Be sure to have at least one "blank" before each "slash".
It's best to "copy-and-paste" from the Microsoft document into NOTEPAD, and then to "join" multiple lines into one line, and then to "copy-and-paste" from NOTEPAD into the command-line prompt.
_________________
In the Command Prompt window, type the command listed below for your version of Windows and press ENTER.
For 32-bit versions of Windows:
dism.exe
/image:c:\
/remove-package
/packagename:?Package_for_RollupFix~31bf3856ad364e35~x86~~16299.248.1.17
For 64-bit versions of Windows:
dism.exe
/image:c:\
/remove-package
/packagename:?Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17
NOTE: Remove the "?" -- a bug in this forum's "rich-text" functionality messes up what I type.
Note: If Windows is not stored on the C: drive, replace the C: in the above commands with the appropriate drive letter.
03-19-2018 07:51 PM
I carefully reentered the code (didn't know how to copy and paste since I only have access to windows recovery ) but I believe I entered it correctly but the code still failed. I opened the log and was able to copy and paste the result.
Thank you for your help!
BenM3
2018-03-19 21:12:32, Info DISM DISM.EXE: Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=8
2018-03-19 21:12:32, Info DISM DISM.EXE: Dism.exe version: 10.0.16299.15
2018-03-19 21:12:32, Info DISM DISM.EXE: Executing command line: dism.exe /image:c\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Warning DISM DISM Provider Store: PID=1640 TID=1628 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-03-19 21:12:32, Warning DISM DISM Provider Store: PID=1640 TID=1628 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-03-19 21:12:32, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2018-03-19 21:12:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2018-03-19 21:12:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2018-03-19 21:12:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2018-03-19 21:12:32, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2018-03-19 21:12:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2018-03-19 21:12:32, Info DISM DISM Provider Store: PID=1640 TID=1628 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-03-19 21:12:32, Error DISM FolderManager: PID=1640 onecore\base\ntsetup\opktools\dism\providers\folderprovider\dll\folderimage.h:190 - CFolderImage::CreateFolderImage(hr:0x80070032)
2018-03-19 21:12:32, Info DISM DISM FFU Provider: PID=1640 TID=1628 [X:\windows\system32\c\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2018-03-19 21:12:32, Info DISM DISM WIM Provider: PID=1640 TID=1628 [X:\windows\system32\c\] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-03-19 21:12:32, Info DISM DISM VHD Provider: PID=1640 TID=1628 [X:\windows\system32\c\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-03-19 21:12:32, Info DISM DISM FFU Provider: PID=1640 TID=1628 [X:\windows\system32\c\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2018-03-19 21:12:32, Info DISM DISM Imaging Provider: PID=1640 TID=1628 The provider FfuManager does not support CreateDismImage on X:\windows\system32\c\ - CGenericImagingManager::CreateDismImage
2018-03-19 21:12:32, Info DISM DISM VHD Provider: PID=1640 TID=1628 [X:\windows\system32\c\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-03-19 21:12:32, Info DISM DISM Imaging Provider: PID=1640 TID=1628 The provider VHDManager does not support CreateDismImage on X:\windows\system32\c\ - CGenericImagingManager::CreateDismImage
2018-03-19 21:12:32, Info DISM DISM WIM Provider: PID=1640 TID=1628 [X:\windows\system32\c\] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-03-19 21:12:32, Info DISM DISM Imaging Provider: PID=1640 TID=1628 The provider WimManager does not support CreateDismImage on X:\windows\system32\c\ - CGenericImagingManager::CreateDismImage
2018-03-19 21:12:32, Info DISM DISM Imaging Provider: PID=1640 TID=1628 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2018-03-19 21:12:32, Error DISM DISM.EXE: Failed to access the image folder or image's windows folder.
03-19-2018 09:22 PM
If not successful again- try System Restore from the Advanced menu. If that fails also try a Reset on the Troubleshoot window.
**Click Accept as Solution on a Reply that solves your issue**
***Click the "YES" button if you think this response was helpful.***
03-20-2018 07:03 PM
"md",
You are awesome! I FINALLY GO IT RIGHT, and it worked. Now I am trying to get my computer caught up on Windows Updates. Thank you and everyone else on the Forum for their patience and consideration.
BenM3