mackid1993

Check your indexing settings, searching for reg pulls up registry editor for me. You can add custom start orbs, this already exists. The start menu is essentially as it was in Windows 7, this is how Windows 7 behaved. I doubt this will be changed since it works as expected. Right click and shutdown, restart from there. I'm not the dev, but I think he has bigger things to work on right now re: taskbar. Why not just use Open-Shell for this?

I agree, because Start11 wasn't affected. Start11 has a fully reimplemented taskbar. SAB will likely have the same as Tihiy already reimplemented the systray. It's the only way to not play a cat and mouse game with MS, patching the Win 11 taskbar isn't sustainable as it will contently break any time a change is made which frequently happens in the beta channel. Based on my understanding reimplementation is the only solution. We've known this was going to be an issue for a while so hopefully a beta will be ready before 24H2 is released.

No, Explorer Patcher was flagged as well with the same block. They are flagging anything that restores the Windows 10 taskbar. This has nothing to do with Russia, if you look at the forum Tihiy is based in Mauritius now and moreover I get the feeling he probably hates the bald **** as much as we all do. It's likely that he is working on a taskbar rewrite given that updates have been fairly quiet lately, the system tray rewrite was amazing so if he is rewriting the taskbar I'm personally very excited.

I wonder what the long term fix for this is going to be? I wonder if @Tihiy will just call the installer setup.exe to get around this.

Seems like they are going after Explorer Patcher too. https://github.com/valinet/ExplorerPatcher/issues/3088

Rename the installer to anything else, even TotallyNotStartAllBack_setup_3.7.8.exe will work.

I just tried to use Win 11 for a day without SAB and while it's now passable because of the taskbar icon ungrouping, SAB just makes things 👨‍🍳!

@Tihiy can you rename the installer to StartAgainBackwards.exe and see if it slips by them? Edit: In all seriousness just rename the installer to setup_3.7.8.exe. Microsoft can't block setup.exe.

I guess now we wait for an official answer. Hopefully it's fixable with a patch.

I'm wondering if Microsoft is targeting SAB? If so how would @Tihiy get around that? I guess we'll find out soon! Edit: @rseiler if you uninstall SAB, update and reinstall SAB what happens? I'm wondering if the classic taskbar is totally gone now.

I wonder if this is the end of the classic taskbar.

It's safest to play with canary in a VM not on bare metal.

Well it's patching explorer and you are running a pre-production build where changes are being made to explorer. What would you expect? Everything to completely work 100% of the time? This is why when using software like SAB it's best to stay on production as I'm certain Tihiy is testing every Canary build in a VM for major issues and patching them before they can make it down the pipeline to prod. I would advise against using Dev or Canary on your main machine, explore it in a VM safely where there's no risk of data loss or other issues.

I can confirm this is fixed. Thank you @Tihiy for looking into this again. Thanks @Dart Vanya for the assist!

I wonder if he uninstalls Windows Terminal if it will fall back to Command Prompt?

It's never safe, any build can break it. Right now other users have reported things working on 26090 and that's all we know. There is a new feature flag called DisableWin10Taskbar that's enabled by default. SAB 3.7.7 bypasses this but we don't know if this means the classic taskbar will be removed soon and if so what can be done to replace it.

Strange, sorry! Edit: Just disabled dark magic and this doesn't happen anymore. Strange that it occurs when DM is on, must be a conflict with something on my system.

So I found a nasty Dark Magic edge case when taking ownership of a file. This doesn't happen when Dark Magic is disabled. I've tested this in Directory Opus. When the error is dismissed Directory Opus is left in a completely frozen state and needs to be killed. This also happens with Explorer which also causes a freeze which requires an Explorer restart.

Looks like mica acrylic to me, do you have Dark Magic on? There have been some changes recently with that. Edit:

Wow, maybe they aren't removing the code? I'm wondering if it's still there because they just can't remove it due to some sort of old Vista spaghetti code keeping it hidden there. Hence the feature flag to break it and not just stripping it out like they did with the system tray. There must be something that will break if they remove it otherwise it would have been gone already OR they realize that their most dedicated users still like it and it's not harming anything so they are throwing us a bone. One of the two. It probably doesn't help that there's yet another new person in charge of Windows and Surface. If they'd just add small taskbar buttons and provide some API to allow for overlays on the taskbar so apps like Traffic Monitor and NetWorx work correctly and don't have icons overlap them I'd use the Win 11 taskbar. If it is removed maybe it's a possibility to mod the new taskbar and make it better instead of a full rewrite if a full rewrite is even possible given the complexity.

26090 is out with no watermark. Anyone running it with SAB... how is the taskbar looking?

I'm not 100% certain but I think the consensus is Insider builds are not supported. If this is happening in stable I'd be more concerned. Given that the legacy taskbar is likely going to be removed from 24H2 I imagine @Tihiy is busy looking for a stable solution going forward. I think we're pretty lucky it's working at all in Canary right now.

Glad this forum isn't dead and it was just a datacenter outage. Glad to be back. I may go and donate a few bucks to MSFN now....

Eventually it's just gonna be gone I fear. Hopefully by then @Tihiy has a solution. Fortunately we have until the fall before 24H2 is broadly deployed.

Just unlock it and drag it.