Hi judhistira,
Whatever that DLL is, its not part of the Windows 10 OS. Thus it must belong to a third party application you have installed at some stage.
You could
right-click on
Start then
left-click on
Task Manager. When Task Manager opens click the
Startup tab and take a look at what is listed there as these are the applications which can load as computer boots up.
You could disable the culprit there if it's obvious which one belongs to your mystery DLL file.
Alternatively, a third party application may have written a registry value to force its automatic boot when computer starts. If you have all ready removed a virus, or some third party application using uninstall, a security program, or some cleaning program, this value may have been left behind, and it is called, but as the error tells you, there is no module for Windows to locate; thus its unable to load.
For a local User the common registry keys to check are:
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce
If this issue is affecting multiple Users on your computer then its more likely to be here:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce
To save opening the Registry Editor immediately you can do a simple reg query via a standard command prompt:
- Right-click on Start
- Left-click on Command Prompt
- When the Command Prompt window opens type or copy & paste the following commands.
Note: Press Enter key after each command to execute
Code:
reg query "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run"
Code:
reg query "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce"
Code:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run"
Code:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce"
Sample result image - your's may differ
View attachment 3517
If nothing shows up here there its possible it has created its own unique Registry key in which case you'd need to search the Registry for that key. Again, you could search the registry using command prompt like so:
-
Code:
reg query HKCU /v "Postallchthyisms.dll" /s
-
Code:
reg query HKLM /v "Postallchthyisms.dll" /s
These are the likely keys to contain a new third party subkey which calls on that mystery DLL file. It could be written else where, but that is highly unlikely.
Report back on your results. If you do find a reference to that Postallchthyisms.dll in the registry I'll tell you how to remove it and thus end this error message.
If on the other hand, nothing shows up using the above commands and/or searches then you could make use of Microsoft's tool designed to dig out all startups called AutoRuns which you could use to help locate this too if needed. That can be downloaded via Microsoft's Technet site here:
https://technet.microsoft.com/en-us/sysinternals/bb545021.aspx
This takes a little getting used to using though, so if you end up needing this you may need help on using it. Just ask if you require assistance. Someone will help.
Regards,
Regedit32