Skip to main content
Participant
Nov 18, 2026 6:36 PM UTC
Open for Voting

Lightroom Classic 16.0 (Win 11) scrambled folder structure in existing catalog; 15.6 could not open catalog afterward

TITLE:

P: Lightroom Classic 16.0 (Win 11) scrambled folder structure in existing catalog; 15.6 could not open catalog afterward

 

BODY:

 

Summary

After updating from Lightroom Classic 15.6 to 16.0 on Windows 11, my production catalog opened in 16.0 with its folder structure scrambled. Folders for previously imported images appeared mixed together in the Folders panel and did not match the actual folder structure on disk. As expected for 16.0, no catalog upgrade prompt appeared.

 

I uninstalled 16.0 and reinstalled 15.6. Since 16.0 does not require a catalog format upgrade, 15.6 should have been able to open the same catalog, but it could not. I had to restore the catalog from a backup to continue working.

 

Expected behavior

- Folders panel shows the same folder structure in 16.0 as it did in 15.6.

- Because 16.0 makes no catalog format change, the catalog remains usable in 15.6 after reverting.

 

Actual behavior

- Folders panel in 16.0 showed previously imported folders mixed together, not matching their locations on disk.

- After reverting, 15.6 could not open the catalog.

 

Steps taken

1. Updated Lightroom Classic from 15.6 to 16.0 through the Creative Cloud app.

2. Launched 16.0. It opened my production catalog directly (no upgrade prompt, as expected).

3. Observed scrambled folders in the Folders panel.

4. Uninstalled 16.0 and reinstalled 15.6.

5. Tried to open the same catalog in 15.6. It would not open.

6. Restored the catalog from a backup.

 

Catalog details

- Catalog is on the internal C: drive.

- Photos are stored on external drives.

- Approximately 100,000-250,000 photos.

 

System

- Windows 11, fully updated

- NVIDIA GeForce RTX graphics, driver up to date

- High-performance laptop; full System Info available on request

 

Other notes

- This was the full release, not a beta.

- I kept the affected catalog file and can provide it.

- I'd like to know whether this is a known issue and whether it is addressed in 16.1. I plan to test 16.1 on a duplicate catalog before using it on my production catalog.

    1 reply

    kglad
    Community Expert
    Community Expert
    Nov 18, 2026 6:40 PM UTC

    moved from using the community.

    Translate