<Back

 Usually Power Drawers works, but sometimes I get a program error or crash.

When errors occur, it’s important to determine:
a) if Power Drawers is related to the error and 
b) if not Power Drawers, what program(s) actually are at fault so you know whose tech support department(s) to contact about the problem. 

When you access files and applications through Power Drawers, an error could be caused by either Windows, other shell extensions installed, the application you were opening, the application associated with the file you were opening or Power Drawers. Use the information below to help determine what was the cause of the problem. If the problem really is caused by Power Drawers, we will be eager to fix the problem ASAP. First read everything below to help determine the cause of the problem. 

Because Windows and applications are complex and interact with each other, programs sometimes crash or report errors. Even carefully written and tested programs could crash if you run too many apps at once or if some other app made the system unstable. Therefore, if something crashes on your computer, don’t assume that Power Drawers or Windows itself is at fault, even if you just installed it or used Power Drawers to access the file or program. 

What Error Messages Mean
Most error messages shown in Windows are in a form such as “xxxxx caused a fault in module yyyyy” where xxxxx and yyyyy are the executable components involved in the program error. If neither xxxxx nor yyyyy is a Power Drawers component, then the problem is not related to Power Drawers. Here is a list of Power Drawers executable components: powerext.dll, powercom.dll, powerapp.exe, pwrtray.exe, pwrupdat.exe, pwrscan.exe. If none of these files is mentioned in an error message, Power Drawers is not part of the problem.

If an error occurs and displays the error message ‘This program has performed an illegal operation and will be shut down’, then click on the Details button (if there is one) to see a more useful error message in a form such as “xxxxx caused a fault in module yyyyy”. The other information on the Details view is not useful for determining what crashed.

For example, if you launch an application called WNORANGE.EXE and there was an error, the error message might say “WNFRUIT.DLL caused a fault in module WNORANGE.EXE”. In such a case, you would need to contact the vendors of WNFRUIT.DLL and WNORANGE.EXE to determine what is causing the error since it has nothing to do with Power Drawers or Windows itself. 

If Still In Doubt, Temporarily Disable Power Drawers
If you think Power Drawers might be interfering with some other application, you can easily disable it to ensure it doesn’t interfere and to test if Power Drawers is the cause of a problem. (see Disabling/Enabling Power Drawers).  If the problem is not repeatable with Power Drawers enabled or the problem occurs even with Power Drawers disabled, then you know Power Drawers is not the cause of the problem. After the test, make sure you re-enable Power Drawers. (see Disabling/Enabling Power Drawers)

If Power Drawers does seem to be related to a problem, make sure your copy of Power Drawers is updated (See Updating) and, if necessary, use our Tech Feedback form to contact our tech support department. We will need enough detail about the error so that we can duplicate the error on a test computer here. If we can't duplicate the error, we can't fix it, but if we can duplicate a reported error, we will fix it, test the fixed version and post it so that your Updater can install the fixed version.