StartIsBack++

George King

George King

Active Member
Messages
440
Reaction score
186
StartIsBack++​
promo1-2x.jpg


Download
Code: 
https://www.startisback.com/#download-tab

Switches
Code: 
/silent - Perform silent install for current user
/elevated - Install for all users

Example
Code: 
StartIsBack++.exe /elevated /silent
 
Last edited:
George King said:
StartIsBack++​
promo1-2x.jpg


Download
Code: 
https://www.startisback.com/#download-tab

Switches
Code: 
/silent - Perform silent install for current user
/elevated - Install for all users

Example
Code: 
StartIsBack++.exe /silent /elevated
Click to expand...
Evening I integrated startisback on a windows 11 iso as shown in the example (StartIsBack++.exe /silent /elevated) but it does not work, installing the modified iso startisback does not install automatically. Suggestions are accepted. Thank you
 
garlin said:
StartAllBack is the W11 version. Try that one.
Click to expand...
thanks for the answer but the problem is not the startisback file, I use the file for windows 11. the problem is that once inserted in the iso with the post-setup procedure, this does not install automatically I hope I have explained thanks
 
From a CMD shell, "/silent /elevated" results in a StartAllBack Welcome screen. Silent means all windows should close by themselves.
This means it can't work in Post-setup until the author fixes /silent.
 
That's the same problem I had in testing. /elevated /silent from CMD creates new bugs on the desktop (changing to all white on white), before you log out. My impression is to wait until the final product. Right now it's a RC (release candidate).
 
Feel free to report it to creator on official forum. I havent tried it on Windows 11 yet
 
Someone asked the same question again, here's my solution.
TLDR - StartAllBack has two serious bugs:

1. StartAllBack /elevate cannot be run by a privileged user, the program will turn your desktop a solid white color and opens exception errors when your system is restarted. This is a problem because Post-Setup executes as SYSTEM.

2. StartAllBack automatically opens a configuration panel without asking.

Solution is move it from System - Execution to User - Execution. Because you're not privileged, both /elevate /silent and the automatic pop-up panel work as designed.
 
garlin said:
Someone asked the same question again, here's my solution.
TLDR - StartAllBack has two serious bugs:

1. StartAllBack /elevate cannot be run by a privileged user, the program will turn your desktop a solid white color and opens exception errors when your system is restarted. This is a problem because Post-Setup executes as SYSTEM.

2. StartAllBack automatically opens a configuration panel without asking.

Solution is move it from System - Execution to User - Execution. Because you're not privileged, both /elevate /silent and the automatic pop-up panel work as designed.
Click to expand...
Yes It is installing by your method but the initial setup screen ("we are preparing your desktop") is taking too long to finish and enter into actual desktop.
 
You're running it from (Before logon), which is the new name for (System - Execution). Move SAB to (After logon).

For reference, I checked out Chocolatey's install script and asheroto uses AutoHotKey to send a button click to bypass the popup window.
 
garlin said:
You're running it from (Before logon), which is the new name for (System - Execution). Move SAB to (After logon).

For reference, I checked out Chocolatey's install script and asheroto uses AutoHotKey to send a button click to bypass the popup window.
Click to expand...
I am using a old version of NtLite. There are two tabs given for the post setup -> 1. Machine - Execution Queue and 2. User - Execution Queue. First I added the startisback++.exe in the "Machine - Execution Queue" tab at that time the installation didn't happen (I couldn't see it after first logon) then I tried with "User - Execution Queue" and I could see it after first logon (but the initial logon takes too much time to finish, around 10minutes for a single program). I am new to this forum and also exploring NtLite for only a week now (also tried it two years ago but then I was not too serious and didn't have enough time to explore) so I am a bit of noob for technical terms like "SAB". Please expalin what "SAB" is.
 
Last edited:
SAB is what StartAllBack users call the program. I've covered in other threads how StartAllBack is problematic for Post-Setup.

When run from Machine, it doesn't like that it's running under SYSTEM rights. There's some self-elevation code that can't handle this scenario.
When run from User, it's better behaved but does an annoying post-install popup.

Bottom line - if StartAllBack's developer really wanted to make it correctly install in unattended mode, he could have done so. The fact that it's a headache reflects on his (poor) design choices or aesthetics.
 
garlin said:
SAB is what StartAllBack users call the program. I've covered in other threads how StartAllBack is problematic for Post-Setup.

When run from Machine, it doesn't like that it's running under SYSTEM rights. There's some self-elevation code that can't handle this scenario.
When run from User, it's better behaved but does an annoying post-install popup.

Bottom line - if StartAllBack's developer really wanted to make it correctly install in unattended mode, he could have done so. The fact that it's a headache reflects on his (poor) design choices or aesthetics.
Click to expand...
ok now i get it. so the problem is with the actual binary the way it's coded.
 
You must log in or register to reply here.
Back
Top