StartAllBack

Wolfzz · Apr 1, 2024

StartAllBack 3.7.8.4900

Fixed navbar not present with 7 & 10 Explorer styles on 22635.3420+

Not Sure what else has been fixed

https://startisback.sfo3.cdn.digitaloceanspaces.com/StartAllBack_3.7.8_setup.exe

Mikaelo · Apr 2, 2024

Wolfzz said:
StartAllBack 3.7.8.4900

Fixed navbar not present with 7 & 10 Explorer styles on 22635.3420+

Not Sure what else has been fixed

https://startisback.sfo3.cdn.digitaloceanspaces.com/StartAllBack_3.7.8_setup.exe

StartAllBack 3.7.8.4901
same link

Try3 · Apr 4, 2024

See

Microsoft is blocking Windows 11 build upgrades on systems with StartAllBack

https://www.neowin.net/news/microsoft-is-blocking-windows-11-build-upgrades-on-systems-with-startallback/

www.elevenforum.com

Denis

Lamberto Vitali · Apr 5, 2024

Try3 said:
See

Microsoft is blocking Windows 11 build upgrades on systems with StartAllBack

https://www.neowin.net/news/microsoft-is-blocking-windows-11-build-upgrades-on-systems-with-startallback/

www.elevenforum.com

Denis

Startallback should sue MS and make millions. Wanna play silly legal games eh?

NormanF · Apr 5, 2024

Try3 said:
See

Microsoft is blocking Windows 11 build upgrades on systems with StartAllBack

https://www.neowin.net/news/microsoft-is-blocking-windows-11-build-upgrades-on-systems-with-startallback/

www.elevenforum.com

Denis

Workaround is to uninstall StartAllBack, upgrade Windows. Reinstall the SAB executable with a different name.

Until there's a fix issued.

Lamberto Vitali · Apr 5, 2024

I assume the update has been blocked because it contains more badly written fluffy MS nonsense in the display which doesn't play nicely with startallback, so we don't want it anyway.

I've finally discovered what was messing up my 3rd party wallpaper changer. Whenever my wallpaper was changed automatically, windows refreshed every single part of every single window about 30 times each, during which time the mouse could hardly move. The problem was MS's accent colours.

antspants · Apr 5, 2024

Lamberto Vitali said:
Startallback should sue MS and make millions. Wanna play silly legal games eh?

On what grounds should they sue Microsoft?

Lamberto Vitali · Apr 6, 2024

Because MS are deliberately blocking their profits. Remember the "fake ink" manufacturers suing the printer manufacturers? Printer manufacturers were actually designing printers so they would not allow the use of "fake" ink. Notice how they all now let you press ok to continue?

antspants · Apr 6, 2024

This is Y2K all over again!!!

Lamberto Vitali said:
Because MS are deliberately blocking their profits. Remember the "fake ink" manufacturers suing the printer manufacturers? Printer manufacturers were actually designing printers so they would not allow the use of "fake" ink. Notice how they all now let you press ok to continue?

Well then, you should consult them on how to proceed with suing Microsoft.
It wouldn’t pass the pre trial hearing. It’s just temporary for Gods sake, and there is a bypass which is simply renaming the installer. 5 seconds effort.

This reminds me of the Y2k.

pietcorus2 · Apr 6, 2024

Wonder if just disabling SAB , untill the upgrade/updates are finished, will be enough..............

cereberus · Apr 6, 2024

Lamberto Vitali said:
Because MS are deliberately blocking their profits. Remember the "fake ink" manufacturers suing the printer manufacturers? Printer manufacturers were actually designing printers so they would not allow the use of "fake" ink. Notice how they all now let you press ok to continue?

What a silly argument. Answer this question then.

Suppose MS did not block an app over who they had no control, and users had serious issues, those users could then sue MS for loss of production, quoting negligence as MS did not tell them an using an (actually) rather unecessary app was going to give problems.

MS would win hands down in a court of law saying they were protecting their users and that that they have no obligation to ensure 3rd party apps are compatible.

MS have done the right thing - end of story.

Lamberto Vitali · Apr 6, 2024

cereberus said:
What a silly argument. Answer this question then.

Suppose MS did not block an app over who they had no control, and users had serious issues, those users could then sue MS for loss of production, quoting negligence as MS did not tell them an using an (actually) rather unecessary app was going to give problems.

MS would win hands down in a court of law saying they were protecting their users and that that they have no obligation to ensure 3rd party apps are compatible.

MS have done the right thing - end of story.

It's not a silly argument, it's an analogy of something with precisely the same thing happening. One set of companies blocking the profits of another set by abuse of power.

If the changes MS make cause problems, it's due to their own buggy crap as per usual. And they wouldn't be responsible if startallback became incompatible. That sort of thing happens all the time.

Why are you standing up for these utter clowns?

antspants · Apr 6, 2024

Lamberto Vitali said:
Why are you standing up for these utter clowns?

Why are you using Windows?

Lamberto Vitali · Apr 6, 2024

antspants said:
Why are you using Windows?

Because it's a better OS than Linux and Mac. But I got it free with that big giveaway.

antspants · Apr 6, 2024

It comes across like you’re throwing a tantrum about a non-event. In fact you’re throwing out more complaints than the maker of SAB. Didn’t they calmly come out and say “rename the exe”? They didn’t come out saying “Don’t you realise who we are?” “Weez gunna sue youz gize!” like a Karen who’s been refused a drink at a bar for being sloshed.

Edwin · Apr 6, 2024

I have a reasonable suspicion MS targeted SAB and EP because of their high exposure lately!
And, most likely, many portions aren't running as Trusted Installer!
Take, for instance, Stardock products, they modify a lot of stuff, but it's kosher.

antspants · Apr 6, 2024

Edwin said:
I have a reasonable suspicion MS targeted SAB and EP because of their high exposure lately!
And, most likely, many portions aren't running as Trusted Installer!
Take, for instance, Stardock products, they modify a lot of stuff, but it's kosher.

Maybe Stardock are doing it properly, who knows. I doubt that Microsoft would feel threatened by SAB

Lamberto Vitali · Apr 6, 2024

antspants said:
It comes across like you’re throwing a tantrum about a non-event. In fact you’re throwing out more complaints than the maker of SAB. Didn’t they calmly come out and say “rename the exe”? They didn’t come out saying “Don’t you realise who we are?” “Weez gunna sue youz gize!” like a Karen who’s been refused a drink at a bar for being sloshed.

How many users do you think read these forums and would know to rename it? Most folk install something and expect it to work.

Lamberto Vitali · Apr 6, 2024

Edwin said:
I have a reasonable suspicion MS targeted SAB and EP because of their high exposure lately!
And, most likely, many portions aren't running as Trusted Installer!
Take, for instance, Stardock products, they modify a lot of stuff, but it's kosher.

What MS should be doing is realising so many people are rejecting their screwed up interface, and working to make the next version more reasonable and personalisable. Then startallback wouldn't be required.

antspants · Apr 6, 2024

Aparrently:
StartAllBack uses undocumented or deprecated interfaces that are undergoing change as Microsoft refactors the shell experience in Windows 11

This should not affect Start11 because it is mostly using public, documented APIs and services.