Ordner mit Bildern werden nicht mehr angezeigt

• The affected files are corrupted or incomplete
• The files are not really JPGs despite the .jpg extension
• There is a permissions/ownership problem in those folders
• The path or filename is too long or contains unusual characters
• The drive/file system has errors
• The files were altered by sync software, backup software, encryption, or malware

1. Quick test: copy one affected JPG to D:\​

1. Pick one JPG that does not open.
2. Copy it directly to:

1. Try opening D:\test.jpg.

Result meaning​

• If D:\test.jpg opens: the file is probably OK, and the problem is related to the folder path, permissions, or filename.
• If D:\test.jpg still does not open: the file itself is probably damaged, encrypted, incomplete, or not a valid JPG.

2. Check whether the JPG is actually a valid JPG​

1. Right-click one affected file.
2. Choose Properties.
3. Check the Size.

1. Open PowerShell.
2. Run this, replacing the path with one affected file:

3. Test with a short folder name​

1. Create a new folder:

1. Copy one affected JPG into it.
2. Rename it to something simple:

1. Try opening:

4. Check permissions on the affected folders​

1. Right-click an affected folder.
2. Select Properties.
3. Open the Security tab.
4. Make sure your Windows user has at least Read permission.
5. If permissions look wrong, click Advanced and check the owner.

5. Check the drive for file system errors​

1. Open Command Prompt as Administrator.
2. Run:

6. Try opening with a robust image viewer​

• IrfanView
• XnView MP
• Paint.NET
• GIMP

7. Important question: were the files synced or restored?​

• OneDrive/Google Drive sync problems
• Copying from an external drive
• Recovery software
• Backup restore
• Disk errors
• Ransomware/encryption damage

Questions for you​

1. Does an affected JPG open after copying it to D:\test.jpg?
2. What is the file size of one affected JPG?
3. Does the file start with FF D8 FF in PowerShell?
4. Are the affected folders on an internal disk, external USB disk, NAS, or cloud-synced folder?
5. Did anything happen recently — Windows update, disk check, backup restore, sync error, or crash?

WindowsForum AI said:

Format-Hex "D:\YourFolder\YourImage.jpg" -Count 16

Click to expand...

Option 1: PowerShell-compatible JPG header check​

1. Open PowerShell.
2. Run this command, replacing the file path with one affected JPG:

$path = "D:\YourFolder\YourImage.jpg"
$bytes = [System.IO.File]::ReadAllBytes($path)
$bytes[0..15] | ForEach-Object { "{0:X2}" -f $_ }

FF
D8
FF
E0

FF
D8
FF
E1

Option 2: Shorter command​

What the result means​

FF
D8
FF

Important next test​

1. Copy one affected JPG into D:\.
2. Rename it to:

1. Try opening:

What this means​

• Corrupted
• Partially overwritten
• Encrypted by some software
• A different file type renamed to .jpg
• Damaged by disk/file-system errors
• A placeholder or broken sync/recovery file

1. Compare with a working JPG​

2. Check file size​

3. Stop writing to drive D: for now​

4. Run a read-only disk check first​

5. Check whether many files have the same bad header​

Get-ChildItem "D:\YourFolder" -Filter *.jpg -Recurse | ForEach-Object {
    $b = [System.IO.File]::ReadAllBytes($_.FullName)
    [PSCustomObject]@{
        File = $_.FullName
        Header = ($b[0..2] | ForEach-Object { "{0:X2}" -f $_ }) -join " "
        Size = $_.Length
    }
}

6. Possible next steps​

1. Check backups first — File History, cloud backup, external disk, phone/camera originals.
2. Try opening the broken file with IrfanView, XnView MP, or GIMP, but if the header is wrong, they will likely fail too.
3. If the photos are important, use recovery software before running more repair attempts.
4. Check the drive health with a SMART tool such as CrystalDiskInfo.
5. Run a malware scan if many files changed suddenly.

My current assessment​

Format-Hex "D:\ana.jpg" -Count 16
Get-Item "D:\ana.jpg" | Select-Object Name,Length,LastWriteTime

Most likely causes​

1. File-system corruption on D:
   A damaged directory table, bad clusters, or interrupted write operation can affect many files in one folder tree.
2. Failing HDD/SSD/USB drive
   If D: is an external disk, old HDD, USB stick, SD card, or secondary SSD, drive errors are a strong possibility.
3. Interrupted copy/move/sync operation
   If the files were moved from camera/phone/cloud/external disk and the operation was interrupted, many files can end up broken.
4. Recovery software restored wrong data
   Recovered files often keep names like .jpg, but the contents may be unrelated or incomplete.
5. Cloud/sync placeholder problem
   OneDrive, Google Drive, Dropbox, NAS sync tools, or backup tools can sometimes leave placeholders or partial files.
6. Encryption/ransomware or third-party software damage
   Less common, but sudden mass corruption should make you check this. Usually ransomware also changes extensions or leaves notes, but not always.

What I would do now​

1. Stop writing to D:​

2. Check whether D: is healthy​

1. Install or open CrystalDiskInfo.
2. Look at the health status of the drive containing D:.
3. If it says Caution, Bad, Reallocated Sectors, Pending Sectors, or Uncorrectable Sectors, stop using the disk and clone/recover it first.

3. Run a read-only disk check​

4. Check timestamps and sizes of bad files​

Get-ChildItem "D:\" -Filter *.jpg -Recurse |
Select-Object FullName,Length,LastWriteTime |
Sort-Object LastWriteTime -Descending |
Out-GridView

• Many files changed at the same time
• Many files have identical size
• Very small files
• Files changed recently without your action

5. Compare headers in bulk​

Get-ChildItem "D:\" -Filter *.jpg -Recurse | ForEach-Object {
    try {
        $fs = [System.IO.File]::OpenRead($_.FullName)
        $bytes = New-Object byte[] 3
        $null = $fs.Read($bytes,0,3)
        $fs.Close()

        [PSCustomObject]@{
            File = $_.FullName
            Size = $_.Length
            Header = ($bytes | ForEach-Object { "{0:X2}" -f $_ }) -join " "
            ValidJPG = (($bytes | ForEach-Object { "{0:X2}" -f $_ }) -join " ") -eq "FF D8 FF"
            Modified = $_.LastWriteTime
        }
    }
    catch {
        [PSCustomObject]@{
            File = $_.FullName
            Size = $_.Length
            Header = "ERROR"
            ValidJPG = $false
            Modified = $_.LastWriteTime
        }
    }
} | Out-GridView

6. Check backups before repairing​

File History
OneDrive/Google Drive/Dropbox version history
Windows Backup
External backup drive
Phone/camera memory card
Recycle Bin
Previous Versions

7. Run malware scan​

1. Open Windows Security.
2. Go to Virus & threat protection.
3. Run Full scan.
4. Then run Microsoft Defender Offline scan.

Important question​

Method 1: Open Command Prompt first​

1. Click Start.
2. Type:

1. Right-click Command Prompt.
2. Choose Run as administrator.
3. In the black window, run:

1. Leave the window open and copy/post the result here.

Method 2: Use PowerShell/Terminal​

1. Right-click Start.
2. Choose Terminal (Admin) or PowerShell (Admin).
3. Run:

Method 3: Save the output to a text file​

bad sectors
file record segment
index errors
Windows found problems
no problems found

Important: Do not run repair yet​

Also check whether Command Prompt is blocked​

1. Press Win + R.
2. Type:

1. Press Enter.

1. Run CHKDSK and save the result to Desktop​

1. Press Win + R.
2. Paste this command:

1. Press Enter.
2. Wait 1–3 minutes.
3. Look on your Desktop for:

1. Open that file and copy the result here.

2. If no text file appears​

1. Press Win + R.
2. Paste:

1. Press Enter.
2. Check the desktop again.

3. If the Command Prompt window is off-screen​

1. Press Alt + Tab and see whether Command Prompt or Windows Terminal appears.
2. If yes, select it.
3. Press Alt + Space.
4. Press M.
5. Press one arrow key, for example Left.
6. Move the mouse — the window may snap back into view.
7. Click once to place it.

4. If you have used a second monitor before​

1. Press Win + P.
2. Select:

Important​

Run CHKDSK as administrator and save output​

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click Run new task.
3. Type this:

1. Tick/check:

1. Click OK.
2. In the Administrator Command Prompt, run:

If the admin window still is not visible​

1. Press Ctrl + Shift + Esc.
2. Click Run new task.
3. Paste this full command:

1. Tick/check Create this task with administrative privileges.
2. Click OK.
3. Wait a few minutes.
4. Check your Desktop for:

If it still says the disk is locked​

Photo viewer
Backup software
Cloud sync tools
Explorer windows open in D:
Image editors

Important​

What your findings suggest​

1. Old corruption that went unnoticed
   The files may have been damaged long ago, but only noticed now when you tried to open them.
2. Bad import/copy/backup event in the past
   A failed migration, restore, copy from another drive, recovery program, or sync issue can create many files with correct names but wrong contents.
3. Files restored from damaged media
   Recovery tools often recreate filenames/extensions, but the internal data may be wrong.
4. Application or sync software replaced content
   Less common, but possible if some tool processed or synchronized those folders incorrectly.
5. Not an active SSD failure
   A 96% SSD health reading is reassuring. It does not prove the old files were always valid, but it makes an ongoing disk failure less likely.

What I would do now​

1. Preserve the current state​

2. Search backups by filename​

External backups
Old PCs/laptops
Cloud storage version history
Phone/camera storage
SD cards
NAS backups
Windows File History

3. Check “Previous Versions”​

1. Right-click the folder.
2. Open Properties.
3. Go to Previous Versions.
4. Restore only to a different folder first, not over the current one.

4. Keep the SSD monitored​

5. Strengthen backup strategy​

Final note​