File path that DLL uses by default

[rolfk]

I hope you didn't just hardcode this path in your software, at least if you not only intend to install the software on systems of your own that you fully control. Otherwise systems might be heavily locked down and you might not have the right to create arbitrary folder hierarchies even during installation of a software. Also the naming scheme for the standard hierarchy can change for specially setup Windows installations or because of localized directory names. Some companies like to do heavily customized Windows installations for their internal computers just for the fun of it.

Better might be to use one of the "special" locations that you can retrieve through SHGetSpecialFolderPath(). That will isolate you more from such internationalization issues and custom Windows installs. But it all depends on the audience for your software. No need to go extreme for an internal software tool that never will leave your company.