Click here to Skip to main content
13,045,285 members (67,476 online)
Rate this:
Please Sign up or sign in to vote.
See more:
Hello All,
my application writes a OLE compound document with summary properties.
I fail to tweak the registry so that the explorer shows these file properties.
If I rename the file to a .doc (or .xls or even .msi) extension, I see the additional properties.
But not with my own extension on Windows 7 systems.

Now I copied the same file on a Windows XP system, again without anything changed within the registry. To my (well, not sooo big) surprise, XP shows all the expected data within the properties.

XP defines the following entries within the registry:





@="Summary Properties Page"

The three CLSIDs are the following:

{1F2E5C40-9550-11CE-99D2-00AA006E086C} Security Shell Extension

@="Security Shell Extension"


{3EA48300-8CF6-101B-84FB-666CCB9BCD32} OLE Docfile Property Page
@="OLE Docfile Property Page"


{883373C3-BF89-11D1-BE35-080036B11A03} Microsoft DocProp Shell Ext
@="Microsoft DocProp Shell Ext"


On a Windows 7 system, the same keys appear under:
but without the SuppressionValue entries.

The CLSID {883373C3-BF89-11D1-BE35-080036B11A03} points into shell32.


Posted 24-Mar-13 6:30am
Updated 25-Mar-13 8:58am
Rate this: bad
Please Sign up or sign in to vote.

Solution 1

Well, this bcs of your system does not know abt your files.
You should just specify handlers for that in registry:

HKCR\{your extension} - in here you can put the information abt your extension and how it should be handled (including opening displaying in shell and so on)
Actually I think the main property which you require to add/change is ShellEx\PropertyHandler the default value is the guid of property handler (you can look at it for example for MS office files)

Note: if you specify office handler guid then property may not be displayed in case if MS Office not installed.

Information related to shell extensions: Registering Shell Extension Handlers[^]

Beat Laemmle 25-Mar-13 15:00pm
Maxim, thank you for your answer. The fact that it works on XP leads me to the assumption, that there is a solution without hijacking the office shell extensions.
Maxim Kartavenkov 26-Mar-13 0:54am
What is necessary under XP is to specify property sheet guid (or guids). Under Vista+ as I remember necessary to specify provider (which will map your file properties to standard metadata values) and also property sheet guid (or guids) to show your properties via right click. Whole such information you can find in registry and articles abt shell extension should helps you figure out what properties to use.
Beat Laemmle 26-Mar-13 15:12pm
Maxim, thank you very much for that hint.
After adding a property handler I got my properties.
Rate this: bad
Please Sign up or sign in to vote.

Solution 2

With Maxim's help I figured out the necessary registry entries to see the properties of an OLE compound document.

These registry entries solved that issue:

; For ZipPackages use
; {45670FA8-ED97-4F44-BC93-305082590BFB}  Microsoft XPS Shell Metadata Handler
; For OLE Documents use
; {8d80504a-0826-40c5-97e1-ebc68f953792}  OLE DocFile Property Handler
; Create an entry for the extension of my data files
; Create the file extensions
; Create the ProgIds, but without the code!
; NOTE: ProgIds shall not have more than 39 characters!!
@="My Programs data file"
; Create the property sheet handlers
@="Security Shell Extension"
@="OLE DocFile Property Page"
@="Summary Properties Page"

These entries bring up the properties of OLE compound documents.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Mobile
Web02 | 2.8.170713.1 | Last Updated 26 Mar 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100