microsoft / microsoft/Windows-classic-samples
IFilterSample GUIDs conflicts with GUIDs uses by Microsoft Search Handler
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
It seems, that {1AA9BF05-9A97-48c1-BA28-D9DCE795E93C} and {6C337B26-3E38-4F98-813B-FBA18BAB64F5} already used in Windows 10 by PDF Persistent Handler and Reader Search Handler (%systemroot%\system32\Windows.Data.Pdf.dll) so the IFilterSample sample fails to register/unregister correctly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IFilterSample registration and unregistration path, then inspect where the two reported GUIDs are defined. Compare them with the PDF Persistent Handler and Reader Search Handler entries in Windows.Data.Pdf.dll, and verify that the sample registers and unregisters correctly without conflicting identifiers.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, search
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100