Resolve slow Windows startup caused by a proven third-party driver or package

Windows starts successfully but takes materially longer than its established baseline. Two confirmed cases tied the delay to a Realtek audio component: removing a Realtek audio application/package reduced one system's boot time from about 60 seconds to about 15 seconds, and removing a Realtek USB Audio driver restored normal Windows 11 restart behavior on another system.

The transferable mechanism is not “Realtek is always bad.” It is that a specific third-party package, service, device, or driver can delay startup, and a controlled removal or rollback can prove it. This page requires before/after timing and exact component identification. It does not authorize bulk driver removal.

Searchable Windows error codes and exact messages

The absence of an error code is normal in a performance case. Exact elapsed time, component name, driver provider/version, and repeatable before/after result are more useful than a guessed stop code.

Use this procedure when:

• Windows eventually reaches a usable desktop;
• the delay is reproducible on the same transition—Restart, full shutdown and power-on, or sign-in;
• a specific third-party package, service, device, or driver is nominated by timing, update history, clean-boot isolation, an event, or a device-disable comparison;
• the exact component can be recorded and restored; and
• at least two comparable baseline and post-change trials can be run.

The Realtek branches apply only when the machine actually contains a Realtek audio application or Realtek/Realtek USB Audio device and the controlled test points to that component.

Do not use this procedure when Windows does not start, the drive disappears, firmware stalls, a stop code appears, Automatic Repair loops, the delay is caused by an update phase that says Working on updates, or the system is slow after reaching the desktop but startup time is normal.

It also does not apply when:

• the only evidence is that a driver is old;
• the package name resembles a component from another computer;
• a clean boot made no difference and disabling the exact device made no difference;
• the suspected component is a storage, chipset, encryption, display, keyboard, network, or other essential device whose safe substitution has not been planned;
• the system uses specialized audio routing, digital-audio workstation hardware, OEM hotkeys, conferencing hardware, or accessibility audio that has not been backed up and tested; or
• Windows Update, firmware, or controller-mode changes are being proposed without direct evidence.

Do not generalize this article into “uninstall every Realtek driver.” Realtek network, card-reader, camera, and audio packages are distinct.

The precise function inside the driver that waited, the exact Windows build, and the reason an OEM shipped that package may remain unknown.

The following may not remain unknown before removal:

• the exact startup transition being timed;
• the component's Device Manager name and hardware ID;
• driver provider, version, date, and published INF name when applicable;
• the installed application/package name and publisher when applicable;
• whether the component supplies the computer's only working audio path;
• the location of an OEM-compatible replacement or exported current driver; and
• the result of a reversible comparison, such as clean boot, rollback, or temporary device disable.

An exact build becomes necessary only if the OEM driver package specifies a supported build range.

• Local administrator access
• Saved work, stable power, and a verified backup of important data
• A stopwatch and log for at least two baseline and two post-change starts
• The exact computer or motherboard model and hardware revision
• Access to the OEM support page or a locally saved compatible driver package
• Device Manager and an elevated Command Prompt
• A removable or non-system location with room for a new, unused attempt directory and a package-specific driver export
• A second audio path when audio is operationally critical
• A record of custom audio settings, enhancements, sample rate, channel mapping, and application selections

Do not delete a Driver Store package unless an exported copy or exact OEM replacement is available and the published INF is unambiguous.

1. Save work and disconnect nonessential USB audio devices, docks, capture devices, and headsets. Keep a device connected if it is the exact component being tested; record that fact.

2. Do not change firmware, storage mode, Secure Boot, BCD, or partitions.

3. Create a new, unused attempt folder before the first evidence write:

   set "EVID=%SystemDrive%\FixBackup\FIX-070\Attempt-01"
   if exist "%EVID%\" (echo STOP: choose the next unused Attempt number & exit /b 1)
   md "%EVID%" || exit /b 1
   echo FIX-070> "%EVID%\attempt-marker.txt"
   echo EVID=%EVID%>> "%EVID%\attempt-marker.txt"
   

   If Attempt-01 exists, change only the attempt number to the next unused value and record that exact path. Do not clear or merge an earlier attempt.

4. Record system and driver inventory:

   systeminfo > "%EVID%\systeminfo-before.txt"
   pnputil /enum-drivers > "%EVID%\third-party-drivers-before.txt"
   driverquery /v /fo csv > "%EVID%\driverquery-before.csv"
   

5. In Device Manager, open the suspected device's Properties > Driver page. Record the device name, provider, date, version, and whether Roll Back Driver is available. On Details, record Hardware Ids, Inf name, and Device instance path when available.

6. In Settings > Apps > Installed apps, record the exact related package name, publisher, version, and install date. Distinguish an application/package from the device driver.

7. Measure two ordinary Restarts and two full starts if both are affected. Start the timer at the same action and stop only when the same desktop application is usable.

1. Compare Restart with full shutdown and power-on. If only one is slow, preserve that distinction; use the same transition for all later trials.

2. Open Event Viewer and inspect Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational. Record Events 100 through 110 at the affected starts, especially any event naming the suspected application, driver, or service.

3. Because the baseline restarts clear environment variables, reset EVID to the exact recorded attempt and validate its marker before exporting the log:

   set "EVID=%SystemDrive%\FixBackup\FIX-070\<recorded-Attempt-NN>"
   findstr /x /l /c:"FIX-070" "%EVID%\attempt-marker.txt" >nul || (echo STOP: wrong attempt directory & exit /b 1)
   findstr /x /l /c:"EVID=%EVID%" "%EVID%\attempt-marker.txt" >nul || (echo STOP: attempt path does not match marker & exit /b 1)
   wevtutil epl Microsoft-Windows-Diagnostics-Performance/Operational "%EVID%\Diagnostics-Performance-before.evtx"
   

4. If a related application or service is suspected, perform a documented clean boot:

   • Open msconfig.
   • Select Services > Hide all Microsoft services.
   • Verify Microsoft services are hidden.
   • Disable the remaining third-party services.
   • Disable nonessential third-party Startup apps in Task Manager.
   • Restart and measure.

   If startup becomes normal, re-enable half the items at a time until the exact service or package is isolated. A clean boot does not remove a kernel driver; no improvement does not clear the driver branch.

5. If an exact nonessential audio device is suspected, temporarily disable only that device in Device Manager. Do not select Uninstall yet. Restart and measure the same transition.

6. Re-enable the device and repeat once. The driver/device hypothesis is supported when the delay disappears with the exact device disabled and returns when it is re-enabled.

7. If Roll Back Driver is available and the delay began immediately after that driver changed, record the current package and use rollback as the first corrective comparison. Restart and measure.

8. For a Realtek case, confirm that the selected entry is under Sound, video and game controllers, Audio inputs and outputs, or a clearly identified USB audio device. Do not select a Realtek network adapter, card reader, Bluetooth device, or unrelated system component.

9. Establish the evidence threshold. Proceed to removal only when at least two facts agree, such as:

   • the exact driver/package installation preceded the delay;
   • an event or trace names the same component;
   • clean boot isolates its service/application;
   • temporary device disable changes startup time; or
   • driver rollback restores the previous timing.

If no exact component meets this threshold, restore all test changes and stop. Windows Performance Recorder/Analyzer analysis or vendor support is the next step, not speculative uninstallation.

Choose one branch. Test after each branch; do not stack multiple removals before measuring.

Branch A — Remove only the proven companion application/package

1. Confirm the related device driver and OEM replacement are recorded.
2. Open Settings > Apps > Installed apps.
3. Select the exact proven package—for example, an OEM-listed Realtek Audio Console, Realtek Audio package, or vendor audio utility—and choose Uninstall.
4. Do not remove similarly named network, card-reader, or chipset packages.
5. Restart and run two timed trials.
6. Test speakers, microphone, headphone detection, Bluetooth/USB audio as applicable, volume controls, and communication applications.
7. If startup is normal and required audio functions work, leave the companion package removed unless the OEM documents it as required.
8. If functionality is missing, install the current compatible package from the exact computer or motherboard OEM and retest both audio and startup.

Branch B — Roll back the proven driver

1. Open Device Manager, right-click the exact device, and select Properties > Driver > Roll Back Driver.
2. Select the truthful reason and complete the rollback.
3. Restart when prompted.
4. Record the resulting driver version and run two timed startup trials.
5. If the previous driver restores normal timing and device function, retain it while checking the OEM's release notes for a corrected version.
6. If rollback makes no difference, use Roll Back Driver no further; return to the recorded current version or install the saved OEM package.

Branch C — Uninstall the device while retaining Driver Store rollback

1. In Device Manager, select the exact proven audio device and choose Uninstall device.
2. On the first test, do not select a checkbox that removes the driver package from the system, if such a checkbox is offered.
3. Restart. Windows may re-enumerate the device and reuse a Driver Store package.
4. Measure startup and inspect the newly selected driver version.
5. If Windows selects a generic or different compatible driver and startup becomes normal, test all audio functions.
6. If Windows reinstalls the same defective package and the delay returns, proceed to Branch D only with an unambiguous published INF and replacement package.

Branch D — Remove one proven third-party driver package from the Driver Store

1. Identify the exact published INF. Run:

   pnputil /enum-drivers
   

   Match Published Name, Original Name, Provider Name, Class Name, Driver Version, and Signer Name to the recorded device. Similar provider names are insufficient.

2. If this is a new command session, reset EVID to the exact recorded attempt path and validate the attempt marker. Then create a fresh, package-specific export directory; it must not already exist:

   set "EVID=%SystemDrive%\FixBackup\FIX-070\<recorded-Attempt-NN>"
   findstr /x /l /c:"FIX-070" "%EVID%\attempt-marker.txt" >nul || (echo STOP: wrong attempt directory & exit /b 1)
   findstr /x /l /c:"EVID=%EVID%" "%EVID%\attempt-marker.txt" >nul || (echo STOP: attempt path does not match marker & exit /b 1)
   set "DRVEXP=%EVID%\DriverExport-<exact-oem#.inf>"
   if exist "%DRVEXP%\" (echo STOP: package export directory already exists & exit /b 1)
   md "%DRVEXP%" || exit /b 1
   dir /a /b "%DRVEXP%" | findstr . >nul && (echo STOP: export directory is not empty & exit /b 1)
   pnputil /export-driver <exact-oem#.inf> "%DRVEXP%"
   if errorlevel 1 (echo STOP: PnPUtil export failed & exit /b 1)
   

3. Require PnPUtil to report a successful export. List every exported INF and save the list:

   dir /s /b "%DRVEXP%\*.inf" > "%EVID%\exported-INF-list.txt" || (echo STOP: no exported INF was found & exit /b 1)
   type "%EVID%\exported-INF-list.txt"
   

   Identify one exact restore INF inside this package-specific directory. Its file name must match the recorded Original Name, and its [Version] identity—provider/manufacturer references, class/class GUID, DriverVer, and catalog—must agree with the recorded published package. Confirm the referenced catalog and package files exist. Save the one verified full path as RESTORE_INF; do not use a wildcard:

   set "RESTORE_INF=<full-path-to-the-one-verified-exported-INF>"
   if not exist "%RESTORE_INF%" (echo STOP: verified restore INF is missing & exit /b 1)
   echo %RESTORE_INF%> "%EVID%\verified-restore-INF-path.txt"
   type "%RESTORE_INF%" > "%EVID%\verified-exported-INF.txt"
   

   Stop if no INF matches, more than one candidate remains, the export contains a different package, or its catalog/package files are incomplete.

4. Identify every device currently using that published INF before invoking /uninstall. In an elevated PowerShell window, replace the placeholder with the exact recorded name:

   Get-CimInstance Win32_PnPSignedDriver |
     Where-Object { $_.InfName -ieq 'oem##.inf' } |
     Select-Object DeviceName,DeviceID,InfName,DriverVersion,Manufacturer |
     Format-Table -AutoSize
   

   Save the output. Cross-check with pnputil /enum-devices /drivers when that switch is supported by the installed Windows build. /delete-driver ... /uninstall affects any devices using the package, not just the audio endpoint first selected. Continue only when every listed instance is understood and each required device has a verified compatible fallback or exact exported rollback package.

5. Remove only the matched package:

   pnputil /delete-driver <oem#.inf> /uninstall
   

6. Do not add /force. If Windows refuses because the package is in use or critical, stop and use the OEM-supported uninstall path.

7. Restart and measure twice.

8. If the device has no suitable driver, install the exact OEM replacement:

   pnputil /add-driver "<path-to-OEM-INF>" /install
   

   If the OEM supplies an installer rather than an exposed INF, use that signed installer instead.

9. Retest all affected devices, all audio functions, and Device Manager status.

• Clean boot fixes startup: a service or application is implicated; isolate it before touching drivers.
• Disabling the exact device fixes startup and re-enabling it restores the delay: the device/driver path is strongly implicated.
• Removing only the companion application fixes startup while audio works: keep the driver, leave the optional package removed, and document the result.
• Rolling back the driver fixes startup: retain the working version and defer the newer version until the OEM publishes a correction.
• Uninstalling the device causes Code 28 or no audio: install the saved OEM-compatible driver.
• Removal changes nothing: restore the package and continue performance tracing. Do not remove a second unrelated driver based on guesswork.
• A stop code, missing drive, or firmware stall appears: stop this performance article and route by the exact failure.

• Do not uninstall every Realtek component.
• Do not remove storage, chipset, ACPI, USB host-controller, display, keyboard, or network drivers to test an audio hypothesis.
• Do not use pnputil /delete-driver ... /force in this procedure.
• Do not install a generic driver chosen only by vendor name when the OEM customizes the hardware.
• Do not use third-party “driver updater” or registry-cleaner software.
• Do not change SATA/AHCI/RAID/VMD mode, firmware mode, Secure Boot, BCD, or partitions.
• Do not declare success from one fast boot; background maintenance can create a false result.
• Do not leave the computer in an undocumented clean-boot configuration.

1. Re-enable any device disabled during diagnosis.

2. Restore all clean-boot services and Startup apps that were not independently proven defective.

3. Reinstall the OEM package from the exact model's saved installer, or reset EVID to the exact recorded attempt, validate its marker, read verified-restore-INF-path.txt, and reinstall only that exact verified INF:

   set "EVID=%SystemDrive%\FixBackup\FIX-070\<recorded-Attempt-NN>"
   findstr /x /l /c:"FIX-070" "%EVID%\attempt-marker.txt" >nul || (echo STOP: wrong attempt directory & exit /b 1)
   findstr /x /l /c:"EVID=%EVID%" "%EVID%\attempt-marker.txt" >nul || (echo STOP: attempt path does not match marker & exit /b 1)
   type "%EVID%\verified-restore-INF-path.txt"
   set "RESTORE_INF=<exact-full-path-recorded-in-that-file>"
   if not exist "%RESTORE_INF%" (echo STOP: exact exported INF is missing & exit /b 1)
   pnputil /add-driver "%RESTORE_INF%" /install
   if errorlevel 1 (echo STOP: exact INF restoration failed & exit /b 1)
   

   Do not substitute *.inf, /subdirs, or a similarly named package. Confirm PnPUtil names the intended package and reports success before restarting.

4. Restart and confirm Device Manager shows the intended provider, version, and no unexpected problem code.

5. Restore application-specific audio settings from the record.

6. If the removed companion application is required, reinstall its OEM or Microsoft Store version and retest startup. A rollback that restores the delay confirms the relationship but does not justify leaving required functionality broken.

1. Run three trials of the same affected transition and calculate the median startup time.
2. Compare that median with the two-trial baseline.
3. Confirm no yellow warning icon or Code 10, 28, 31, 39, or 43 appears on the tested device.
4. Test speakers, microphone, headphones, volume controls, sleep/resume audio, and one communication application.
5. Review Diagnostics-Performance events for the three verification starts.
6. Confirm the intended driver provider/version and installed-app state.
7. Confirm all unrelated clean-boot items are restored.
8. Record the removed or retained package, exact published INF when applicable, before/after medians, and functional test results.

Bounded confidence: approximately 80% when the same exact component passes a disable/enable, rollback, or remove/restore comparison. Two OEM-community cases reported successful Windows 11 startup recovery after removing a Realtek audio package or Realtek USB Audio driver. Microsoft documentation confirms the Device Manager and PnPUtil command behavior. The project has not independently reproduced those machines, and the evidence does not justify applying the Realtek-specific action to unrelated slow-start systems.

Stop when the component cannot be identified unambiguously, no replacement driver exists, the device is operationally critical, the system is managed, the suspected package is storage/chipset/firmware related, Windows stops booting, or the first reversible comparison does not change the measured delay.