USB ports on a Nitro V15 that stop working are most often a Windows or driver issue before they are a hardware one. If a port stops recognizing devices after a sleep, or after an update, the cause is frequently USB selective suspend, a Windows power-saving feature that turns ports off to save energy and sometimes fails to turn them back on. Turn it off in Power Options, Change plan settings, Advanced settings, USB settings. Uninstalling the USB controllers in Device Manager and restarting makes Windows rebuild them. Test with a second device and a second port to learn whether the fault is the device or the port.
A port that never works, or that is loose, is a hardware issue; if only one port fails, try the others and note which one. A power reset, with the charger unplugged and the power button held for thirty seconds, also clears stuck controllers. If the ports work at the BIOS but not in Windows, the cause is software, and if a keyboard on the port does not respond in the BIOS, the port or board is at fault. A device that draws a lot of power, such as an external hard drive, can also fail on a port when the laptop is on battery, so test with the charger connected.
Differential
Likely causes of “Acer Nitro V 15 USB or Thunderbolt device is not recognized”, and how to tell them apart
- 1
USB selective suspend
What separates it Ports stop working after sleep
How to confirm Power Options, Advanced settings, USB settings, selective suspend: Disabled
- 2
A USB controller glitch
What separates it No device is recognized on any port
How to confirm Uninstall the USB controllers in Device Manager and restart
- 3
A bad cable or device
What separates it Only one device fails
How to confirm Try another cable and device
- 4
Stored power
What separates it Ports fail after a crash
How to confirm Unplug, hold the power button for thirty seconds and restart
- 5
A damaged port
What separates it The plug is loose or no port works
How to confirm Contact Acer service
Before you touch a setting
Record this first — changing settings destroys the evidence
- Which ports fail
- Whether it began after sleep or an update
- Whether a second device works
- The model number
Try in this order
0 of 8 completedTest a second device
ReversibleUse a known-good USB device.
Try another port
ReversibleNote which ones work.
Disable selective suspend
ReversiblePower Options, Change plan settings, Advanced, USB settings.
Reinstall the controllers
ReversibleDevice Manager, Universal Serial Bus controllers, uninstall and restart.
Do a power reset
ReversibleUnplug, hold power for thirty seconds.
Update the BIOS and chipset driver
ReversibleFrom Acer's support page.
Test in the BIOS
ReversiblePress F2 at the logo and see whether a USB keyboard works there; if it does, the ports are fine and Windows is the issue.
Test on the charger
ReversiblePlug in the original adapter, because power-hungry devices can fail on battery power.
Model-specific
What is true of this model and not of its siblings
- Selective suspend
- A power-saving feature that can fail to wake ports.
- One port or all
- All ports failing suggests software; one port suggests hardware.
- Charge-only cables
- Some USB cables carry power but no data, which looks like a dead port, so try a cable known to transfer files.
- Front and rear ports
- The Nitro has ports on both sides and sometimes at the rear, and one can fail while the others work.
- Hubs and docks
- A bus-powered hub can overload a port, so test the device directly first.
Stop boundary
When this stops being a self-service repair
- !If every port fails after the controller reinstall and a power reset, contact Acer
- !If a port is loose, it needs repair
- !A burning smell means stop
Evidence ledger
Sources behind this answer
Exact questions
Common questions
Why do my USB ports stop after sleep?+
Selective suspend.
How do I rebuild the USB drivers?+
Uninstall the controllers and restart.
What if only one port fails?+
It may be a hardware fault on that port.
Will a power reset help?+
It clears stuck controllers.
Why does my USB drive not appear?+
A charge-only cable, a driver glitch or a dead port; test another cable and port.