How to Unlock Windows 11’s Hidden Vault of Classic 90s Icons Without Installing Anything

Windows 11 may look like the future, but buried inside its System32 folder is a living museum of 1990s computing art. As Neowin reported on July 27, 2026, a handful of vintage icon libraries—including moricons.dll and pifmgr.dll—still ship with the operating system and can be tapped for custom shortcuts using nothing more than Windows’ built-in Change Icon dialog.

A Time Capsule in System32

The discovery isn’t just a nostalgia trip. It’s a practical reminder that Windows’ compatibility roots run deep. The same DLLs that once gave Program Manager its personality now sit dormant, yet perfectly accessible, in Windows 11’s core system directory. Open the Change Icon dialog, point it to C:\Windows\System32\moricons.dll, and suddenly you’re staring at a grid of pixel-art folders, floppy disks, CRT monitors, and chunky application symbols designed for an era when 16 colors were a luxury.

The icons are genuine artifacts. They predate the rounded minimalism of Microsoft’s Fluent design by decades, offering stark outlines, literal metaphors, and a tactile sense of physical computing objects. For anyone who remembers Windows 3.1 or Windows 95, the visual punch is immediate. For everyone else, it’s a chance to inject genuine distinction into a desktop that can sometimes feel sterile.

Neowin’s guide was the first to spotlight the breadth of this hidden collection, walking readers through a simple shortcut-customization process that requires no registry edits, no third-party software, and no administrator privileges. At a time when customizing Windows often feels locked down, this old-school trick is a welcome surprise.

Why Microsoft Keeps These Digital Fossils Around

If you’re wondering why Windows 11 still carries icons from an operating system released in 1995, the answer is simple: breaking things is expensive. In Windows, an icon isn’t just a picture file. It’s a resource embedded within an executable or DLL, referenced by a numerical index. Old software, enterprise installers, and even long-forgotten management tools can still point to a specific icon inside, say, shell32.dll or moricons.dll. Remove that resource, and those shortcuts or applications suddenly display a generic placeholder—or worse, crash.

Microsoft documents this architecture extensively. Icons can be stored as RT_GROUP_ICON resources that bundle multiple sizes and color depths, and the operating system selects the most appropriate variant for your display. This system has been in place since the early Win32 days. So when you install a cumulative update, Windows doesn’t strip these old assets precisely because it can’t be sure nothing still depends on them. The result is a preservation-by-default strategy that has inadvertently left us with a treasure trove of visual history.

Icon Treasure Map: The DLLs Worth Exploring

Start with the two most famous libraries, then branch out. Here’s a quick-reference breakdown of what each file offers and which shortcuts suit it best:

Every file listed here can be opened through the same Change Icon dialog. Experimentation is free and risk-free.

How to Put a 30-Year-Old Icon on Your 2026 Shortcut

The process hasn’t changed since Windows 95. Right-click any shortcut (or create one first), choose Properties, then on the Shortcut tab click Change Icon. Windows may warn that the file contains no icons—ignore that; it’s referring to the shortcut’s target, not the DLL you’re about to browse. Click OK, then delete the existing path and paste in the full DLL location, like:

C:\Windows\System32\moricons.dll

Hit Enter. The selection pane fills with whatever icon resources the DLL contains. Choose one, click OK, then Apply. The shortcut instantly adopts the vintage artwork. If you don’t like it, repeat the steps and pick another, or click Restore Defaults to return to the original.

What if you see a “no icons” message even after entering a valid DLL path? That’s rare but can happen if the DLL lacks properly formatted icon groups. Double-check the file name and path, and try another library from the list. The classic picks—moricons.dll, pifmgr.dll, and shell32.dll—are the most reliable.

The Safety Catch: Why This Is Better Than Downloading Random .ico Files

The biggest advantage is defense in depth. You’re not downloading an executable icon installer from a forum. You’re not granting elevated rights to a script. You’re simply pointing a shortcut at a resource that Microsoft already shipped and digitally signed. Even if an icon looks old, its source code has passed through Redmond’s own build pipeline.

That’s not just a theoretical benefit. Malicious icon packs have occasionally bundled adware or browser hijackers along with innocuous-looking .ico files. By sticking to the built-in libraries, you avoid that entire category of risk. And because you’re only changing a shortcut’s metadata, not the actual executable or system file, there’s zero chance of triggering Windows Resource Protection or interfering with future updates. If anything goes wrong, a single right-click and “Delete shortcut” removes all traces.

The Fine Print: What Works, What Doesn’t, and What to Avoid

Legacy icons come with legacy limitations. Many were drawn for 32×32 pixel screens at 16 or 256 colors. On a 4K monitor, some will look charmingly crisp; others will appear muddy, jagged, or simply too small. Windows 11’s scaling tries its best, but an icon designed for a 14-inch CRT cannot magically gain resolution it never had. Use these for accent, not for every shortcut on a productivity desktop.

Accessibility matters too. An over-detailed floppy disk icon can be hard to distinguish at small sizes, especially for users with visual impairments. For frequently used shortcuts, choose icons with strong silhouettes and high contrast—like the classic folder from shell32.dll or the speaker from mmres.dll. The goal is to make the desktop more usable, not just more nostalgic.

Never edit or delete the actual DLL files. Browsing them is safe; modding them is not. Windows treats these as protected system files, and any alteration can be silently overwritten by the next update—or worse, leave a broken reference that troubleshooting tools later choke on. Stick to the Change Icon dialog, and you’ll never need to worry.

Enduring Charm, Responsibly Applied

This isn’t a call to turn Windows 11 into a Windows 95 theme park. It’s a celebration of an operating system that, for all its modern polish, still carries the DNA of its predecessors. The fact that a clean Windows 11 install can, in seconds, display a pixel-perfect Windows 3.1 icon is a testament to engineering decisions made decades ago—decisions that prioritized stability and backward compatibility over tidy housekeeping.

Use it to make your desktop more personal. Give your remote desktop shortcut a workstation icon from mstscax.dll. Let your retro games folder shine with a moricons gem. Distinguish your backup drive with a floppy disk from shell32.dll. These small touches require zero sacrifice in security or performance, and they turn an impersonal default layout into something that actually feels yours.

Will Microsoft ever scrub these fossils? Possibly. Each feature update might remove a few icons that no combination of compatibility testing deems essential. But the core libraries—especially shell32.dll and imageres.dll—are so tightly woven into the system that they’re likely to persist for years. Until then, Windows 11’s hidden icon vault remains one of the quietest, safest, and most satisfying ways to customize your PC.