Windows 10 Missing icon data in shell32.dll & imageres.dll.

Image Observations​

• File Properties Dialog (Image 1):
• The imageres.dll file in your C:\Windows\System32 directory only shows a size of 2.50 KB (2,560 bytes). This is not normal, as imageres.dll is usually at least 20 MB or larger, containing numerous system resources, including icons.
• Attributes like "Read-only" and "Hidden" are standard for system files, but the unusually small size suggests:
• It could be a placeholder or corrupted file.
• There is redirection or virtualization occurring (e.g., the actual resources might be elsewhere).
• Resource Hacker UI (Image 2):
• The imageres.dll file displays extremely limited resources, with "MUI" (Multilingual User Interface) and possibly "Version Info" being the only available data.
• The blank resource tree further supports the theory that this file does not directly contain the icon resources, but they might be stored elsewhere or accessed through a different mechanism.

Potential Causes​

• Compressed/Stub File:
• The imageres.dll in your case might just be a stub file pointing to another location where the actual resources reside. This form of optimization isn’t uncommon in modern Windows updates to save disk space.
• Resource Virtualization:
• Windows may now rely on virtualized storage or APIs to provide these icons dynamically, which may not be accessible through tools like Resource Hacker.
• For example, icons may be pulled from a common cache or generated through system calls at runtime.
• Corruption or Incomplete Installation:
• The file size (2.50 KB) is concerning. Even redirection files are generally larger, and the fact that your imageres.dll exhibits the same behavior on both physical and VMware installations might indicate a broader issue with the ISO or build you’re installing.
• Network-Based Resources (Rare):
• Although uncommon, some Windows Server installations or lightweight modes might offload resources to be downloaded via the internet or fetched from a networked system. However, this is unlikely unless you’re using a vastly stripped-down edition of Windows.

What to Do Next​

• Verify File Integrity:
• Run this command in Command Prompt as an Administrator:
  
  Code:

       sfc /scannow

  This will repair any corrupted or missing system files.
• Alternatively, run the DISM (Deployment Image Servicing and Management tool) to restore system health:
  
  Code:

       DISM /Online /Cleanup-Image /RestoreHealth

• Check Other Installation Sources:
• If the behavior persists across multiple installations (e.g., physical and virtual), verify the integrity of your Windows ISO or installer. You can download the latest official Windows ISOs from the https://www.microsoft.com/software-download/ to ensure a clean image.
• Explore Alternate Resource Locations:
• On modern Windows systems, check if the real icon data exists in a cached DLL file:
  
  Code:

       C:\Windows\WinSxS

  This directory stores cached DLL versions and may have alternates of imageres.dll or shell32.dll that contain the actual icon resources.
• Icon Redirection/Registry Check:
• Use tools like the Windows Registry Editor to investigate if shell32.dll and imageres.dll are pointing to other files for icons. Look under:
  
  Code:

       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Icons

• Compare with Working System:
• If you have access to a functioning Windows 10/11 machine with the correct imageres.dll or shell32.dll, copy the files (if licensing allows) and compare them. Proper backups should always be made first.

If All Else Fails​