Problem Messages

This section is largely about meesages that report items of concerns (including errors and warnings).

Many errors generate log files and/or error messages. If this section does not provide suitable solutions to a problem, also check out log files. Some times of problems are also described in the section discussing errors.

Problem messages most likely to be found with Microsoft Windows
[#wnevtmsg]: Messages from Windows Event Logs

A collection of information including some details about challenging Windows Event Log events.

“Windows Script Host” dialog box

A “Windows Script Host” dialog box may pop up, showing some details like specifying a script file, line number, character number, error number (which may start with “0x”) and be 8 hexadecimal digits, code (which might be 8 hexadecimal digits that match what is seen in the error number), and a “source” of the problem. (This summary is based on an example from when slmgr.vbs gave Error 0xC004D302, which is a specific example that is described further by scheduling software licensing.)

This is most likely not a problem that is caused directly by a fault with the actual “Windows Script Host” program. Rather, the cause of the issue is likely a problem encountered by the specific script file. The details of the problem will vary based on what script file is being used. Determine which script file is being used. That is the information that is most likely to be useful in correctly determining the cause of the issue.

Then, use a search engine to see what is looked up. If that does not seem to add clarity, then people with relevant programming skills might want to take a look at the source code. (Variable names might be a useful hint as to what is going on.) If that is not providing results (perhaps because a programmer is not available), then the most reasonable option may be to utilize technical support, possibly provided by the software vendor.


Sometimes a program in the “system tray” (which Microsoft has also called the “message notification area”) may show a message. These messages are sometimes called balloons.

The messages tend to go away by themselves. Clicking on them will often result in opening a window that is related to the message, and so that window migiht show some further information that is related to the message.

In Microsoft Windows, such messages will often also be in the operating system's event logs. See: Messages from Windows Event Logs.

Hovering over the message might not keep the message on the screen. One approach that may be helpful is to perform a screen capture before the message disappears. For instance, in Microsoft Windows, press the PrtSc (“print screen”) button. Note that this might clobber the clipboard, but if that is an acceptable loss, then try creating a screen capture. If the image is saved into the clipboard, then find a program (like a “Paint” program, or perhaps a word processor if there is not an available program that was primarily designed for handling graphics formats), and use that program to try saving the image.