Windows System Errors
No More Items
0x80070103Reviewed for reference consistency: August 11, 2026
the enumeration reached its end and returned nothing further
What 0x80070103 Means
The 0x80070103 error on the Windows System Errors indicates no more items — the enumeration reached its end and returned nothing further. This typically occurs due to the driver-offering pass found no driver variant left to present for the device.
Enumerations end quietly — 0x80070103 is the HRESULT for Win32 error 259, ERROR_NO_MORE_ITEMS, whose official text is simply 'No more data is available'. In Windows Update discussions the code is overwhelmingly reported on driver deliveries: the update surface tries to install a driver for a device that already carries that driver, the offering pass finds nothing new to apply, and the result is recorded as a failed install.
How to fix 0x80070103
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
List the drivers the system actually offers
The third-party driver inventory shows which packages and versions exist, making offered-versus-installed comparisons direct.
pnputil /enum-driversCheck which devices report problems
A device whose driver is genuinely current reports no problem status, which separates cosmetic update noise from real driver damage.
Get-PnpDevice -PresentOnly | Where-Object Status -ne "OK" | Select-Object FriendlyName, InstanceId
Technical Background
The constant belongs to the enumeration family of low-range Win32 codes — WAIT_TIMEOUT (258) and ERROR_NO_MORE_ITEMS (259) sit together at the end of that range, marking boundaries rather than malfunctions. Read literally, 0x80070103 says the collection had nothing further, which is an outcome, not a fault.
The driver-update context gives the code its common visibility. Driver offers flow through the same pipeline as other updates, and when the device's installed driver already satisfies or exceeds the offered package, the delivery ends without an install to perform. Responses on Microsoft's Q&A consistently describe that pairing — an already-installed driver produces this result code — and the practical reading is that the update entry is cosmetic rather than a device problem.
Common Causes
- The driver-offering pass found no driver variant left to present for the device
- An enumeration API was called past its final element, which the caller misread as failure
- Duplicate delivery of an identical driver package left the offering sequence exhausted
Typical Scenarios
- Update history shows a driver install failing repeatedly for one device while the device itself works with its currently installed driver
- A scan re-offers a driver package whose matching variant is already present, ending the offering sequence
- Custom code walks a device or package collection past its last element and treats the end-of-list value as an error
What to Know
Comparing the offered driver's version against the installed one resolves the ambiguity: a match turns the repeated failure entry into an artifact of the offering pass.
Frequently Asked Questions
Common questions about Windows 0x80070103 error
Win32 error 259, ERROR_NO_MORE_ITEMS, listed in WinError.h with the message 'No more data is available'. The 0x103 field is hexadecimal for 259.
It indicates an offering loop, not device damage: the package being offered is already satisfied by the installed driver. Guidance on Microsoft's Q&A treats the entry as harmless in that situation.
The update pipeline reports delivery attempts. When a driver is already present, the attempt completes without installing anything, and the end-of-offering value is logged as the attempt's result.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
You have unresolved file conflicts preventing Git from completing the current operation.
You tried to add a remote named 'origin', but one with that name already exists.
Git does not know which remote branch should receive your pushed commits.
You checked out a specific commit, detaching your working directory from the branch history.