wbload.dll in WindowBlinds 10 does not meet the Microsoft signing level requirements

from Stardock Forums

Hi,

I have about 50 of these event ID 3033 errors in Event Viewer at Microsoft>Windows>CodeIntegrity>Operational every day on my windows 10 PC with WindowBlinds 10.88 installed. They are either:

Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\System32\dllhost.exe) attempted to load \Device\HarddiskVolume3\Windows\System32\wbload.dll that did not meet the Microsoft signing level requirements.

or

Code Integrity determined that a process (\Device\HarddiskVolume3\Program Files (x86)\Microsoft\EdgeWebView\Application\147.0.3912.98\msedgewebview2.exe) attempted to load \Device\HarddiskVolume3\Windows\System32\wbload.dll that did not meet the Microsoft signing level requirements.

I looked at the certificate for wbload.dll. Windows says the certificate is ok, although it expired in 2022. Strangely there are no errors about wbload2.dll or wbload.dll and wbload2.dll that are in SysWOW64. Their certificates are ok but expired in 2022.

I have no issues at all with WindowBlinds. It works great.

Do the errors mean wbload.dll is being blocked? What issues would these errors be causing ?

I suppose it's useless trying to exclude msedgewebview2.exe from being skinned in windowblinds to see if that removes the error because the next update for it would stop the exclusion working as the new file would be in a different location? It's annoying since WindowBlinds can't skin Edge anyway.

How do I find out which process is calling dllhost.exe?

 

 

 

windowblinds
284 views 3 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

protected processes do not allow non MS signed dlls into them.  This is probably why you get that error.

It is not a problem, it is just logging that the OS blocked it.  We cannot block the loading and exclusion would make no difference as in order to process the exclusion we would have to load the code which is being blocked.

You can just ignore it.

There was also a case of some dlls not being date countersigned which could also be the trigger of this.  This was changed in later versions of WB, but either way it shouldn't be causing any issues for you.

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top
Quoting Neil Banfieldreply 3992763

You can just ignore it.


Not really, I think this might cause steam client to "crash" with error 0x3000. Does not happen every time, and it only started after the last WB update as far as I remember. Now it got so annoying I decided to look into it. And this is only thing I found. So steams CEF component/W11 update or something decided that the dll injection is too much and don't want to continue.

So steam can't start and asks me to try starting it again and then starts without problem. Really annoying having to do it every single windows start.

Code Integrity determined that a process (\Device\HarddiskVolume7\progs\pelit\Steam\bin\cef\cef.win64\steamwebhelper.exe) attempted to load \Device\HarddiskVolume4\Windows\System32\wbload.dll that did not meet the Microsoft signing level requirements.