WB11 - Incompatible with Windows Search?

Error generated by Widows Search Box in Taskbar prevents Explorer.exe from launching on alternate startups

from Stardock Forums

When starting Windows 10, after log-in there is a black screen instead of desktop. After force-shutdown, Windows launches normally, going to desktop after log-in. I must always startup twice to get the desktop. Plus, I keep my taskbar at the top, but after successful restart the taskbar is often reset to the Left side. 

Disabling 'Stardock WindowBlinds' in Services allows normal startup without error or black screen. (Also: Disabling Start11 with WB11 enabled does not resolve the problem. However this problem did seem to begin with an ~early-April update of Start11.)

This occurs when Windows Search box is Hidden in Taskbar settings.

Widows Log recorded this error on each WB-enabled startup (my emphasis):

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10010</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2026-04-20T17:33:48.9181162Z" /> <EventRecordID>184236</EventRecordID> <Correlation ActivityID="{b89ebc96-815b-4072-a563-eb0b43cbbd39}" /> <Execution ProcessID="1444" ThreadID="11188" /> <Channel>System</Channel> <Computer>ASROCK370</Computer> <Security UserID="S-1-5-21-2481096253-2108667185-4035526888-1001" /> </System> - <EventData> <Data Name="param1">Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!ShellFeedsUI</Data> </EventData> </Event>

 

 

windowblinds
256 views 7 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. First, please try, uninstall Windowblinds, reboot immediately (important), download latest version available in your account product download page: https://store.stardock.com/myaccount/products.  Install it, reboot immediately again. Retest it and report back.

If the issue still appear, please post additional information.

  1. Windows 10 full version and OS Build number. Please use Winver.exe to get these number.
  2. Windowblinds full version numbers.
  3. The issue appear on any theme that come along with Windowblinds?
  4. Post a video showing the issue might help us understand the issue better.

Thank you,
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

OS: 22H2 19045.7184

WB: WindowBlinds 11.07 (024 - Windows 10 Edition) - 64 bit OS. Downloaded 4/24/26

Appears on all of the following: (Not all are Stardock): Acrylic7, Echo, Simple, Ansaro, Precision, Corporate, Modern, Windows 8, Windows 8 Metro, Luna (Danioc), Windows Classic. Does not yet seem to appear on "Default" style.

 

 

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

Have you done the uninstall, reboot, reinstall steps?

Thank you,

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Yes, done before testing the styles in the list.

Are you affiliated with (or do you work for) Stardock, or are you a self-appointed 'community advisor'?

Reply #5 from Stardock Forums Top

Hello, I’m not a self‑appointed advisor. I’ve been officially assigned by Stardock as a Community Assistant to help moderate discussions and provide support here. My role is to act as a middle point between community members and Stardock’s Support and Development teams. Before passing issues along, I’ll first try to help resolve them with the troubleshooting steps and guidance available, so we can often address concerns more quickly.

Moving forward, would like to suggest Clean Boot refer here: https://support.stardock.com/space/SHC/1334935592/Start11+Clean+Boot. Do know that clean boot need to be done with care. Try it and report back.

Thank you,

Basj,
Stardock Community Assistant

 
Reply #6 from Stardock Forums Top

So, clean boot and look for what?  

I have already reported that normal boot with WB11 disabled in Services eliminates the problem. I do not see how a clean boot will be useful, since that is typically used to identify a service or app that causes or is related to the problem. I have in already located the offending service: Stardock WindowBlinds and/or Windows Search Shell Feeds UI in the Taskbar.

And as I have already reported, I have deferentially tested Start11 against WB11 (because the problem apparently started with a recent Start11 update), by 1-disabling both, 2-disabling Start11 but enabling WB11, and 3-Disabling WB11 but enabling Start11.  Result: whenever WB11 is enabled = Explorer.exe crashes at startup owing to an error in the Windows Search box Taskbar UI, as indicated in the error message I supplied.

So, why should I do a clean boot in order to track down the offending service/app when I have tracked already tracked down the offending service for you, including the point in the
Windows Startup sequence where the offense occurs: 

Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!ShellFeedsUI  -ONLY WHEN- WindowBlinds11 is enabled. Error Code 0x8080000000000000 (system file corruption?), likely caused by or through WindowBlinds11. (Speculation: System File corruption that is initiated by one newly-incompatible WB Style, possibly being perpetuated across subsequent, healthier style selections, so that one instance of a bad style might be corrupting all subsequent style selections.)

Please forward this information to Stardock Developers.

DanMS

 

Reply #7 from Stardock Forums Top

Hello,
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