rounk-ctrl/TranslucentSM

TranslucntSM cannot be started after upgrading to 26100.1297

huashan233 opened this issue · 12 comments

I can't start TranslucntSM after upgrading to 26100.1297, the process ends immediately after opening the start.exe and the start menu gets stuck for a while before it regains response

I concur with this issue.
Started after I upgraded to 22631.3958 yesterday.

From the Event Viewer -

Faulting application name: StartMenuExperienceHost.exe, version: 10.0.22621.3958, time stamp: 0x77b900e4
Faulting module name: StartTAP.dll, version: 0.6.9.0, time stamp: 0x66215a1a
Exception code: 0xc0000005
Fault offset: 0x00000000000091a4
Faulting process ID: 0x0x17C4
Faulting application start time: 0x0x1DAE003216E8642
Faulting application path: C:\WINDOWS\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe
Faulting module path: D:\Program Files\TranslucentSM\StartTAP.dll
Report ID: 494b10db-e631-43f9-9ae4-9184e46ae72c
Faulting package full name: Microsoft.Windows.StartMenuExperienceHost_10.0.22621.3958_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App

The same problem as HarlingtonTigers. Updated yesterday to 22631.3958 and the program stopped running!

Same here after installing KB5040527 and KB5041169

huh, ill check

Same here, hope you can figure something out!

Same. Nothing works.

Same. It happens with version 0.6.5 and 0.6.9 only.
Downgrade to version 0.6 works for me (except Hide Recommended causes crash).

That is a good find.
I can concur that 0.6 works for me. Although it is not the latest version it will do until a solution is found to the problem.

Somehow for me, the Start menu crash happens even after unistalling this app. Installing the old version of the app, doesn't help either.

Just a thought here.
If you actually use the options added in 6.5 and 6.5.9 then it will crash. I found that.
Have a look at your reg entries. You might need to switch HideSearch and/or HideRecommended to 0.

Just a follow up for this feature request.

Downgrade to 0.5, it still works on Windows 11.
Thanks to #35 Meqr1 for this insight :)