Hello George:
I have similar problem where my Nexus Ultimate keeps chrashing frequently. This issue started once windows 11 upate was pushed on me from 23H2 to 24H2. I see high memory usage alert showingup and the dock crashing. I tried to uninstall and re-install the applicaton multiple times. I searched the forum looking for a work around and it looks like there is none. Windows 11 24H2 update is nothing but useless piece of garbage that raked havoc to my system. What do you propose? In the past, Nexus Ultimate memory consumption never jumped few MBs but now I see 1.6GB and eating up 44% of the memory.
I have few subdocks and it keep crashes and reset to modules.
Obrigado my friend

In your screenshot that's 1.6 *MB*, not 1.6 GB.

That is not correct. For example, here we have 1,706,264KB = 1.7GB

You changed those screenshots. In the original one it said 1.6 MB.

Unfortunately there is nothing to do (other than uninstalling 24H2 and going back to 23H2, for instance) since this is a bug/leak in the OS and not in the application itself.

Not even the infamous "Windows ME" release was anywhere nearly as bad as this big steamy pile of ****. That Microsoft ever officially released 24H2 should tell you all you need to know about the current internal state of that company. My God!

Ok, for the first time Windows Update is offering to update my Windows 11 23H2 version to 24H2. I guess this means the issue with the Assassin Creed games has finally been fixed by Microsoft and they lifted the block?

I understand how important it is for me to do this so I can finally work on all those incompatibility issues between Winstep vs 24H2 but at the same time I'm kind of scared. I don't want to hose my main production system - guess I'll have to do some research now about which issues are still pending in 24H2.

Be scared! Be *very* scared! You really never know what's going to go wrong with M$ and Win 11 next, Jorge. I certainly wouldn't want to risk getting any kind of production system f***ed up that way. Why not use a VM to be safe? Perhaps on your previous box?

Not the same. I know from previous experience you need to have a feel for the issues on a 24/7 ongoing base. Guess I'll have to take the plunge anyway - wish me luck.

I certainly do. Still, I'm sure you'll back up everything first - you know, belt, braces, piece of string...

Well, whether I wanted it or not, the fact is that 24H2 just installed itself without asking my permission first. Typical modern Microsoft, all I can do now is restart my system and watch the world burn...

Sigh.

Argh! Sh...ugar! :/ Too damn annoying, M$. well, don't forget to fiddle while you watch, Jorge. Burn, Baby, burn! (Mind you, we might all yet see that IRL, thanks to certain narcisists... )

And I'm in! God help me!

So, first thing I see is that everything related to the system tray is missing in the NextSTART taskbar, as expected... This is because in 24H2 Microsoft removed everything related to the old systray.

I already changed the code so it brings back the button to pop up the system tray overflow window under 24H2. With luck I can get it to work the same as in 23H2, not perfect, but pretty functional provided you move all non-system tray icons to the tray overflow panel.

And the NextSTART systray is finally working like in 23H2.

Hey, congrats Jorge, great stuff for Win 11 users! Now watch M$ throw another spaniel [sic!] in the works next time...

First they should solve all the issues in 24H2, but I suspect they won't lol

I will have to make a post detailing stuff wrong with 24H2 that affects Winstep software. I have never seen such a train wreck, and this *months* after launch!

Another apparent issue: something as basic as auto-hiding the **Windows** taskbar doesn't seem to be working (not good because it means in certain cases a collapsed shelf docked to the bottom of the screen becomes inaccessible, as it is covered up by a Windows taskbar that should be hidden but isn't - also not good if you are trying to avoid burn in on OLED displays).

I searched online and the "official" solution for this seems to be to restart Explorer via Task Manager (which comes with its own set of issues as some applications will not re-register their system tray icons etc) and is, at best, a temporary solution.

OTOH, the issue that affected incorrect CPU usage reporting in all 3rd party applications that has been plaguing us since 22H2 (which I provided an optional fix in the CPU Meter Settings via the 'Serialize Timer Expiration' setting) SEEMS to have been fixed. Only took them 2 years and two major Window releases, yay!

Another record for Microsoft lol

Anyway, I haven't run into any high memory usage situations with WorkShelf/Nexus Ultimate yet as those reported in this thread, and memory usage numbers seem to be stable. What this probably means is that whatever is leaking memory is probably specific to some configuration users have (i.e. to be clear: the memory leak is not the fault of the Winstep application itself but another bug in the OS, but for it to happen it requires a specific configuration in the Winstep application - or even in Windows itself - which I will need to reproduce here in order to find the culprit and come up with a work-around).

Unless Microsoft fixed this issue in one of the latest updates to 24H2, of course. I need more feedback from Winstep users on 24H2, please.