DCKFinder

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

★ 17 Open GitHub ↗

Dangling COM Keys Finder

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# DCKFinder: Dangling COM Keys Finder

A simple utility to locate COM registry keys referencing DLL or EXE which are not on the system anymore.

## Disclaimer

I'm quite a bad C++ coder, so bear with me but this code might not be really elegant.

## Overview

During COM development or testing, it is usual to register many COM server DLLs/EXEs in the system to test their functionalities. The main issue with that 
is that several orphaned keys might be left in the Windows Registry, just as garbage. This utility has been developed to easily locate these instances, in order to 
delete them.

## Why

I attended the amazing COM Programming Course by [Pavel Yosifovich][1], and I found myself registering many DLLs for testing various COM test servers, leaving a lot of garbage in the registry.
Within the class we discussed how it could be actually useful to craete a little utility to locate all these "orphaned" or "dangling" registry keys, and that's the reason for this tool.

## Next Steps

* adding a functionality to automatically delete orphaned DLLs

## Usage

The tool is pretty easy to use, as observable by the help below:

```
Dangling COM Registry Keys Finder v0.1

Optional args:
-f <filter>: Filter Keys showed (choices: [all, d, nd, dr, dnr] ) (default: all)
   d: Dangling
   nd: Non Dangling
   dr: Dangling relative (only relative paths)
   dnr: Dangling non-relative (only non-relative paths)
-t <type>: Filter Keys showed (choices: [none, machine, user] ) (default: all)
```

To locate orphaned COM DLL/EXE registered using per-user redirection, use the following command:

```
DCKFInder.exe -t user -f d
```

To locate orphaned COM DLL/EXE registered for all users, use the following command:

```
DCKFInder.exe -t machine -f d
```

The Rel/No-rel distinction was added because some DLL are registered using just the name and not the full path. As nothing ensures those DLL are actually "orphaned" (indeed, they usually aren't), I decided to add
the option to filter them out or in on demand.

## Considerations

Be aware that results of the x86 and x64 version of the tool may differ due to [reflected keys](https://docs.microsoft.com/en-gb/troubleshoot/windows-client/deployment/view-system-registry-with-64-bit-windows).

## Credit

* [zodiacon][1]

[1]: https://twitter.com/zodiacon

DCKFinder

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README