Data Recovery Case File · Mac & Apple Systems · Caught Between Two Versions
A Library Conversion Interrupted Partway Leaves a Structure Neither Version Can Read
His enquiry places the failure at a moment rather than at a device. A photo library that has not opened since a system update, where "the application crashed during the update and I have not been able to open it since" — and the library has since been copied from an array onto an external drive. Major updates convert application libraries to new formats, and a conversion interrupted partway leaves a structure that is neither the old one nor the new one.
| Media | Photo application library originally held on an array and since copied to an external drive — application failing during a system update and not opening subsequently |
| Reported situation | System update applied to a laptop · photo application crashing during the update · library not opening since · library previously stored on an array · library subsequently copied to an external drive over a direct connection · photographic content required |
| Fault class | Library format conversion interrupted — internal database left between versions with original image files intact; content recoverable independently of the library structure |
| Equipment used | Failure identified as an interrupted format conversion rather than media damage · copied library preserved unmodified as the working source · library internal structure examined for version state and conversion markers · original image files extracted from the library package independently of its database · recovered images validated by opening at full resolution |
The decode: what an update does to a library, and why the photographs are safe
What a photo library actually is: a package containing a database and the image files it organises. The database records albums, dates, edits and arrangement; the images sit inside as ordinary files.
Why a system update touches it at all: major versions change the database format. The application converts the library on first launch after an update, rewriting its internal structure to the new arrangement.
Why that conversion is a vulnerable moment: it rewrites the database in place. An interruption partway leaves records partly in the old format and partly in the new, and neither version of the application can then read it coherently.
Why the application refuses to open it rather than repairing it: a half-converted database is ambiguous. Opening it and guessing would risk losing the organisation entirely, so refusing is the safer behaviour.
Why the photographs themselves are almost certainly untouched: the conversion rewrites the database, not the images. The original image files sit inside the package exactly as they were, in their own folders, at full resolution.
Why that makes this a far better position than it feels: the loss is of organisation rather than content. Albums, arrangement and edit history are at risk; the photographs are not.
Why the copy he made was the right move: it removed the library from the array and gave him a second instance. Work can proceed against the copy while the original stays untouched, which is exactly the right ordering.
What is worth checking before anything technical: whether the array still holds the pre-update library. If the original was copied rather than moved, an unconverted version may still exist — and that would open normally on the earlier application.
What is done where it does not: the images are extracted from the package directly, bypassing the database entirely. They are ordinary files in ordinary folders once the package is opened as a directory, which requires no working library at all.
What must not happen: no repeated attempts to open the library, and no accepting an offer to repair it. Each attempt may continue the conversion from where it stopped, and a repair rewrites the structure that is being reconstructed.
On the bench
The failure was identified as an interrupted format conversion rather than media damage — a photo library comprising a database recording albums, dates, edits and arrangement alongside the image files themselves, with major system versions changing that database format and the application converting on first launch. Interruption leaves records partly in each format, which no version reads coherently, while images remain untouched. Original image files were extracted from the package independently of its database.
The outcome
The failure identified as an interrupted conversion, the copied library preserved unmodified, and images extracted independently of the database. Free assessment, one fixed written figure including VAT. The decode: what was being rewritten is the database, not your photographs. A conversion stopped partway leaves records between two formats — and the images sit inside the package as ordinary files at full resolution.
A photo library that stopped opening after a system update
Stop trying to open it and refuse any offer to repair it, since each attempt may continue the conversion from where it stopped. Check first whether an earlier copy of the library still exists wherever it was stored before — if it was copied rather than moved, an unconverted version may open normally. Understand what failed: major updates convert a library's internal database to a new format on first launch, and an interruption leaves records partly in each, which no version can read. Your photographs sit inside the package as ordinary files and are untouched.
Stop opening it — call Manchester Data Recovery on 0161 871 0788; identified as an interrupted format conversion, copy preserved unmodified, images extracted independently of the database.
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.