Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[OutOfProcCOM] COMRegistration.LocalServer.Unregister does not fully delete the COM class from registry

Open
  • Is something wrong?
#5,960 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
desktop

Research direction

Start in the ExeServer project in the OutOfProcCOM sample and inspect COMRegistration.LocalServer.Unregister. Reproduce the /regserver and /unregserver steps with administrator privileges, then verify in Registry Editor that the HKCR\CLSID{AF080472-F173-4D9D-8BE7-435776617347} folder is removed completely.

Written by the indexing model from the issue text.

Description

The ExeServer project in the OutOfProcCOM sample doesn't fully unregister itself when starting with /unregserver. This seem to be caused by the COMRegistration.LocalServer.Unregister function only deleting the content inside the HKCR\CLSID\{class-id} folder, but not the folder itself.

Steps to reproduce:

  • Build OutOfProcCOM solution
  • Run ExeServer.exe /regserver with admin privileges.
  • Run ExeServer.exe /unregserver with admin privileges.
  • Open regedit.exe and observe that there's still a HKCR\CLSID\{AF080472-F173-4D9D-8BE7-435776617347} folder there.
Dominant language
C#
Stars
3.7k
Forks
5.1k
Avg merge
8m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/samples

All issues in dotnet/samples

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.