Solved Severe Open-Shell Problem on Win11 24H2 When System Resumes from Sleep. Any fix?

hdmi · Dec 30, 2024

Rollback_Jockey said:
Have you made any effort to check if the underlying OS is healthy? This is clearly NOT an OpenShell problem.

As a matter of true fact, the Windows 11 taskbar never was healthy, and today it still isn't. It has what I like to call "Panos Panay virus/windemic". lol That's why I always recommend to use ExplorerPatcher's Windows 10 (ExplorerPatcher) taskbar style option if running on Windows 11 version 24H2 or, if running on version 23H2, Windows 10 taskbar style option. YMMV

BuddhaNature · Dec 30, 2024

hdmi said:
On systems that support Modern Standby

I had a look at this myself a couple of days ago. My system firmware does not support Modern Standby ('sleep zero' mode — S0 mode). Got this information through PowerShell command> powercfg /a

And I will have to leave that at that.

I also have hibernation disabled on the system as I don't want Fast Startup or Hybrid Sleep operating on the system.

Also today, I reverted all "Recommended" settings made by O&O ShutUp back to "Factory Settings". And from Winaero Tweaker I reverted to system defaults the three tweaks that I made with that. Those three tweaks were:

Windows 11 > Enable Ribbon. "Permanently enable classic File Explorer with Ribbon."
Advanced Appearance Settings > Scrollbars. This sets File Explorer scrollbar width and the size of scrollbar buttons.
File Explorer > Automatic Folder Type Discovery. "Disable automatic folder type discovery."

I then rebooted the system and did some test sequences of resume from sleep. The issue showed up again. From this I take it that O&O Shutup10++ settings were/are not the issue. The tweaks I was using in Winaero Tweaker were/are not the issue.

From there I then (once again) applied the "Recommended" settings in O&O ShutUp. Though in Winaero Tweaker I only applied one of the tweaks I had applied before. That tweak was:

File Explorer > Automatic Folder Type Discovery. "Disable automatic folder type discovery."

I decided not to apply the other two tweaks as they do target File Explore.r and the taskbar is, as far as I am aware, is also an Explorer process — at least Task Manager treats things as if that were the case.

After doing that I rebooted the system and have been testing resume from sleep for most of the rest of the day and, Glory be!, there has been no recurrence of the issue so far. That said, the problem is intermittent so it might turn up again, on the other hand maybe not.

Your Task Scheduler suggestion I will keep under my hat in case the issue does occur again. Thanks very much for taking the time to type all that out.

hdmi · Dec 30, 2024

BuddhaNature said:
I had a look at this myself a couple of days ago. My system firmware does not support Modern Standby ('sleep zero' mode — S0 mode). Got this information through PowerShell command> powercfg /a

And I will have to leave that at that.

I also have hibernation disabled on the system as I don't want Fast Startup or Hybrid Sleep operating on the system.

Also today, I reverted all "Recommended" settings made by O&O ShutUp back to "Factory Settings". And from Winaero Tweaker I reverted to system defaults the three tweaks that I made with that. Those three tweaks were:

Windows 11 > Enable Ribbon. "Permanently enable classic File Explorer with Ribbon."
Advanced Appearance Settings > Scrollbars. This sets File Explorer scrollbar width and the size of scrollbar buttons.
File Explorer > Automatic Folder Type Discovery. "Disable automatic folder type discovery."

I then rebooted the system and did some test sequences of resume from sleep. The issue showed up again. From this I take it that O&O Shutup10++ settings were/are not the issue. The tweaks I was using in Winaero Tweaker were/are not the issue.

From there I then (once again) applied the "Recommended" settings in O&O ShutUp. Though in Winaero Tweaker I only applied one of the tweaks I had applied before. That tweak was:

File Explorer > Automatic Folder Type Discovery. "Disable automatic folder type discovery."

I decided not to apply the other two tweaks as they do target File Explore.r and the taskbar is, as far as I am aware, is also an Explorer process — at least Task Manager treats things as if that were the case.

After doing that I rebooted the system and have been testing resume from sleep for most of the rest of the day and, Glory be!, there has been no recurrence of the issue so far. That said, the problem is intermittent so it might turn up again, on the other hand maybe not.

Your Task Scheduler suggestion I will keep under my hat in case the issue does occur again. Thanks very much for taking the time to type all that out.

I highly doubt that the scrollbar width and scrollbar buttons size was the culprit, but it still could be. When I was experimenting with this tweak a few years ago I found that changing these sizes to 17 pixels or larger was causing misalignment issues in some places. So, I wrote my own batch script (that needs to be run as an Administrator to work). It changes both of these settings to 17 pixels without it causing those issues, at least for me.

Batch:

reg add "HKCU\Control Panel\Desktop\WindowMetrics" /v ScrollWidth /t REG_SZ /d -260 /f
reg add "HKCU\Control Panel\Desktop\WindowMetrics" /v ScrollHeight /t REG_SZ /d -260 /f
pause

I keep automatic folder type discovery disabled too BTW. I use ExplorerPatcher to get the File Explorer with the Ribbon back, but since you don't want ExplorerPatcher, you could try the registry tweak from Option Three in this tutorial:

Restore Classic File Explorer with Ribbon in Windows 11

This tutorial will show you how to restore the classic File Explorer with Ribbon for your account or all users in Windows 11. File Explorer in Windows 10 has a ribbon, tabs, and a title bar with color. The ribbon includes common tasks, such as copying and moving, creating new folders, emailing...

www.elevenforum.com

(There's two separate .reg files that you can download from there (one to apply the tweak, one to undo it.)

As for the task in Task Scheduler. On systems that support S3 Standby, choose Power-Troubleshooter as the Source (as opposed to Kernel-Power), and choose 1 as the Event ID (as opposed to 507).

BuddhaNature · Dec 31, 2024

hdmi said:
As for the task in Task Scheduler. On systems that support S3 Standby, choose Power-Troubleshooter as the Source (as opposed to Kernel-Power), and choose 1 as the Event ID (as opposed to 507).

Thank you for the guidance. My PC does have S3 Standby and, I assume that is what is used when I send the system to sleep.

I have set up the Scheduled Task as advised using Power-Troubleshooter and Event ID 1. I have tested it as working from within Task Scheduler using the right-click Run function and it runs fine. Now I have to wait on the intermittent issue occurring and see if the Task runs fine for that in the wild (so to speak).

If the issue recurs I will update this thread to give the information on whether or not the scheduled task worked.

Many thanks again.

BuddhaNature · Jan 1, 2025

Well I spent a good part of yesterday sleeping and resuming the system and it seemed that the problem did not recur. Then I got to thinking that a 5 second delay on the task was maybe too fast and perhaps preventing me from seeing the task working by the time I got to view the Desktop on resume from sleep. So I set the delay to 30 seconds and tried sleep/resume tests again, without success — it seemed the issue wasn't recurring.

Today I did another test, the issue occurred, and I saw the scheduled task work just as it should. Yippee! So now I've set the delay back to 5 seconds and see how I get on with that.

In any case, I'll mark this thread as 'Solved' now that I have a workaround that does work. Thank you very much @hdmi for the help — greatly appreciated.

All above said, if anyone ever finds out what the cause of the issue is in the first place please do post here.

hdmi · Jan 1, 2025

BuddhaNature said:
, if anyone ever finds out what the cause of the issue is

It's Panos Panay.

See: IT Jobs Explained With A Broken Lightbulb

BuddhaNature · Jan 2, 2025

hdmi said:
As for the task in Task Scheduler. On systems that support S3 Standby, choose Power-Troubleshooter as the Source (as opposed to Kernel-Power), and choose 1 as the Event ID (as opposed to 507).

I have spent most of this morning looking into the Task Scheduler and Event Viewer of Windows to try to understand better your advice on setting a scheduled task and how it all slots together. While researching that I think I discovered a mistake in you advice. The mistake concerns using the Kernel-Power event as a to take an action.

You say it is possible to use Kernel-Power Event ID 507 as the resumed from sleep flag. However, in digging into this I couldn't find any such events in my Event Viewer 'System' logs. What I did find though were Kernel-Power Event ID 107 events and these were to do with resume from sleep.

I'm just making the point here in case some other unfortunate user runs into the same issue I reported in this thread and tries Kernel-Power Event ID 507 as a trigger. It won't work, need Event ID 107 if going down the Kernel-Power route.

If I'm mistaken in this please do correct me @hdmi. And, I mean no offence by what I have written here — your help remains immense!

That said, I have some reservations on if 107 would work. I think if that was being used as the flag then a fairly long delay in exiting and launching Open-Shell anew would have to be made as the 107 log is made at (on viewing of my own log) some 10 to 20 seconds before the Power-Troubleshooter 1 event gets logged — so I'm thinking there might be some time lag from the 107 event being logged before the system is sufficiently 'initialised' for the workaround to work (hope I have expressed that clearly). But I'm just guessing on this and don't know if I'll ever get around to testing my theory. If anyone has any comments on this I would be happy to hear them.

Thanks again!

hdmi · Jan 2, 2025

BuddhaNature said:
I have spent most of this morning looking into the Task Scheduler and Event Viewer of Windows to try to understand better your advice on setting a scheduled task and how it all slots together. While researching that I think I discovered a mistake in you advice. The mistake concerns using the Kernel-Power event as a to take an action.

You say it is possible to use Kernel-Power Event ID 507 as the resumed from sleep flag. However, in digging into this I couldn't find any such events in my Event Viewer 'System' logs. What I did find though were Kernel-Power Event ID 107 events and these were to do with resume from sleep.

I'm just making the point here in case some other unfortunate user runs into the same issue I reported in this thread and tries Kernel-Power Event ID 507 as a trigger. It won't work, need Event ID 107 if going down the Kernel-Power route.

If I'm mistaken in this please do correct me @hdmi. And, I mean no offence by what I have written here — your help remains immense!

That said, I have some reservations on if 107 would work. I think if that was being used as the flag then a fairly long delay in exiting and launching Open-Shell anew would have to be made as the 107 log is made at (on viewing of my own log) some 10 to 20 seconds before the Power-Troubleshooter 1 event gets logged — so I'm thinking there might be some time lag from the 107 event being logged before the system is sufficiently 'initialised' for the workaround to work (hope I have expressed that clearly). But I'm just guessing on this and don't know if I'll ever get around to testing my theory. If anyone has any comments on this I would be happy to hear them.

Thanks again!

On systems that support Modern Standby, the Event Source is Kernel-Power and the Event ID is 507. Whereas on systems that support S3 Standby, the Event Source is Power-Troubleshooter and the Event ID is 1. (In both cases the Log Name is System.) As you know, it is possible to find out whether the system supports Modern Standby, i.e., Standby (S0 Low Power Idle) or supports Legacy Standby, i.e., Standby (S3), also commonly referred to as sleep, although Microsoft also likes to use nomenclature such as Modern Standby sleep session, etc. so, sleep can sometimes tend to be a bit of an ambiguous term.

BuddhaNature · Jan 2, 2025

Okay @hdmi. Thanks very much for the clarification and further information. I understand things better now. :0)

Rollback_Jockey · Jan 5, 2025

For reference a new version of OpenShell has just been released.

pietcorus2 · Jan 6, 2025

Its 4.4.195 ( beta-version ).......... :wink:

BuddhaNature · Jan 7, 2025

Well colour me sad. After having this problem on my Desktop PC with 24H2 today I started working on my Laptop and installed 24H2 to that. Dash! I have the same problem involving Open-Shell on the laptop too. Same workaround Scheduled Task 'solution' on resume from sleep works though, so not all is lost. Two machines, same problem with 24H2 for me. Double-dash!

Rollback_Jockey · Jan 7, 2025

BuddhaNature said:
Two machines, same problem with 24H2 for me. Double-dash!

5 Machines here, all clones and not one single issue with OpenShell.

Now you're having problems on 2 machines that rules out a system issue for certain. Very odd.

BuddhaNature · Jan 19, 2025

I have been swithering on whether or not to post this in case I provoke the Fates and Sod's Law gets applied but the problem with Open-Shell on resume from sleep has vanished as mysteriously as it first appeared.

It stopped happening on 09 January and this on both my Desktop PC and my Laptop machine. Once it dawned on me that it wasn't occurring any more I disabled the Scheduled Task I was using as a workaround to see how things would go. All went fine and this was while still using Open-Shell v4.4.194.

A few days after that Open-Shell v4.4.195 was released and I updated to that and still the problem has not recurred.

I am completely baffled as to what caused the problem in the first place and to what 'fixed it' in the second place, but pleased that all is working fine now. Computers, it seems, still do release small quantum packets of joy now and then, even if not so assuredly on 24H2.

Rollback_Jockey · Jan 19, 2025

4.4.195 was out of Beta within 3 days, i installed it and am yet to have any issues. Build log is not clear what was changed, they may have just elevated it to release.

pietcorus2 · Jan 19, 2025

Works fine in 23H2 , together with latest SAB............

Spunk · Jan 19, 2025

I have been running Windows 11 24H2 since it came out With Open-Shell without any problems. After a major Windows update,
I do have to run Open Shel Menu settings and it automatically resets it.
Be sure you are running the latest version of Open-Shell 4_4_195

Solved Severe Open-Shell Problem on Win11 24H2 When System Resumes from Sleep. Any fix?

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer