Data Recovery Case File · Formatted & Logical Faults · The Code Is Not the Cause
Device Manager Error Codes Decoded
His enquiry named the specific errors rather than describing them, which makes the case answerable. A 1TB Verbatim external drive that he had "had no luck accessing, and I have experienced code 28 and code 43, which I am unable to resolve." Anyone who searches those numbers finds thousands of pages recommending the same remedies: reinstall the driver, update Windows, uninstall the device and rescan. Those are reasonable suggestions for the situations the codes were designed to describe. They are also, on an external hard drive holding data somebody needs, the wrong response to what the codes are actually reporting — because the numbers describe a symptom in Windows, not a fault in the drive.
| Media | Verbatim 1TB external hard drive — presenting numbered device errors in Windows; contents inaccessible |
| Reported situation | Drive inaccessible · Windows reporting driver-related device error codes · standard online remedies attempted without success · data required |
| Fault class | Device failing to complete enumeration or identification — Windows reporting a driver-level symptom of a hardware-side failure |
| Equipment used | Removed from enclosure and assessed on a native connection · Atola Insight Forensic readiness and identification diagnostics · PC-3000 Express technological-mode service-area assessment · Data Extractor imaging under strict timeouts |
The decode: what the codes mean, and why the standard advice misses
What the codes describe: both are Windows reporting that it could not bring a device into service. One indicates that no driver is installed for the device; the other that the device reported a problem and Windows has stopped it. Neither is a storage diagnosis. They are the operating system's account of an outcome, and they are deliberately generic because the same outcome has many causes.
Why the usual advice exists: for their intended cases, it is sound. A genuinely missing driver, a corrupted driver installation, or a device that needs re-enumerating after a bad disconnect are all real and all fixed by reinstalling or rescanning. That is why the internet is full of it.
Why it does not apply to a failing drive: because on an external hard drive, these codes very often mean the device did not complete its identification — it did not tell Windows reliably what it was, so Windows could not attach the right driver or decided the device was misbehaving. That happens when a drive fails to reach readiness: head calibration failing, or the reserved firmware region unreadable. In those cases there is no driver to fix. Reinstalling one addresses the report rather than the cause, and the code returns immediately.
What the advice costs him: more than time. Each cycle of uninstalling, rescanning and reconnecting is another power-up of a drive that may be struggling, and some of the suggestions found alongside these codes are actively harmful — running disk repair utilities, initialising the disk, or letting Windows "fix" it. On a drive with a data problem, that sequence is how a recoverable fault becomes a partial recovery.
The distinction worth carrying: Windows error codes describe what Windows could not do. They are excellent for diagnosing Windows and poor for diagnosing hardware. When the device in question holds data you need, the correct response to a numbered code is not to work through remedies but to stop and establish what the drive itself is doing — which requires equipment that talks to the drive rather than to the operating system.
What to do instead: disconnect it. The codes have already told him the device is not completing enumeration, which is all Windows can establish, and further attempts add nothing.
On the bench
The drive was taken out of its enclosure and assessed on a native connection, which removes Windows from the question entirely — the codes describe an operating system's experience, and the useful information is what the drive reports electrically. The Atola Insight Forensic read the identification and readiness sequence directly, establishing whether the drive was failing to identify itself at all or failing later in its start-up. Access followed through the PC-3000 Express in technological mode where the service area proved damaged, and imaging ran under Data Extractor with strict timeouts once the drive would address its media.
The outcome
The drive assessed independently of Windows, its readiness failure located and the contents imaged. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone chasing a numbered device error: those codes describe what Windows could not do rather than what is wrong with your drive — one means no driver is installed, the other that the device reported a problem and was stopped, and both are deliberately generic; on an external drive they very often mean the device never completed identification, which happens when a drive cannot reach readiness, and there is no driver to fix; reinstalling addresses the report rather than the cause; and each cycle of uninstall-and-rescan is another power-up of a struggling drive.
Windows giving you a numbered device error
Stop working through the driver remedies. Those codes describe what Windows couldn't do rather than what's wrong with your drive — one means no driver is installed for the device, the other that the device reported a problem and Windows stopped it, and both are deliberately generic because the same outcome has many causes. On an external hard drive they very often mean the drive never completed telling Windows what it was, which happens when it can't reach readiness — a head calibration problem or an unreadable firmware region. There's no driver to reinstall for that, so the code comes straight back. Worse, the cycle of uninstalling, rescanning and reconnecting is another power-up each time, and some advice found alongside these codes suggests initialising or repairing the disk, which destroys what a recovery rebuilds from. Disconnect it and get the drive itself assessed.
The code describes Windows, not your drive — call Glasgow Data Recovery on 0141 404 0294; assessed on a native connection, readiness measured directly, service area repaired and imaged out.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.