Hi - has anyone else seen the Powershell error after installing Start11. We have tested this and when Start11 is a bunch of the machines, the error happens. When it is removed, there is no longer an error. We are running Windows 11 Version 10.0.22000.918] and Start11 1.25.
Any help or guidance you can give would be appreciated.
Hello,
Sorry to hear you are having issues.
What do you mean when Start11 is a bunch of the machines ?
AzDudeStardock Community Assistant
We have installed Start11 on about 20 machines and after installing it we now get the Powershell error. Once we uninstall, the error goes away. hope that helps.
I have forwarded your report to the Stardock support team for their review and recommendations.
Please keep an eye on this thread for any updates.
We really do appreciate your feedback, thanks.
How long has the machine been running before shutdown?
Totally varies. Since there are so many, some are a couple of hours, some are longer. The test I just did was boot up, log in and then shutdown and it happened immediately.
Additional data points. Here is the event log just before and when the error happens:
Application popup: powershell.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application.
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
Hope this helps..
Does your computer have any specific tasks it runs on shutdown?
Also does the same happen on reboot?
I have never come across anything like this before to the best of my knowledge so there is something different to a stock install going on.
It happened on reboot and shutdown for all the users (well at least those who have reported). I just uninstalled it on my two machines and have restarted and shutdown multiple times and no error on either. Very odd. We have gotten a number of comments from the users since we rolled out the update on the windows 11 machines.,
Good Afternoon - another data point as I continue to troubleshoot this. If I "kill' the following "SmartMenuExperienceHost.exe" then there is no error. If it restarts or is in "suspended" the error exists.
Thats a Microsoft process not a Start11 one so thats especially odd.
Correct. But as soon as I uninstall start 11 there is no error whatsoever
going to open up a ticket since we have premium support
I have been looking for a solution to this problem for a long time. This error only occurs when you shutdown using the "windows start button", you use the "start11 button" or "Windows+X＂ Shutdown or reboot without powershell error. I have tested many times by reinstalling the system and only once the error did not appear, but I could not reproduce it.
Can you help me understand this a bit better:
The native 'Windows Start Button' - by way of Ctrl + Clicking the Start11 button? If that is the case, in what cases would you be using the native Windows Start button?
Of the ‘40 users’, is there anything about them that are unique to them - for example, are there logoff scripts that run for them but not others? Do they have restricted permissions where others (you, who cannot reproduce it) do not?
For the ones that do see it, as a test, try killing Start11_64.exe from taskmanager and then trying to shut down. Is the error seen then?
Sean DrohanStardock Product Lifecycle Manager
Hi Sean - if I kill Start11_64.exe I do not get the Powershell error. I am only using the START button from START11. Hope that data helps.
Hi Sean.Willing to help you.
I turned off the start button for Start 11, so I didn't use it. keep using The native 'Windows Start Button' .
Like I said above, strangely it only appears on the native 'windows start button'. Shutting down the computer using other methods does not have this error.
I have replied to one of your tickets a few times. Have you seen them?
[引用谁=“sdRohan” 回复=“17” id=“3868861”]
我已经回复了你的一张票几次。你见过他们吗？
肖恩·德罗汉Stardock 产品生命周期经理
我看到了。问题似乎与某个硬件有关，我在 VM 中对其进行了测试，没有出现问题。[/引用]
[/引用]
I see it. The problem seems to be related to some hardware, I tested it in the VM and there was no problem.
Hi Sean - I have also responded back. Even the newest version does the same thing, unfortunately we have it on about 80 machines now.
Did you see this answer from another user?
I did but not sure it applies since it was vague. We have many Lenovo laptops and it happens in all.
Would be great to get some definitives at this point.
Understood but only Lenovo laptops, all your other PC installs do not see the issue.
I can pick this back up in your ticket if you can confirm that someone is monitoring it and will respond to it.
Sean - we only have Lenovo laptops. I have been responding to the posts so not sure if there was something wrong since they kept getting closed. I will go in and respond to the ticket as soon as I am done responding to this post.
I have responded to SSN-38033.
There are many great features available to you once you register, including:
Sign in or Create Account
