How to Completely Remove a SOLO Printer Driver from Windows
A step-by-step guide to returning a Windows PC to a clean state before reinstalling your SOLO label printer.
If you have ever removed a SOLO printer from Windows, plugged it back in, and watched Windows silently reattach the same faulty driver, you are not doing anything wrong. Removing a printer and removing its driver are two entirely different operations, and Windows only does the first one when you click “Remove device”.
The driver package itself stays behind in the Windows driver store, along with registry entries, spooler files and hidden device records. The moment the printer reappears on USB, Windows finds that package and reinstalls it automatically — including whatever was wrong with it.
This guide covers both the quick method, which resolves most cases, and the full teardown for when you need the machine genuinely clean.
When you need this
- A driver has become corrupted and reinstalling on top of it changes nothing
- You are moving from one label software package to another and want no legacy drivers interfering
- Print output is wrong in a way that survives a reinstall
- Two identical printers have swapped identities and you want to rebuild both cleanly
- You are preparing a test machine and need it in a true “never seen this printer” state
Before you start
- Disconnect the SOLO printer from USB. Leave it unplugged until the very end.
- Log in as a local administrator. Several of these steps will fail silently without it.
- Open PowerShell as administrator — right-click the Start button and choose Terminal (Admin) or Windows PowerShell (Admin).
- Set a System Restore point if you intend to follow the full teardown. Steps 7 and 8 touch the registry and device records.
NOTE: Section 7 involves editing the Windows registry. Incorrect edits can prevent Windows from starting. Export a backup of each key before deleting anything, and if you are not comfortable in RegEdit, stop after Section 6 — that is sufficient for the overwhelming majority of cases.
NOTE: Positive ID Labels accept no responsibility for any damage to your system undertaking the proposed actions in this guide.
Part 1 — The quick method
Try this first. It resolves most driver problems and takes about two minutes.
1. Remove the printer
Go to Settings → Bluetooth & devices → Printers & scanners. Click the SOLO entry, then Remove.
2. Remove the driver package
Press Win + R, type the following and press Enter:
printui /s /t2
This opens the Drivers tab of Print Server Properties directly. Select the SOLO driver in the list and click Remove. Choose Remove driver and driver package — not just “Remove driver” — then click OK. The package option deletes the actual files rather than only the association.
3. If it says the driver is in use
Press Win + R, type services.msc, find Print Spooler, right-click and choose Stop. Retry step 2, then Start the spooler again afterwards.
4. Reboot, then reinstall
Restart the PC before installing the new driver. This clears anything still cached in memory.
If the reinstall now behaves correctly, you are done. If Windows still picks up the old driver, continue to Part 2.
Part 2 — The full teardown
Work through these in order.
1. Uninstall the bundled software
Go to Settings → Apps → Installed apps and remove any of the following that are present:
- Label Direct
- Direct Print
- TSC Console / TSC Printer Utility / DiagTool
- Seagull Scientific drivers (listed as “Drivers by Seagull”) (You can download a copy for reinstallation here: Seagull Driver Set)
- BarTender, if it was installed alongside
2. Remove all printer queues
Settings → Bluetooth & devices → Printers & scanners. Remove every SOLO and TSC entry, including any that look stale or unused — entries such as “TSC TDP”, “TTP” or older model names left over from previous installations.
3. Stop the print spooler
In your elevated PowerShell window:
net stop spooler
Leave the window open. You will restart the spooler at the end.
4. Strip the driver packages from the driver store
This is the step most people miss. The “Remove” button in Settings only removes the print queue. The driver package remains in C:\Windows\System32\DriverStore\FileRepository, and Windows will rebind to it as soon as the printer is reconnected.
List every third-party driver package:
pnputil /enum-drivers
Scroll through the output and note the Published Name (oem##.inf) of any entry whose Original Name, Provider or Class mentions TSC, Seagull, SOLO, or “Drivers by Seagull”. Then remove each one in turn:
pnputil /delete-driver oem47.inf /uninstall /force
Substitute the correct oem##.inf number each time. The /force flag is needed because some packages remain marked as in use until the next reboot.
5. Remove the drivers via Print Management
Run printmanagement.msc. Expand Print Servers → [your PC] → Drivers.
Right-click each TSC, SOLO or Seagull entry and choose Remove Driver Package — not “Remove Driver”. Only the package option deletes the underlying files.
If this step refuses to run because the spooler is stopped, start it with net start spooler, complete the removals, then stop it again before moving on.
6. Clear leftover spooler and driver files
With the spooler stopped, clear the following:
| Location | What to remove |
|---|---|
C:\Windows\System32\spool\PRINTERS\ | All contents (stuck print jobs) |
C:\Windows\System32\spool\drivers\x64\3\ | TSC and Seagull DLLs, plus any subfolder named after a SOLO model. Leave the generic Microsoft files alone. |
C:\ProgramData\Seagull\ | Whole folder, if present |
C:\Program Files\Seagull\ | Whole folder, if present |
C:\Program Files (x86)\Seagull\ | Whole folder, if present |
C:\Program Files (x86)\Label Direct\ | Whole folder, if Step 1 left it behind |
C:\Program Files (x86)\Direct Print\ | Whole folder, if Step 1 left it behind |
7. Clean the registry
Open regedit. Use Ctrl+F to search for TSC, then Seagull, then SOLO, then your specific model name.
Delete matching entries only beneath these keys:
- HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\
- HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\
- HKLM\SYSTEM\CurrentControlSet\Enum\USBPRINT\
- HKLM\SYSTEM\CurrentControlSet\Enum\USB\
Under the final USB key, only remove the entry matching your printer’s hardware ID. To confirm which that is, plug the printer in briefly, open Device Manager, find the device, and check Properties → Details → Hardware Ids. The value takes the form USB\VID_xxxx&PID_xxxx. Match that exactly rather than guessing — deleting the wrong entry will break an unrelated USB device.
Right-click each key and choose Export to save a .reg backup before deleting it.
8. Purge ghost devices
Hidden device records can hold a driver binding even after everything above. In an elevated Command Prompt:
set devmgr_show_nonpresent_devices=1 devmgmt.msc
In Device Manager, choose View → Show hidden devices. Check under Printers, Print queues, Software devices and Universal Serial Bus controllers for greyed-out TSC or SOLO entries.
Right-click each one → Uninstall device → tick Delete the driver software for this device → confirm.
9. Restart the spooler and reboot
net start spooler
Then restart the PC.
Verifying the machine is clean
After the reboot, check both of the following:
- Settings → Printers & scanners shows no SOLO or TSC entries
pnputil /enum-driversreturns nothing referencing TSC, Seagull or SOLO
Then plug the printer back in. On a genuinely clean machine it will appear in Device Manager under Software devices, or as an unrecognised USB device — it should not bind to a driver automatically. That is the correct starting point for a fresh manual installation.
If it does bind automatically, a driver package survived Section 4. Run pnputil /enum-drivers again and look more carefully at the Provider column.
A faster approach if you do this regularly
If you are an IT provider, reseller, or you rebuild machines often, running this teardown by hand every time is a poor use of an afternoon. Two alternatives are worth setting up once:
Windows Sandbox — included with Windows 10 and 11 Pro. It gives you a disposable Windows desktop that resets completely when you close it. Enable it under Turn Windows features on or off. Ideal for testing an installation procedure repeatedly.
A virtual machine with snapshots — VirtualBox or Hyper-V lets you take a snapshot of a clean Windows install and roll back to it in seconds. You will need USB pass-through configured to reach the printer, which in VirtualBox means installing the Extension Pack.
Both require hardware virtualisation to be enabled in the machine’s BIOS/UEFI. If Sandbox or your VM software refuses to start, that is almost always the cause — look for a setting named Intel VT-x, Intel Virtualization Technology, SVM Mode or AMD-V in the BIOS, usually under Advanced, CPU Configuration or Security. Note that on corporately managed machines this setting may be locked by IT policy.
Reinstalling your SOLO printer
With the machine clean, follow the standard installation procedure: install the driver package first, with the printer disconnected, then connect the printer over USB when prompted. Installing in that order is what allows Windows to bind the correct driver on first detection.
Need a hand?
If you are a customer and have worked through this and the printer still is not behaving, get in touch with our technical support team – including the printer model and a note of which steps you have already completed- and you will get an answer considerably faster.