The working properties is for the desktop shortcut (I moved it to another folder off the desktop), and the not working properties is for the original gridstack entry.

I restarted my computer to test something on Windows 10 and when I rebooted Windows 11 the Grid Stack link to the TFD Launcher shortcut also stopped working. I tried recreating the shortcut and the link in the Grid Stack and was not able to get it to work again. It does still work if I launch it directly from the desktop shortcut.

Very strange, especially the shortcut version that was previously working fine no longer working after a reboot.

1. Is that the only application you are having trouble launching?

2. What version were you running before this beta? The previous beta?

3. How did you add the desktop shortcut (.lnk file) to the Grid Stack (shortcuts normally are resolved automatically)? Did you use the new ALT key pressed method?

4. Since the launcher is actually running, could it be that it is being launched minimized?

That is the only application that is causing a problem. I did have a problem with this application not launching at all from Start11. The only way I could get it to work was to pin a shortcut to Start11. That is where I got the idea from. An update to Start11 solved that problem about a year ago. I don't know what they changed. It has always worked fine with Winstep Xtreme.

I was running the previous beta on Windows 10 and Windows 11 without a problem.

I used the "Insert New Grid Stack Item" command from inside the Grid Stack. The Grid Stack is on my Taskbar. In Windows 10 I was using a Shelf and it would not work from that either.

I tried clicking in several areas where the launcher window would be and nothing happens. It doesn't show on the taskbar and clicking where it should be also does nothing.

I don't know if this will help. Since Windows 10 when you move the mouse pointer inside the launcher window the mouse pointer would disappear when you moved it. Before Windows 10 that did not happen.

It appears it may be a WorkShelf problem. If I add the TFD Launcher to Quick Launch or the NextStart Menu it works ok. It doesn't work when launched from a Dock, Shelf, or a Drawer.

After even more testing the shortcut version is now working again.

I did try a new video card driver. That did not solve the problem.

Alt/Tab shows an empty, I assume a transparent, window that I can close.

Since I do have several workarounds, don't feel that you have to solve this problem before your desired end of month date to release a final version.

Actually I did change something in the routine that launches applications to solve another issue, and since I haven't worked on NextSTART lately I did not re-compile it, so it is still the same version as the previous beta (i.e. the old code).

I think I know what might be causing the issue, and if I am right you might have the same problem launching that item from NextSTART in the official release.

So, I've changed a little something in the launcher code to prove my theory, please download the beta again from the links in the previous post (should now say Beta 7 for Xtreme, I have not changed the Nexus Ultimate beta) and see if you can run the launcher from WorkShelf now (try BOTH the item with the shortcut and the one that points directly to the executable), then please let me know.

Thanks! That solved the problem for both the direct link and the shortcut. I tested it on Windows 10 and Windows 11 with Start11, Windowblinds 11, and ExplorerPatcher.

Thanks for the quick feedback.

This had to do with how ShellExecuteEx handled a pointer to a null string vs. an actual NULL (0) being passed as the working directory. One of those things you think it's the same but actually isn't.

Down the track you'll have to tell me how you managed to get Start 11 and Winstep to not try and occupy the same space and doing some weird and wonderful placement or disappearing acts (without shifting the taskbar of one or the other to a different location i.e.).

Winstep Xtreme, Start11, and Windowblinds 11 actually work very well together. There are many Winstep Xtreme themes based on Windowblinds themes, and using the three programs together gives you a matching Taskbar, Start Menu and Explorer. Plus you get all the great benefits of Winstep Xtreme.

Start11 simply gives you the choice of seven different Start Menus, each with different substyles. Winstep Xtreme simply displays what ever you have chosen. If used with Windowblinds, the Start Menu (I believe only the Windows 7 style) is also skinable. Start11 also allows you to move the Windows Taskbar to the sides or the top on Windows 11.

The only issue I have with the Taskbar is a slight flickering or resetting when closing full screen applications. The only time that the Taskbar has disappeared was when I was changing Windowblinds themes on Windows 11. I think it is because I am also using ExplorerPatcher (I don't have this problem when I don't use ExplorerPatcher). Logging out and back in solves that problem. In my experience, Winstep Xtreme treats the Taskbar exactly the same whether it is skinned or not. I have also used it with the Windows Taskbar on the botton and the Winstep Taskbar on the side (Ubuntu style) or the top (Mate style). On the Winstep Taskbar you can hide the System Tray and the Tasklist and just use the Quick Launch area for applications or Grid Stacks. You could also have two Taskbars on the bottom, top, or side.

I use ExplorerPatcher to change Windows Explorer on Windows 11 to the Windows 7 style because the multi tab Explorer doesn't always skin very well.

Stardock seems to have fixed the issues with Windowblinds that people commonly complained about years ago. I have experimented with just about every setting. I have changed fonts, colors, start buttons, and styles and was able to restore everything back to the original Windows look without issue. It has never corrupted my system in the two years that I have been using it. They even have a check box to always use the OS start button rather than the style one (a common complaint was you couldn't get the Windows start button back). Like Winstep they also have a great forum, and Jorge also pops up there occasionally.

Bugger, miss a couple of days and suddenly there are dozens of posts! Don't know when I'll be able to catch up, had a bad fall Friday morning and have concussion, fell on my nut. :/ Bloody nuisance. Back ASAP.

OMG! You're ok? Rest man... and be on the look out for weird symptoms, just in case.

Not too, too bad, thanks Jorge. Nausea's gone, but still get a headache all the time so lots of paracetamol. Nothing weird. Sleeping a lot and have the place darkened. Taking it easy as much as possible.

If it doesn't get better soon please get it checked out... can't mess around in our age bracket.

You seem to have it down well.
I use only nexus Ultimate with Start 11 and Winstep on another login without it. I have got used to that. I found one or the other would lose its taskbar when attempting Start 11 with Winstep. I also accept it is more than likely the way I have set my system up.
Start 11 taskbar kept auto hiding and would not come back regardless of whether auto-hide was off in both winstep and Windows 11, it still auto-hid for me with Winstep also running. It's probably PEBCAC
(Problem Exists Between Chair And Computer)