wbload.dll audit failure

from WinCustomize Forums

Well...I've been having problems with Windows Explorer taking a few minutes to actually display items or to finish loading or something.  When I start WinExp, the window is blank, then the "not responding" window frame shows up, eventually it finishes. 

In an attempt to troubleshoot this mess, I found this entry in the Audit section of the Event Viewer...there are over 80 entries (I tried counting, but there are too many.  They start at 9:54:02 and end at 9:58:52 which is 'about' how long it took explorer to get over itself.)

"Code integrity determined that the image hash of a file is not valid.  The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.

File Name:    \Device\HarddiskVolume3\Windows\System32\wbload.dll"

WindowBlinds info:

Your computer has a Windows Experience Index base score of 3.4
Your Windows Graphics Experience score is 3.4

WindowBlinds version : WindowBlinds 6.4 (build 129 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Dell E198WFP(Digital)) 1 is attached to NVIDIA GeForce 8300 GS

Wblind.dll         2009/03/24 12:59:20
Wbsrv.dll         2009/03/24 16:03:02
Wbconfig.exe         2009/02/10 17:28:20
Wbload.exe         2008/03/30 12:27:14
Wbhelp.dll         2007/08/27 11:54:07
Tray.dll              2007/09/12 17:58:21
Wbload.dll              2007/11/04 17:50:28
Screen.exe         2008/06/13 11:24:09

The "About" screen is reporting this version as 6.4 (build 129 x86 - Vista Edition)

I actually thought that IconPackager was the culprit, it still could be, there are issues reported in that section of the forums, but I though I would pass this along.

Thanks,

David

windowblinds
2,863 views 5 replies
Reply #1 from WinCustomize Forums Top

upon receiving advice from The Wiz, am uninstalling WB, rebooting per instructions, cleaning out left-overs, rebooting, re-installing.  Will report back...

Reply #2 from WinCustomize Forums Top

hmm, some of my file dates have changed.  It would appear that when I used Impulse to update WB all this time, I wasn't getting a full set of file updates:

Wblind.dll         2009/03/24 12:59:20
Wbsrv.dll         2009/03/24 16:03:02
Wbconfig.exe         2009/03/24 16:04:20
Wbload.exe         2009/03/24 16:04:14
Wbhelp.dll         2009/03/24 16:04:07
Tray.dll              2009/03/24 16:04:21
Wbload.dll              2008/04/28 11:34:28
Screen.exe         2009/03/24 16:04:09

ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from WinCustomize Forums Top

It would appear that when I used Impulse to update WB all this time, I wasn't getting a full set of file updates:
End of quote

 

maybe not necessarily

I noticed a long time ago with SDC - there was a difference between 'updating' and 'uninstalling/rebooting/reinstalling' on the dates - I seem to recall Neil saying on 'updating' only the files that needed changing were changed - so even if the was a newer dated file, if it was the same as the old file - no point in updating it 

- I'm thinking Impulse is the same way - I installed WB 6.3 with SDC, updated to 6.4 with Impulse and now I show:

 

Wblind.dll         2009/03/24 16:04:20
Wbsrv.dll         2009/03/24 16:04:58
Wbconfig.exe         2009/03/24 16:04:20
Wbload.exe         2008/04/28 12:35:14
Wbhelp.dll         2008/04/28 12:35:07
Wbui.dll         2008/04/28 12:35:05
Tray.dll              2008/04/28 12:35:21
Screen.exe         2008/07/22 11:10:09

Reply #4 from WinCustomize Forums Top
your wbload.exe is almost a year older than the one I ended up with. Does the newer date on my version mean that this file has been updated at some point? If not, I agree with what you said about 'updating', otherwise, you should have the newer version and something went astray.
Reply #5 from WinCustomize Forums Top

i think the newer dates coincide for a 'new version' possibly for new trials/purchases

 

(and mine is for XP)