The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →If a device stopped working immediately after Windows updated, start with the device itself—not a generic driver-downloader. Open Device Manager, locate the affected hardware, and read its status or error code. That evidence tells you whether to roll back a recent driver, update or reinstall it, or obtain a compatible package from the hardware maker.
The same symptom can have different causes. A graphics device showing code 43, audio that disappeared after an update, a flickering display, and an update that fails with 0xC1900101 each require a different route. The steps below separate those cases and keep the least risky remedy first.
As an Amazon Associate I earn from qualifying purchases.
Start with the device and its Device Manager status
Before changing anything, write down what failed, when it failed, and whether Windows Update finished successfully. “The driver stopped working” is not a diagnosis. A named device and a status code are much more useful.
Open Device Manager
- Right-click the Start button and select Device Manager.
- Expand the category for the failed hardware: Display adapters for graphics, Sound, video and game controllers for audio, Network adapters for Wi-Fi or Ethernet, Printers for printers, or the relevant category for another device.
- Look for a yellow exclamation point, a device listed as unknown, or a device that has disappeared.
- Right-click the device, choose Properties, and read the message on the General tab. Record the code and the exact device name before proceeding.
Microsoft identifies a yellow exclamation point as a common sign of a device problem. The code and wording determine which remedy is sensible; do not uninstall several unrelated drivers simply because one device is failing.
#1 Best Overall
- Complete All-in-One Dual USB-A & USB-C System Toolkit – boot, repair, recover, reinstall, reset forgotten Windows or Linux passwords, restore files, access locked systems, run LIVE/install best Linux OS systems - all from one ultra-fast 128 GB USB 3.0 drive loaded with premium Linux and Windows utilities.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Powered by the most powerful Multi-Boot Manager – easily launch dozens of OS and recovery tools without reformatting. Works with laptops, desktops, mini-PCs, Windows tablets and other modern USB-C devices — no adapters or setup required.
- Includes 31+ OS & Utilities (x86-64 & ARM64) – Linux Ubuntu, Kali, Mint, Tails, retro-gaming emulator - Batocera (ready to play), Garuda, Fedora, openSUSE, Solus, CAINE Digital Forensics, 3D printing and engineering Linux OS, Windows Installers, DriverPacks, Antivirus Rescue Disks, and much more!
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Determine which failure you actually have
A device broke after Windows installed successfully
If Windows reached the desktop normally and the hardware failed afterward, investigate a driver change or a device-specific problem. Ask whether the affected driver was updated at the same time. If the timing matches a driver update and a previous version exists, rollback is the most targeted first move.
Windows Update itself failed
An update that never completes is a different case from a device that broke after a successful update. Microsoft associates error 0xC1900101 with an incompatible driver causing the Windows installation to fail. Treat that as an update-installation problem: remove or update the incompatible hardware driver identified by the setup diagnostics, then retry the upgrade. Do not assume that every 0xC1900101 incident means Windows replaced a working driver after the update.
The device has a specific Device Manager code
Codes are diagnostic labels, not measurements of how severe a problem is. Microsoft maintains a code-specific table because the recommended action varies by code. Use that guidance when the status is not code 43, rather than applying a single “reinstall everything” recipe.
Use this remedy ladder
Choose the first option that matches the evidence. The table compares the practical decision points.
| Remedy | Use it when | Requirements and limits |
|---|---|---|
| Roll Back Driver | The problem began after a recent driver update and the Driver tab offers a previous version. | Administrator permission is required. The button can be unavailable when Windows has no earlier driver to restore. |
| Update driver | Rollback is unavailable or the installed driver is old, damaged, or incompatible. | Device Manager can search automatically; Windows Update is Microsoft’s normal recommended route for driver updates. |
| Uninstall and reinstall | The driver installation is corrupted or an update did not repair the device. | Restart after uninstalling. Windows will attempt to reinstall; some devices, including certain printers, need manual setup. |
| Manufacturer package | Windows cannot find a compatible driver or the device needs a model-specific package. | Use the hardware maker’s official support site and match model, Windows release, and system architecture. |
1. Roll back a driver when the timing fits
Rollback is designed for a regression that follows a driver change. It restores the previous package instead of introducing another variable.
- In Device Manager, right-click the affected device and select Properties.
- Open the Driver tab and select Roll Back Driver.
- Choose a reason when Windows asks, then confirm.
- Restart if Windows prompts you, and test the same operation that originally failed.
You must have administrator rights. If Roll Back Driver is missing or disabled, Windows may not retain a previous version; it does not indicate that you have overlooked a hidden setting. Move to an update or reinstall instead. Microsoft notes that when an issue follows a Windows Update, reinstalling the previous driver often resolves it.
2. Update the driver through Windows
When there is no usable rollback, let Windows look for a compatible package before downloading anything manually.
Rank #2
- Supports UEFI and Legacy BIOS boot on many PCs and laptops. If boot issues occur, check Secure Boot settings and use the included boot instructions.
- Complete All-in-One Dual USB-A & USB-C System Toolkit – boot, repair, recover, reinstall, reset forgotten Windows or Linux passwords, restore files, access locked systems, run LIVE/install best Linux OS systems - all from one ultra-fast 128 GB USB 3.0 drive loaded with premium Linux and Windows utilities.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Powered by the most powerful Multi-Boot Manager – easily launch dozens of OS and recovery tools without reformatting. Works with laptops, desktops, mini-PCs, Windows tablets and other modern USB-C devices — no adapters or setup required.
- Includes 31+ OS & Utilities (x86-64 & ARM64) – Linux Ubuntu, Kali, Mint, Tails, retro-gaming emulator - Batocera (ready to play), Garuda, Fedora, openSUSE, Solus, CAINE Digital Forensics, 3D printing and engineering Linux OS, Windows Installers, DriverPacks, Antivirus Rescue Disks, and much more!
- In Device Manager, right-click the device and choose Update driver.
- Select Search automatically for drivers.
- Allow the search to finish and follow any installation prompts.
- Restart Windows if requested, then check the device in Device Manager again.
Windows Update remains Microsoft’s recommended normal path for hardware-driver updates. You can also open Settings > Windows Update and select Check for updates, but an update shown there may not be the same package as the one supplied by the device manufacturer. If Windows reports that the best driver is already installed while the device still has an error, continue to reinstall or use the official manufacturer package rather than repeatedly clicking Search.
3. Reinstall one affected device
Reinstallation is appropriate when the driver files or registration are damaged. Target only the device that is failing.
- In Device Manager, right-click the affected device and select Uninstall device.
- Confirm the removal. If Windows offers a checkbox to remove the driver package, read the prompt carefully; removing a package can leave the device without a fallback until a new one is installed.
- Restart the computer.
- After restart, check Device Manager. Windows attempts to detect the hardware and reinstall a driver automatically.
- If it does not, return to Device Manager and use Action > Scan for hardware changes, or install the correct package from the manufacturer’s official support page.
Microsoft cautions that some devices, such as printers, may require manual installation after an uninstall. Keep a working network connection available if the replacement driver must be downloaded, and do not remove unrelated network, storage, chipset, or input drivers as a general cleanup exercise.
4. Install a driver from the hardware maker safely
Use a manual package when Windows cannot locate a compatible version or when the manufacturer publishes a fix for your exact model. Microsoft explicitly advises avoiding driver-download websites other than the manufacturer’s official site.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Identify the exact PC or device model from its label, firmware screen, or the manufacturer’s support utility.
- Confirm the Windows release you run and its architecture, such as 64-bit x64 or ARM64. A package for a different release or architecture can fail to install or create a new malfunction.
- Download the driver only from the manufacturer’s official support page. Prefer a package that names your model and Windows version.
- Read the release notes for prerequisites, required restarts, and whether an older driver must be removed first.
- Run the installer as an administrator when requested, restart, and verify the Device Manager status.
If the support page offers several packages, do not choose by date alone. The newest file may not support an older Windows release or a particular hardware revision. When the model, operating system, or architecture is unclear, contact the manufacturer’s support channel instead of guessing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Route the fix by symptom and code
Graphics device showing error code 43
Microsoft’s code 43 guidance applies to graphics hardware that reports to Windows that it is not working properly. In Device Manager, expand Display adapters, open the device’s properties, and confirm the code. Follow the rollback, update, or reinstall sequence above, testing after each restart. A yellow exclamation point beside the adapter supports this route; it does not identify which of the three remedies will work.
Screen flickering
Use Task Manager to separate an application problem from a display-driver problem. Press Ctrl+Shift+Esc to open Task Manager and observe whether its window flickers too. If Task Manager remains stable while the rest of the screen flickers, an application or shell component is more likely. If Task Manager flickers as well, investigate the display driver and any recent Windows or graphics-driver change. Microsoft lists rollback as an option when the timing points to a recent update and administrator permission is available.
Rank #3
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Audio stopped working after a Windows update
Microsoft’s audio guidance lists an incompatible audio driver and audio services that failed to start as possible causes. In Device Manager, inspect the audio device first; then try rollback, update, or reinstall according to the remedy ladder.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the driver looks healthy but sound is still absent, restart the relevant services:
- Press Windows key + R, type
services.msc, and press Enter. - Find Windows Audio, right-click it, and choose Restart.
- Do the same for Windows Audio Endpoint Builder.
- Test the selected output device again in Settings > System > Sound.
The audio support page notes that Windows 10 support ended on October 14, 2025. That lifecycle notice does not mean every Windows edition or every device has the same support status; check the release and hardware maker’s support information that applies to your system.
Windows Update fails with 0xC1900101
When setup stops with 0xC1900101, start with the update failure’s diagnostic details and identify the incompatible driver, often in network or graphics hardware. Update or replace that specific driver through Device Manager or the manufacturer’s official site, disconnect unnecessary peripherals if the setup instructions call for it, and retry the update. This workflow addresses a blocked installation; it is not proof that a post-update driver replacement caused a later device failure.
Another Device Manager code
Open Microsoft’s “Error codes in Device Manager in Windows” guidance and use the entry matching your code. Some codes indicate disabled hardware, missing resources, or a device that Windows cannot enumerate; applying the graphics code 43 procedure to those cases can waste time or remove a working fallback.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What to check after each change
- Device Manager no longer shows the warning icon or reports a specific error.
- The device appears in the application that uses it: a network list, Sound settings, display configuration, printer queue, or input panel.
- The original failure can be reproduced safely, such as playing a test sound, opening a known display workload, or printing a test page.
- Windows Update still completes normally if the original incident involved an update.
- The driver version and date now shown on the Driver tab match the package you intended to install.
If a change makes the situation worse, return to Device Manager and use Roll Back Driver when it becomes available, or reinstall the previously downloaded official package. Keep notes of each version and restart so you can tell which change altered the behavior.
Common mistakes that prolong the problem
- Changing drivers before identifying the device: a vague symptom can come from hardware, services, an application, or Windows setup rather than the driver.
- Rolling back without matching the timeline: rollback is useful after a driver change, not as a universal response to every update-related complaint.
- Removing a broad group of drivers: uninstall only the affected device; removing network or storage drivers can make recovery harder.
- Using third-party driver sites or “driver updater” utilities: they can supply the wrong model or architecture. Microsoft recommends the manufacturer’s official site.
- Ignoring administrator permission: rollback and installation actions can fail or be unavailable without an administrator account.
- Confusing update failure with post-update failure: 0xC1900101 identifies an incompatible driver blocking setup, while code 43 describes a graphics device reporting that it is not working properly.
When software steps do not resolve it
If the correct manufacturer driver, a clean reinstall, and an appropriate rollback leave the same code, document the device model, Windows release, driver version, and exact status message for the manufacturer’s support team. A persistent code after a known-good package can indicate firmware, connection, power, or physical hardware trouble that a Windows driver change cannot repair. The evidence from Device Manager helps support distinguish those possibilities without repeatedly reinstalling the same software.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
