You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
After installing Open-Shell it starts and Win 10 freezes. I can press Ctrl-Alt-Del to start Task Manager and change active programs (started before Open-Shell installation), restart system, but cannot start new programs. Ending Opens-Shell's running task in Task Manager leads to its restarting.
This happens since installing Win 10, on all versions of Open-Shell (160, 170, 190) on one of my PCs - HP Spectre x360 14. Apparently it is some driver problem.
If you advice me how to stop the execution of Open-shell I could: Start an event-logger, Start Open Shell, Stop again Open-Shell and send you the result file. Or I can start the event logger before starting the installation of Open-Shell , but how to stop the Event logger in that case (to save the event log in a freezed PC)?
Please advice hot to run the event logger and which file to send to you?
P.S. I can actually start File Explorer (through Task Manager-Open location on some running processes) and start by it any executable program while PC is freezing.
If you are able to start Task manager then please create dump from Windows Explorer process (right-click on the process and select Create dump file) and attach it here (or send to me directly to ge0rdi (at) gmx.com).
If you are able to start Task manager then please create dump from Windows Explorer process (right-click on the process and select Create dump file) and attach it here (or send to me directly to ge0rdi (at) gmx.com).
Thank you for your support!
Please find attached file @link. It has been created according your advice after installing Open shell, giving it time to start, and after having freezed the taskbar.
I can see weird lockup in Open-Shell initialization. Trying to figure out what is going on there.
Though I have noted that you have Start11 and Fences from StarDock running.
Those may possibly interfere with Open-Shell.
Could you disable/uninstall them temporarily to see if that will help with the lockup issue?
Though I have noted that you have Start11 and Fences from StarDock running.
Actually, I have disabled Start11 before installing Open-Shell (there is an option in the app itself). Fences have been left running.
But - I have had this error since I have taken this PC on Win 10, long before I had Stardock's apps. Comming from Open Shell being a longtime user I tried a lot of ways and searched the net to manage it working at my situation, unfortunately without success. I suppose it has to do smth. with some display driver, as all apps I have installed on this PC are the same on my other PC-s, where Open shell works as expected.
I have disabled Start11 before installing Open-Shell
According to the dump it is loaded and running.
Maybe you can try to uninstall it (since you have disabled it already)?
I have had this error since I have taken this PC on Win 10, long before I had Stardock's apps.
I see.
Open-Shell is stuck in its initialization. It tries to get some standard icons which results in some COM call that will then cause our init hook to be triggered and whole thing repeats again and again.
Need to compare it with normal initialization to see what could have caused that behavior.
According to the dump it is loaded and running. Maybe you can try to uninstall it (since you have disabled it already)?
Uninstalled Start11 completely... and Open-shell started as expected. I thought - may be I have been wrong and Start11 is misbehaving :( Restarted several times, played with Open Shell and customized it, done some work (incl.Windows Update)... and restarted again... and Taskbar again stuck! Hence - Start11 is not the problem.
It is the same issue as before. Still have no clue what's going on :(
You can try to disable other software that is loaded in Explorer:
Stardock Fences
Google Drive Extensions
Dropbox Shell Extension
User Mode Driver for Intel(R) Graphics Technology
I'd try to use Autoruns tool from Sysinternals and disable them one by one, restart machine/explorer and check if something helped. Maybe that would help us to narrow down the issue.
I tried a lot of combinations with Stardock's Start11 and Fences. At some cases Open-Shell was working OK. As there was no obvious pattern of behavior I uninstalled both Start11 and Fences, but after that at PC starting Open-Shell freezed the taskbar again.
So - Stardock's Start11 and Fences are not the problematic apps (as I have already stated, that at the time I first got the problem I had no idea of Stardock apps).
(In the pull-request I mentioned you can see message(s) from AppVeyorBot regarding new build. There is a link that will allow you to get the installer.)
Sorry for answering this late, have been out of town.
Good news - Open-Shell is working perfectly now! :)
Using "OpenShellSetup_4_4_192-dsogbvsu.exe"
NO freezing!
Activity
ge0rdi commentedon Aug 22, 2023
If you are able to start Task manager then please create dump from
Windows Explorerprocess (right-click on the process and selectCreate dump file) and attach it here (or send to me directly toge0rdi (at) gmx.com).theLittlePrinceAD commentedon Aug 22, 2023
Thank you for your support!
Please find attached file @link. It has been created according your advice after installing Open shell, giving it time to start, and after having freezed the taskbar.
As file size is too big please see attached link to Mega cloud.
https://mega.nz/file/t5oWhawC#StH_qyBZTtPnzut5Ywd9r-LzLbRQo7jXUkHJ3BhstWA
ge0rdi commentedon Aug 22, 2023
I can see weird lockup in
Open-Shellinitialization. Trying to figure out what is going on there.Though I have noted that you have
Start11andFencesfromStarDockrunning.Those may possibly interfere with
Open-Shell.Could you disable/uninstall them temporarily to see if that will help with the lockup issue?
theLittlePrinceAD commentedon Aug 22, 2023
Actually, I have disabled Start11 before installing Open-Shell (there is an option in the app itself). Fences have been left running.
But - I have had this error since I have taken this PC on Win 10, long before I had Stardock's apps. Comming from Open Shell being a longtime user I tried a lot of ways and searched the net to manage it working at my situation, unfortunately without success. I suppose it has to do smth. with some display driver, as all apps I have installed on this PC are the same on my other PC-s, where Open shell works as expected.
ge0rdi commentedon Aug 22, 2023
According to the dump it is loaded and running.
Maybe you can try to uninstall it (since you have disabled it already)?
I see.
Open-Shellis stuck in its initialization. It tries to get some standard icons which results in some COM call that will then cause our init hook to be triggered and whole thing repeats again and again.Need to compare it with normal initialization to see what could have caused that behavior.
theLittlePrinceAD commentedon Aug 22, 2023
Uninstalled Start11 completely... and Open-shell started as expected. I thought - may be I have been wrong and Start11 is misbehaving :( Restarted several times, played with Open Shell and customized it, done some work (incl.Windows Update)... and restarted again... and Taskbar again stuck! Hence - Start11 is not the problem.
Please find link to Dump file.
https://mega.nz/file/1tJGFaiZ#kQ1aA0U4Ft9BKCVSEtcQmdhS5jfy8eBfRrGfTLXuTRQ
ge0rdi commentedon Aug 22, 2023
Cannot download the file:
The file you are trying to download is no longer availabletheLittlePrinceAD commentedon Aug 22, 2023
Sorry, my fault! Me stupid!
Link updated.
ge0rdi commentedon Aug 22, 2023
It is the same issue as before. Still have no clue what's going on :(
You can try to disable other software that is loaded in Explorer:
Stardock FencesGoogle Drive ExtensionsDropbox Shell ExtensionUser Mode Driver for Intel(R) Graphics TechnologyI'd try to use
Autorunstool fromSysinternalsand disable them one by one, restart machine/explorer and check if something helped. Maybe that would help us to narrow down the issue.theLittlePrinceAD commentedon Aug 23, 2023
I tried a lot of combinations with Stardock's Start11 and Fences. At some cases Open-Shell was working OK. As there was no obvious pattern of behavior I uninstalled both Start11 and Fences, but after that at PC starting Open-Shell freezed the taskbar again.
So - Stardock's Start11 and Fences are not the problematic apps (as I have already stated, that at the time I first got the problem I had no idea of Stardock apps).
Please find the memory dump file, without Start11 and Fences:
https://mega.nz/file/RsgXSDRT#qU7Zg3k8U0h1SzjCOIdXuv6NGV8N6hur4epf4y7oIW4
P.S. How to disable "User Mode Driver for Intel(R) Graphics Technology"? I have never used Autoruns.
Avoid recursive Start menu initialization (#1675)
ge0rdi commentedon Aug 24, 2023
@theLittlePrinceAD
Could you, please, try build from #1678 PR?
It should avoid endless recursion during start menu initialization.
theLittlePrinceAD commentedon Aug 24, 2023
Sorry, what exactly should I do?
I have been a programmer in the past, but have no idea now :(
I am very keen on helping, as I like Open-shell very much!!!
ge0rdi commentedon Aug 24, 2023
Sorry, for being unclear.
Download
Open-Shellbuild from here:https://ci.appveyor.com/project/passionate-coder/open-shell-menu/builds/47869291/artifacts
And install it to see if it helps in your case.
(In the pull-request I mentioned you can see message(s) from
AppVeyorBotregarding new build. There is a link that will allow you to get the installer.)theLittlePrinceAD commentedon Aug 24, 2023
Sorry for answering this late, have been out of town.
Good news - Open-Shell is working perfectly now! :)
Using "OpenShellSetup_4_4_192-dsogbvsu.exe"
NO freezing!
You are the best!!! I am so happy!!!
ge0rdi commentedon Aug 24, 2023
Cool. Thank you for confirmation.
I will include the fix into next official version (you can keep using the version you have for now).
Avoid recursive Start menu initialization (#1675)