What is wisecustomcalla.dll and why are there so many?

You know, the problem with doing google searches on any DLL file name is that there are just too many marketing and other useless pages created to waste 2 hours of your time trying to find out something that you might be able to find out fairly easily yourself.

In google searches you will always get results (many of them sponsored ones) like:
- "Fix wisecustomcalla.dll now" - some "fix-all" registry scanner and repair tool
- "Download wisecustomcalla.dll" - pay $5 to get a copy of a file nobody can describe
- "Buy wisecustomcalla now" - some marketing page that takes keywords searched for and leads you to another search page
"Removal of malware - Information about wisecustomcalla.dll" - one of a plethora of half-baked antivirus tools that sells itself by hinting that the file may be a rogue one.

In the end, a lot of the "What is 'wisecustomcalla.dll'?" pages are nothing more than guessed information uploaded by non-expert members of the public, and it's very hard to know which wer4e offered by people with any technical knowledge at all.

So, why not try and ascertain something about the DLL file yourself.

Right-Click on "wisecustomcalla.dll", and a couple of the other ones with a number suffix, choose "Properties", and then take note of what it tells you under each of the tabs in the properties dialog.  Click any "Details" buttons under the tabs in the properties dialog to show any extended information also.  Post the details here.

Open the Registry Editor (Start Menu > Run > and type REGEDIT > click OK).
Scroll back up the left pane to the top level item and click on it.
Edit Menu > Find > Look at Keys, Values and Data checked, "Match whole string" unchecked > Click "Find Next.

For each entry found, click back on the master key (left pane) containing whatever entry was found, then use the File Menu > Export option to export the "Selected Branch" to a suitably named "Registration file (*.reg)" in a new folder somewhere easy to find later.

To "Find Next" just press F3 and repeat this.  Hopefully it won't find a registry key or value for ALL "wisecustomcallaxx.dll" files, however if you see a value in the right-hand pane of Regedit under a registry key that implies it is only the results of eg. Windows searches for files of that name, then they can be skipped.

Close Regedit when the sarch indicates that no more instances were found.

If there are less than half a dozen finds in regedit, then either zip the *.reg files up into one *.zip file to upload here as an attachment, or Right-Click > Rename the *.reg files by changing the *.reg file extension to *.txt, then upload each.  You could also Right-Click > Edit each *.reg file to open in Notepad, copy the contents, and sequentially copy and paste into one notepad *.txt file to upload.  Experts-Exchange limits the number of file types that can be uploaded.

Do another regedit search, but this time search for the long numeric folder name "24C67B540718445EB6633138D9246BD1".  Double check that I transcribed this properly.  Export the master key of each instance found to suitably named *.reg files and allow us to see the information from them as described above.

Do a Windows file seach for "Files Containing Text" and enter "wisecustomcalla" as the search string.  The search will take a long time, and limit it to only the C:\ drive.  Take note of the names and locations of files such as .INF, .INI, .CFG, and other setup instruction or configuration type files.  They will be the best source of information to ascertain what created the DLL files and from what process.  Any file named "WiseCustom" with a .txt, .inf, or .ini, or .log extension would be great to find.  DON'T load any files found (yet) but keep note of where they are and what they are named and post here.  The names and locations may be enough to give us an insight.

Download and install a small utility that will add a new "Peek" item to the Right-Click menu of any file type.  It will offer sub-options to inspect the file as tandard, Binary, or Unicode.  It extracts as much text-based data from the file to a temporary text file and opens it in Notepad without messing around in any way with the contents of the file right-clicked on.  The right-click menu opton is uninstallable again through your "Add/Remove Programs".

Save Peek.zip from the following link:
from: http://members.ping.at/mlubich/peek11.zip
Extract it to its own folder using WinZip, WinRAR, 7-Zip, or whatever you normally use to handle zip files.
Right-Click on peek.INF and choose "Install".
You will now have your "Peek" right-click menu and you can delete the zip file and extracted files.

Try each of the Peek options on a couple of the *.dll files and *.exe files in that folder.  It can present you with a load of gobbledegook, but amongst the illegible code you can usually see details of what program was used to create them, and some registry keys and log files involved in the process.

My guess is that these are left-over temporary setup files from a progam that was installed from a package built using the "Wise" installer.  The fact that the containing folder is named:
"24C67B540718445EB6633138D9246BD1.TMP"
is a reasonable indicator of this hunch.
Quite often a setup package contains separate resources for many languages that you choose during setup.  If written properly, the installer process should only unpack files used to install the program in that language, however badly written setup packages, or ones where the normal process is overridden to customise setup behaviour (eg. a "silent install" version) can often unpack ALL the resources and forgetto clean up the left-over files after the setup completes.

Normally a setup package uses standard language ID codes like 049 for English, but that is not a hard and fast rule.

Let us know what information you are able to get using my suggestions, and we an then take it further.