How to: Start Minimized, disable auto-update

[Jack Schitt]

Note: As of August 1, 2023 the -vgui option has been disabled.

If you haven't done this prior to then and disabled the auto update process in these instructions you're stuck with the new UI.

The -silent switch and other options still work.

---

METHOD 1:

1. Right-Click on your Steam Client icon in the start menu and select
More > Open File Location.

2. Right-Click on the shortcut in the folder that opens and select Properties.

3. Add a space after the text (after the quotes) in the Target line and paste or type the switches of your choice.

Click apply, then close the properties window.
Exit Steam completely and relaunch to apply the effects.

---

METHOD 2:

Effects Steam everywhere on your PC

1. Press Winkey+R and type regedit

2. Paste this into the Registry Editor's address field:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

3. You should see "Steam" listed in the right pane of Registry Editor.
If you do not have "Steam" listed create it:
Edit > New > String Value and name it Steam (capitol S!)

Double-click on Steam and add a space after the quotes then add the switch(es) of your choice.

Exit Steam completely and relaunch to apply the effects.

---

DISABLE THE AUTO UPDATE PROCESS

1. Go to where your Steam Client is installed to, Winkey+E opens File Explorer.
The Default location is C:\Program FIles (x86)\Steam
NOT where your games are installed to. Where the steam CLIENT is installed to.

2. Open the Steam.cfg file in a text editor. Change both lines from Disabled to Enabled. If you don't have a steam.cfg file create one and paste the following lines in to it.

BootStrapperInhibitAll=Enabled
BootStrapperForceSelfUpdate=Enabled

Exit Steam completely and relaunch to apply the effects.

---

Optional Parameter Switches you can use:

-silent
This forces the Steam Client to start up or open when you click on it in Large Mode minimized to the system tray.

+open steam://open/minigameslist
This option forces the Steam Client to start up in Small Mode.

You can use multiple parameter switches. Separate them with a space:

+open steam://open/minigamelist -silent
This option forces the Steam Client to start up in Small mode, minimized to the system tray.

Full List of Steam Client Command Line Parameters

[Kenpoleon Bonaparte]

Ahh, the good old days, where things look normal, things load quicker, AND everything works again. Thanks again for the instructions, Jack.

[SomeGuy712x]

Originally posted by Jack Schitt:

BootStrapperInhibitAll=Enabled
BootStrapperForceSelfUpdate=Enabled

Huh? I thought I read in other threads that BootStrapperForceSelfUpdate should be "False", not "Enabled". For example, in this thread here:
https://steamcommunity.com/discussions/forum/0/6516193260177025343/
So, did you put the wrong word there by mistake?

[Kenpoleon Bonaparte]

Originally posted by SomeGuy712x:

Originally posted by Jack Schitt:

BootStrapperInhibitAll=Enabled
BootStrapperForceSelfUpdate=Enabled

Huh? I thought I read in other threads that BootStrapperForceSelfUpdate should be "False", not "Enabled". Did you put the wrong word there by mistake?

I did it as he said, and it works fine for me. Another guy, on a different thread, said you don't have to actually disable the auto update though. Just launch from the edited shortcut.

[SomeGuy712x]

Originally posted by Kenpoleon Bonaparte:

Originally posted by SomeGuy712x:

Huh? I thought I read in other threads that BootStrapperForceSelfUpdate should be "False", not "Enabled". Did you put the wrong word there by mistake?

I did it as he said, and it works fine for me.

You managed to quote my comment before I quickly edited it to include that example link. Anyway, if it works just fine for you, then I guess it's okay then.

[Kenpoleon Bonaparte]

Originally posted by SomeGuy712x:

You managed to quote my comment before I quickly edited it to include that example link.

Lol. I hate it when that happens to me.

[Jack Schitt]

Originally posted by SomeGuy712x:

Originally posted by Jack Schitt:

BootStrapperInhibitAll=Enabled
BootStrapperForceSelfUpdate=Enabled

Huh? I thought I read in other threads that BootStrapperForceSelfUpdate should be "False", not "Enabled". For example, in this thread here:
https://steamcommunity.com/discussions/forum/0/6516193260177025343/
So, did you put the wrong word there by mistake?

Not a mistake. I've been running this config file for years.
The default settings for both lines is "Disabled".

"False" might work? If it does work and that's what you want to use, go for it.
I use Enabled/Disabled in mine.

[Kenpoleon Bonaparte]

Originally posted by SomeGuy712x:

You managed to quote my comment before I quickly edited it to include that example link

You must have missed my edit, too. Here it is again. If you're paranoid, you can try it this way.

"Another guy, on a different thread, said you don't have to actually disable the auto update though. Just launch from the edited shortcut."

[Jack Schitt]

Originally posted by Kenpoleon Bonaparte:

Originally posted by SomeGuy712x:

You managed to quote my comment before I quickly edited it to include that example link

You must have missed my edit, too. Here it is again. If you're paranoid, you can try it this way.

"Another guy, on a different thread, said you don't have to actually disable the auto update though. Just launch from the edited shortcut."

I formatted these instructions the way I did trying to make it so everyone can do it. Not everyone uses desktop icons. I included disabling the validation and update checker process to eliminate the possibility those processes throw the new UI at us again. We have the option whether we update or not with them disabled. We don't have a choice if they're enabled,

[Kenpoleon Bonaparte]

Originally posted by Jack Schitt:

I formatted these instructions the way I did trying to make it so everyone can do it. Not everyone uses desktop icons.

Yeah, I saw your post on that... no desktop icons, just a black screen. I'm with you. I only have a few icons, of some documents I use almost every day, cause I don't like my screen being cluttered either. I launch Steam, and other highly-used programs, from my Taskbar. I did it your way and disabled the auto update cause I was afraid if I didn't, then Steam would constantly nag at me on the old UI to do it. With your way, I don't have to worry about Steam nagging.

[Jack Schitt]

The first time I shut down and relaunched after applying the switch I had the new UI disaster torturing me again. I had the update stuff disabled for years. I just turned it back on a few days before this update released. Regret. That stuff's saying disabled now until the client refuses to run.

[Kenpoleon Bonaparte]

Originally posted by Jack Schitt:

That stuff's saying disabled now until the client refuses to run.

I"m leaning that way too.

[MarsTooEpicary]

Tried the -vgui option,Does work but with skin it crashes in like 5-10min interval. Have to suffer through it cause of custom steam skin,Any help?

[Jack Schitt]

Sorry, MarsTooEpicary, I don't have a suggestion for that other than to use the default skin for the old UI. Valve is probably going to disable -vgui when the new UI is stable anyway. Being able to use the old UI is very very likely only temporary. I'll take a look at the skin and see if I can find anything wonky in it if you can share a link to download it from.

[MarsTooEpicary]

Originally posted by Jack Schitt:

Sorry, MarsTooEpicary, I don't have a suggestion for that other than to use the default skin for the old UI. Valve is probably going to disable -vgui when the new UI is stable anyway. Being able to use the old UI is very very likely only temporary. I'll take a look at the skin and see if I can find anything wonky in it if you can share a link to download it from.

Yeah i am currently troubleshooting it(well more like i am trying to find what actually crashes it when i open up something up)

So far only opened the old gui's Music player.Could be the issue

[Jack Schitt]

You may, unfortunately, have to do without the custom skin and use the default skin. Who knows what all the developers did to the old UI files futzing with making the new UI. The crashes might be errors that are in the skin you're trying to use though too.

I hope you can agree using the old UI's default skin is better than trying to tolerate all the things you don't like about the new UI.