Error loading C:/PROGRA~1/UNISTAL~1.DLL

I have a Pc that boots up to this message.
Error loading C:/PROGRA~1/UNISTAL~1.DLL
The specified module could not be found.

How can I fix this?
Any ideas.
Thanks.
Bill

 

Hi, w.young.

I suggest creating a handy Event Viewer shortcut on your desktop.

• Right-click on an empty location of your desktop and then select New > Shortcut.
• In the "Type the location of the item:" field, paste (or type)
  %SystemRoot%\system32\eventvwr.msc /s
• Click the "Next" button.
• In the "Type a name for this shortcut field:" type Event Viewer (or just leave it as "eventvwr.msc" if you prefer).
• Click on the "Finish" button.

Note the time the error occurs and then run the shortcut and see if you can find any more descriptive information. If you double-click on an error entry in Event Viewer, you'll get a Microsoft link to click on that might provide useful information to work with.

Another possible course of action is to enable boot logging for Windows. I don't recall right now with certainty exactly how to do that (or even if it would be helpful).

I recall, during my recently frequent Safe Mode boots , that boot logging can be enabled by repeatedly tapping the F8 key during boot until a black screen appears with several choices (including Safe Mode). Arrow up/down the list of items to "Enabling Boot Logging ", hit Enter. Then proceed with a normal boot to your OS.

EDIT: I think the bootlogging function appends text to the C:\WINDOWS\ntbtlog.txt file. Look for an indented line similar to
Service Pack 2 8 4 2006 16:40:14.500. If you repeatedly use the F3 key in Notepad to search for Service Pack 2 you'll get to the beginning of each log session. However, the information in my ntbtlog.txt doesn't seem to provide information that would be useful in your situation. But, hey, it was worth a shot. The Event Viewer suggestion above might be your best starting point.

EDIT #2: There are a few entries in my ntbtlog.txt file that refer to the Program Files folder (which appears to be the folder your error refers to). So maybe it would be useful for you.

I'm just taking stabs here (intermediate tinkering) about things to try until someone more knowledgeable comes along.

 

Before reading my input below, try to remember exactly when your error started appearing and what changes you made to your computer immediately before that. That might help you nail your problem more quickly. If you can provide more information in this regard, someone might know of a quick fix. [The UNISTAL~1.DLL (sic) filename isn't much help since part of the filename has been truncated (with the ~) in your post #1 report.]

It might be possible to quickly fix the problem using System Restore to restore Windows to the state it was in before the error occurred. Choose a Restore Point that immediately precedes your first encounter with the error, if possible. If you want help with using System Restore, feel free to ask.

I've been using System Restore often lately when I decide to make changes to my computer (i.e., software installations, uninstalls, hardware changes, etc.). It provides a little peace of mind. However, System Restore reportedly isn't a magic cure-all. Sometimes, it reportedly doesn't fix problems.


Another route, which may prove to be time-consuming but seems logical, is to follow the Help instructions in the System Configuration Utility.

• Click Start > Run, type msconfig in the Open: field, and click the OK button.
• Click on the Help button in the System Configuration Utility.
• Double-click on the System Configuration Utility menu item in the "Contents" tab and follow those instructions.