To fix the “PL2303HXA Phased Out” error on Windows 11, you must bypass the modern driver (which intentionally blocks older chips) and force-install Prolific Driver Version 3.3.2.102 (released in 2008). After installation, you must use the Local Group Policy Editor to block Windows Update from automatically overwriting this legacy driver, otherwise, the “Code 10” error will return upon the next reboot.
1. Symptom Profile: The Manufacturer “Kneecap”
Users working with PLCs, GPS units, or Baofeng radios often find their hardware suddenly non-functional after a Windows update. Our forensic analysis identifies three specific indicators of this software-imposed block:
-
The “Yellow Triangle”: Device Manager shows a yellow exclamation mark under Ports (COM & LPT).
-
The Error String: The device description is replaced by the text: “PL2303HXA PHASED OUT SINCE 2012. PLEASE CONTACT YOUR SUPPLIER.”
-
Code 10 / Code 37: Opening the device properties reveals a “This device cannot start” warning, even though the hardware worked perfectly on previous builds.
2. Hardware Specifics: Identifying the Chipset
Before applying the fix, verify your Hardware ID to ensure you are dealing with a genuine or legacy Prolific chip.
-
Right-click Start > Device Manager.
-
Right-click the problematic device > Properties > Details.
-
Select Hardware Ids from the dropdown.
-
Confirm the following strings:
USB\VID_067B&PID_2303(Standard PL2303) orUSB\VID_067B&PID_04BB(I/O Data).
3. Under-the-Hood: Why the Driver is Failing
The root cause is not a hardware defect. Prolific (the chip manufacturer) updated their Windows 11 DCHU driver to perform a version check on the hardware’s internal microcode. If the chip is detected as a “legacy” model (HXA/XA) or a third-party clone, the driver refuses to initialize the ser2pl.sys routine.
Windows 11 25H2 and 26H1 have made this worse by tightening Enhanced Power Management and USB descriptor timing, which causes even some “supported” chips to fall into an unstable state.
4. Advanced Fix: The “Legacy Injection” Protocol
Step A: Clean Driver Purge
You must remove the “poisoned” driver from the Windows Driver Store entirely.
-
Open Command Prompt (Admin).
-
Type:
pnputil /enum-driversand find the Prolific driver entry (e.g.,oemXX.inf). -
Run:
pnputil /delete-driver oemXX.inf /uninstall /force(ReplaceoemXXwith your specific ID).
Step B: Manual Legacy Driver Installation
-
Download Prolific Driver v3.3.2.102 (2008) from a trusted archive.
-
Disconnect your USB-to-Serial adapter.
-
Run the installer. If it fails, use the “Browse my computer for drivers” option in Device Manager and select “Let me pick from a list”.
-
Choose the 2008 version from the list of available drivers.
Step C: Use Group Policy to Block Auto-Updates (Crucial)
Windows Update will try to “repair” this by installing the broken 2026 driver again.
-
Press
Win + R, typegpedit.msc, and hit Enter. -
Navigate to: Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.
-
Enable “Prevent installation of devices that match any of these device IDs”.
-
Click Show… and paste your Hardware ID (
USB\VID_067B&PID_2303).
5. Visual Asset List (Verify Your Fix)
To ensure your guide ranks high, include these 3 real-world screenshots:
-
Device Manager Error: Shot showing the “Phased Out Since 2012” string in the name field.
-
Driver Selection Window: Highlighting the choice between the 2026 “Phased Out” driver and the 2008 “Working” driver.
-
Group Policy Window: Showing the Hardware ID correctly entered into the restriction list.
Leave a comment below and let us know:
-
Which laptop model or motherboard are you using?
-
Did the manual driver install work, or did you find a different fix?
-
Are you noticing a performance boost in AI-enhanced apps like OBS or Adobe Premiere?
Your feedback helps other members of our community solve these annoying driver issues faster!
Read more: What is Intel AI Boost? How to Fix the Missing Driver in Device Manager
🚀 Stay Connected with TechReviewGuide
Don’t miss any of our future video tutorials or tech deep-dives—follow us on our official channels
-
YouTube: Subscribe to our Channel for hands-on reviews.
-
Facebook: Like our Page for the latest tech news.
Frequently Asked Questions (FAQ)
-
Why does my PL2303 adapter say “Phased Out Since 2012” on Windows 11?
This error occurs because Prolific (the chip manufacturer) has intentionally blocked older hardware versions (HXA/XA) in their newer Windows 11 drivers. To force the hardware to work, you must roll back to a legacy driver version from 2008.
-
Can I fix the PL2303 Code 10 error without a legacy driver?
No. Modern Windows 11 drivers are designed to detect “end-of-life” or “clone” chips and will automatically trigger the Code 10 error. The only functional solution is to use the v3.3.2.102 (2008) driver.
-
How do I stop Windows 11 from automatically updating my Prolific driver?
You must use the Local Group Policy Editor (gpedit.msc). Navigate to Device Installation Restrictions and enable the policy to prevent installation of devices that match your specific Hardware ID (USB\VID_067B&PID_2303).
-
Is the PL2303HXA chip compatible with Windows 11 25H2 or 26H1?
While not officially supported, the chip is physically capable of working. By following the “Legacy Injection” method and disabling driver updates, the chip functions perfectly on the latest Windows 11 builds.
-
What is the correct Hardware ID for a genuine Prolific PL2303 adapter?
The most common Hardware ID for these legacy chips is USB\VID_067B&PID_2303. You can verify this in Device Manager under Properties > Details > Hardware Ids.
