Steam -no-browser after patch

README.md

Steam -no-browser after patch (Working June 2023)

• Disregard the original steam shortcut and only use the batch scripts below to launch steam

• There is a slight CPU utilization penalty which can be circumvented by suspending the problematic thread

  • See this comment

steam-no-browser.bat:

@echo off
setlocal EnableDelayedExpansion

set "steam_path=C:\Program Files (x86)\Steam"

:: kill steam if is running
tasklist | findstr /i "steam.exe" && taskkill /f /im "steam.exe"

:: rename binary back to .exe as steam requires it to initialize
for %%a in ("cef.win7", "cef.win7x64") do (
    set "bin=!steam_path!\bin\cef\%%~a\steamwebhelper.exee"
    if exist "!bin!" (
        ren "!bin!" "steamwebhelper.exe"
    )
)

:: open steam
start "" "!steam_path!\steam.exe" +open steam://open/minigameslist -vgui

:: only continue if steamwebhelper is running in case steam is updating
:query_steamwebhelper
tasklist | findstr /i "steamwebhelper.exe" || goto :query_steamwebhelper

:: allow a few seconds for steam to initialize/login
timeout /t 5 /nobreak

:: rename binary and kill the process
for %%a in ("cef.win7", "cef.win7x64") do (
    set "bin=!steam_path!\bin\cef\%%~a\steamwebhelper.exe"
    if exist "!bin!" (
        ren "!bin!" "steamwebhelper.exee"
    )
)

taskkill /f /im "steamwebhelper.exe"

steam-normal.bat:

@echo off
setlocal EnableDelayedExpansion

set "steam_path=C:\Program Files (x86)\Steam"

:: kill steam if is running
tasklist | findstr /i "steam.exe" && taskkill /f /im "steam.exe"

:: rename binary back to .exe as steam requires it to initialize
for %%a in ("cef.win7", "cef.win7x64") do (
    set "bin=!steam_path!\bin\cef\%%~a\steamwebhelper.exee"
    if exist "!bin!" (
        ren "!bin!" "steamwebhelper.exe"
    )
)

:: open steam
start "" "!steam_path!\steam.exe"

Thank you!

Also do note that steam.exe will constantly use 1-1.5% of cpu in this "mode", more explanation here https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3710433479207750727/?ctp=16#c3763355849157101044

Small price to pay for 400mb of RAM saved.

Steam chat will not be available as well.

---- Valve!

Since it's the CreateInterace threads running under steam.exe that are stuck in the error loop, you can simply suspend it with process explorer. Note that the UI will be unusable inaccessible until the threads are resumed (including the tray icon)

Normal behavior:

After running the no-browser script:

Suspending the CreateInterface threads:

You can just rename the steamhelpers, then kill the processes off whilst Steam is running, then rename them back. The client doesn't check that they exist or try to run them again (in that client's run time), from my brief testing.

Obviously if you restart, you'll have to repeat the process, but that's a little cleaner than permanently renaming them.

The client certainly calls for the webhelpers after they are renamed meaning that they will run once renamed back to default.
See https://gist.github.com/amitxv/0c454ba09a2feb3dd38f29c333f68c04?permalink_comment_id=4460606#gistcomment-4460606

Unless you can use the chat and games list (small) functionality without all the webhelpers, or in the old gui mode, what is the point of this? There are many other ways to only use the game without steam involved. Not having the helpers doesn't give back the old functionality, it now brings limited functionality.

I have win7x64 and for the first time script worked, but then steam updated and somewhy created another folder /bin/cef/cef.win7, so I just added the same renaming lines for /bin/cef/cef.win7/steamwebhelper.exe and it works in my case too now (from the second time if new session)

You can just rename the steamhelpers, then kill the processes off whilst Steam is running, then rename them back. The client doesn't check that they exist or try to run them again (in that client's run time), from my brief testing.
Obviously if you restart, you'll have to repeat the process, but that's a little cleaner than permanently renaming them.

The client certainly calls for the webhelpers after they are renamed meaning that they will run once renamed back to default. See https://gist.github.com/amitxv/0c454ba09a2feb3dd38f29c333f68c04?permalink_comment_id=4460606#gistcomment-4460606

With Steam running, I literally just renamed the webhelper executables, killed the processes with taskkill /IM steamwebhelper.exe /F, renamed them back:

Perhaps a better image would be:

My Steam client is nothing but empty space, as you can see, there's no webhelpers in the list below it, none further down.
I've prompted my Steam client to try and find the executables by clicking various options that I've not used previously in this session, "community", etc, let the client shrink to the tasktray, and it hasn't relocated the correctly named/located executables.

If you try it yourself and experience a different result, I'd be interested to hear about it though.
One thing to note, I'm doing this manually (and at a very casual pace too), so perhaps the delay is an important factor.

You can just rename the steamhelpers, then kill the processes off whilst Steam is running, then rename them back. The client doesn't check that they exist or try to run them again (in that client's run time), from my brief testing.
Obviously if you restart, you'll have to repeat the process, but that's a little cleaner than permanently renaming them.

The client certainly calls for the webhelpers after they are renamed meaning that they will run once renamed back to default. See https://gist.github.com/amitxv/0c454ba09a2feb3dd38f29c333f68c04?permalink_comment_id=4460606#gistcomment-4460606

With Steam running, I literally just renamed the webhelper executables, killed the processes with taskkill /IM steamwebhelper.exe /F, renamed them back:

Perhaps a better image would be:

My Steam client is nothing but empty space, as you can see, there's no webhelpers in the list below it, none further down. I've prompted my Steam client to try and find the executables by clicking various options that I've not used previously in this session, "community", etc, let the client shrink to the tasktray, and it hasn't relocated the correctly named/located executables.

If you try it yourself and experience a different result, I'd be interested to hear about it though. One thing to note, I'm doing this manually (and at a very casual pace too), so perhaps the delay is an important factor.

Clicking the "steam" menu item launches the webhelpers again on my system after following your method.

Clicking the "steam" menu item launches the webhelpers again on my system after following your method.

That's interesting, what menu item is that exactly?
Nothing I've been clicking starts them up again, at all, my Steam client is still just empty windows, even after all this time, and clicking all the menu items I can see.

Clicking the "steam" menu item launches the webhelpers again on my system after following your method.

That's interesting, what menu item is that exactly? Nothing I've been clicking starts them up again, at all, my Steam client is still just empty windows, even after all this time, and clicking all the menu items I can see.

My steam interface is also empty but the child processes still spawn.

How strange, mine's still dead after 14+ hours, and clicking all the menu items.

Perhaps task manager is failing to show the process tree properly? Can you try process explorer?

Perhaps task manager is failing to show the process tree properly? Can you try process explorer?

Using your default bat:
https://streamable.com/rhswrc

Perhaps task manager is failing to show the process tree properly? Can you try process explorer?

I just hadn't launched a game in all that time.
Now that I've launched a game, the helpers have returned, and my Steam client has returned to normal.

Resource Manager didn't show them either, prior to launching.

Interestingly, repeating the process works just fine, even when the game overlay active, although I had to terminate the instance of the game overlay (which then relaunched with no webhelpers), and it all seems to be fine again.

Relaunched the game, no webhelpers spawned, however the initial GameOverlay executable causes the main steam client to hang, ending the overlay task has it restart and work as expected, minus any web based functions.

Organised by name:

Perhaps task manager is failing to show the process tree properly? Can you try process explorer?

Using your default bat: https://streamable.com/rhswrc

Can you send the full path to the location of steamwebelper.exe?

Can you send the full path to the location of steamwebelper.exe?

E:\Steam\bin\cef\cef.win7x64\steamwebhelper.exe & E:\Steam\bin\cef\cef.win7\steamwebhelper.exe

Can you manually check if they get renamed to .exee as shown below after using the no-browser script? It should not run if it is renamed to anything other than .exe

Oh, that file is being renamed fine, but somehow a dupe was made causing a relaunch.

My bat now looks like this and it does not reopen the process any longer. I can't, however, use the friendslist (which I need), and sort of makes this only useful for offline playing--and I'm pretty sure you can just run taskkill /f /im "steamwebhelper.exe" after you lunch steam to do that, or go in offline mode for it.

REM https://gist.github.com/amitxv/0c454ba09a2feb3dd38f29c333f68c04
REM 
@echo off

set "steam_path=E:\Steam"

:: kill steam if is running
tasklist | findstr /i "steam.exe" && taskkill /f /im "steam.exe"

:: rename binary back to .exe as steam requires it to initialize
if exist "%steam_path%\bin\cef\cef.win7x64\steamwebhelper.exee" (
    ren "%steam_path%\bin\cef\cef.win7x64\steamwebhelper.exee" "steamwebhelper.exe"
)
if exist "%steam_path%\bin\cef\cef.win7\steamwebhelper.exee" (
    ren "%steam_path%\bin\cef\cef.win7\steamwebhelper.exee" "steamwebhelper.exe"
)

:: open steam
start "" "%steam_path%\steam.exe" -login USERNAME PASSWORD +open steam://open/minigameslist

:: only continue if steamwebhelper is running in case steam is updating
:query_steamwebhelper
tasklist | findstr /i "steamwebhelper.exe" || goto :query_steamwebhelper

:: allow a few seconds for steam to initialize/login
timeout /t 5 /nobreak
:: rename binary and kill the process
taskkill /f /im "steamwebhelper.exe"
ren "%steam_path%\bin\cef\cef.win7x64\steamwebhelper.exe" "steamwebhelper.exee"
ren "%steam_path%\bin\cef\cef.win7\steamwebhelper.exe" "steamwebhelper.exee"
taskkill /f /im "steamwebhelper.exe"

Sadly with this script after another update steam.exe now consumes up to 4% of CPU instead of 2% (that CreateInterface thingy). Thanks valve, managed to make it worse.

P.S. At this point I gave up and removed steam from autostart altogether.

I have impression that if you disable steam autorun and just start game itself (steam starts and hides in tray), i've noticed memory usage is lower than before, about 65mb with all webhelpers...

Well that's expected since UI isn't being loaded into memory

@refriedfood

My bat now looks like this and it does not reopen the process any longer. I can't, however, use the friendslist (which I need), and sort of makes this only useful for offline playing--and I'm pretty sure you can just run taskkill /f /im "steamwebhelper.exe" after you lunch steam to do that, or go in offline mode for it.

If you need the friends list to join another player, you can use Steam chat in the web browser on games that can join others (using the 'Join Game' chat dropdown option or by accepting an invite in chat) from out of game. If the game cannot join your friend using launch parameters, this doesn't help.

If you need the friends list to invite someone to your game, use 2022 Steam with -no-browser since you still get the old chat there. That also gets you the old chat in the overlay.

@Luckz How do you get the 2022 steam without it updating every launch?

@Luckz How do you get the 2022 steam without it updating every launch?

https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3710433479207750727/#c3763355849151540150
or my extra notes: https://steamcommunity.com/discussions/forum/0/3758852249527312123/

Then you have to decide if you want a separate non-updating client or to replace your Steam. In the former case, you also have to decide if you want to share the Steam libraries or not. I've had some issues with game update recognition when appinfo.vdf/packageinfo.vdf were not shared between the two installs – or at least that's my guess.

@Luckz How do you get the 2022 steam without it updating every launch?

https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3710433479207750727/#c3763355849151540150 or my extra notes: https://steamcommunity.com/discussions/forum/0/3758852249527312123/

Then you have to decide if you want a separate non-updating client or to replace your Steam. In the former case, you also have to decide if you want to share the Steam libraries or not. I've had some issues with game update recognition when appinfo.vdf/packageinfo.vdf were not shared between the two installs – or at least that's my guess.

Oh my sweet jesus, you are gorgeous.

I'll keep my fingers crossed that they don't figure out some way to enforce the latest steam.

I thought of sharing my own project: https://github.com/Aetopia/NoSteamWebHelper as the name suggests but takes a different approach to disabling the webhelper for the 2023 Steam Client.

Rather than being a script, its a compiled C program that listens for window showing/hiding events of the Steam window itself, once any those of events are invoked then the webhelper files are renamed, any webhelper processes are killed and then the program exits. Also any command line arguments passed to the program are passed to steam when it launches.

Rather than simply making it inaccessible to Steam and causing the CreateInterface thread to error, could replacing it with some kind of stub executable that just returns success and immediately exits be a possible solution?

Rather than simply making it inaccessible to Steam and causing the CreateInterface thread to error, could replacing it with some kind of stub executable that just returns success and immediately exits be a possible solution?

Steam will continuously attempt to run the WebHelper incase if terminates, resulting in CPU Cycle spikes, so this method/solution is out of question.

Rather than simply making it inaccessible to Steam and causing the CreateInterface thread to error, could replacing it with some kind of stub executable that just returns success and immediately exits be a possible solution?

Steam will continuously attempt to run the WebHelper incase if terminates, resulting in CPU Cycle spikes, so this method/solution is out of question.

Opposite, then? Executable that just pauses/suspends but stays in the process list? Apologies if my suggestions are naive, if I'm being a bother I'll stop.

Rather than simply making it inaccessible to Steam and causing the CreateInterface thread to error, could replacing it with some kind of stub executable that just returns success and immediately exits be a possible solution?

Steam will continuously attempt to run the WebHelper incase if terminates, resulting in CPU Cycle spikes, so this method/solution is out of question.

Opposite, then? Executable that just pauses/suspends but stays in the process list? Apologies if my suggestions are naive, if I'm being a bother I'll stop.

Tried that also, that will cause Steam's window to freeze entirely.

i switched to playnite after steam removed no-browser command

i switched to playnite after steam removed no-browser command

Does it launch a minimal steam instance?

its a different launcher entirely ..... its open source in github ... if u dont want to use tht try switch to epic games now epic has almost all games from steam and u can even close epic launcher completely after launching a game and installing webhelper is completely optional

To get it work with last UI update:

Replace this line:

start "" "!steam_path!\steam.exe" +open steam://open/minigameslist

By

start "" "!steam_path!\steam.exe" -vgui +open steam://open/minigameslist

Can confirm this works, will update the script. Thanks

With the last update, it looks like that some games require the browser to start (elite dangerous for example).
I increased the killing delay to 60 secs to start theses games before the process gets killed.

Hopefully, most games can start without the browser.

did everything as written. does not work

Just use launch options -cef-single-process -skipinitialbootstrap -quicklogin -oldtraymenu -silent
Then switch view to Small Mode, turn most Interface settings off, Library small / low bw / low perf / disable community content
Everything will work when needed, no flooding crashes behind the scene, no clashing with os av & browser, 3 processes (steam + webhelper + crashpad), ~300MB ram usage (over long usage it can raise to 1GB and not release it - but can restart steam really quick)
steamwebhelper no longer lags games, no longer hogs cpu & ram, no longer posses glaring security risks, so postpone fighting it for when it does any of that.
And this coming from the original steamwebhelper_killer author from ~8 years ago.

I think i prefer running the script.

It's basically the same once installed, except it runs smoother with 60MB of ram, without growing over time.

There is no reason to use something that eats 4x more ram at best and require frequent restarts.

Just use launch options -cef-single-process -skipinitialbootstrap -quicklogin -oldtraymenu -silent Then switch view to Small Mode, turn most Interface settings off, Library small / low bw / low perf / disable community content Everything will work when needed, no flooding crashes behind the scene, no clashing with os av & browser, 3 processes (steam + webhelper + crashpad), ~300MB ram usage (over long usage it can raise to 1GB and not release it - but can restart steam really quick) steamwebhelper no longer lags games, no longer hogs cpu & ram, no longer posses glaring security risks, so postpone fighting it for when it does any of that. And this coming from the original steamwebhelper_killer author from ~8 years ago.

This is not as effective as the method in the gist. The latter evidently consumes less CPU and memory. I also made sure to wait until the values stabalize before recording the results.

The method you suggested:

My method:

-cef-single-process -skipinitialbootstrap -quicklogin -oldtraymenu -silent is still 2GB of RAM on a really big account and additionally loses the open chats.
Then again, the web helper killing method incurs that much-discussed CPU penalty, doesn't it?

And while at it, launching "2022 Steam" with CEF nowadays suffers from bugs related to Steam Friends updates. I suppose in -no-browser that's not an issue.

You are correct, but the CreateInterface thread can be suspended to circumvent the CPU usage penalty

alternative steamwebhelper_min.bat

What it does:

• creates a Steam_min shortcut on desktop with a few launch options
• hijacks steamwebhelper via IFEO and inserts couple CEF launch options that steam does not expose
  mainly --single-process and --enable-low-end-device-mode but doing it this way it works when steam asks for self-restarting to apply an update
• default preset uses -vgui mode i.e. the old interface, but there's an OVERLAY variable at the top of the script to easily switch to the new interface (if you want to use the improved in-game overlay at the expanse of extra ram usage)
• default preset uses --disable-background-networking and it generally helps, but you can fully disable networking for steamwebhelper (via fake localhost proxy) with the OFFLINE variable at the top of the script (then Friends, Store won't launch)
• code can be copy-pasted in a batch script but also works in ps1 and directly in powershell console, each time you run it it will install or remove itself

-no-browser will surely be missed, there's no easy way to replicate it now without multiple downsides to killing and physically deleting the files on disk or forcefully suspending threads & etc.
My alternative is a bit more graceful at it, and managed to reduce idle ram usage to under 100MB, but it's certainly not a killer.

I tried 30+ times to install everything as written here. does not work.
don't try, nothing will help here

I tried 30+ times to install everything as written here. does not work. don't try, nothing will help here

What are you talking about? I've been using @Luckz method for months now and it works fine.

I tried 30+ times to install everything as written here. does not work. don't try, nothing will help here

Useless statement:

It dont work guys

Seeking help:

I did X but it happen Y with Z error, what do?

guys, I did absolutely everything according to the guides, it just doesn't work, no matter how hard I try to repeat the same steps 100 times

guys, I did absolutely everything according to the guides, it just doesn't work, no matter how hard I try to repeat the same steps 100 times

repeat the same steps expecting different result for 💯
maybe try different steps then? like the ones I've posted above (it's stupidly simple, just paste code in a powershell window and press enter)
and if it fails, maybe give actual info, starting with the path where you have Steam installed (probably your main issue if it's localized) and ending with output from scripts if any

I did absolutely everything according to the guides

There is multiple advices and code snippets in this conversation. What steps did you follow exactly?
You mean, you have pasted the 2 snippets in the top of this gist to 2 separate .bat files, then ran the one which contains the taskkill command?

@Glastis Very unrelated, but how did you get a dark mode for the Task Manager?

Theme tool: https://github.com/namazso/SecureUxTheme
Theme I'm using: https://www.deviantart.com/kdr3w/art/Dev-825722799

after today update this method is not working anymore for me

start "" "!steam_path!\steam.exe" -vgui +open steam://open/minigameslist

Latest update seems to have broken this specifically, not sure about others.

start "" "!steam_path!\steam.exe" -vgui +open steam://open/minigameslist

Latest update seems to have broken this specifically, not sure about others.

They removed the VGUI entirely.

anyone has fix ?

you can only setup an older version of steam and use that without updating - be warned that long term it will become exploitable

my alternative steamwebhelper_min.bat script from above won't revert the ui, but will limit the cpu & ram usage (and it works for old client too)

isnt there something like legendary alternate client for steam ?

guys, seriously @Luckz's comment. I've been doing that for a long ass time with no interruptions, and thank fucking god for it. Who needs flare? I just my custom message sound and minimal game's list. Using that method, even logging in with all the stupid flash to remove games doesn't auto update. Do it and be marry.

To be honest, I don’t understand who downloads games on a poppy beech. It was only when I bought a poppy that I decided to check if it would run games? I decided to download steam games for mac, since there are official games and without viruses. Yes, many games will show themselves well on a MacBook, but it was not created for this. To me, this looks like violence against a laptop.

alternative steamwebhelper_min.bat

What it does:

• creates a Steam_min shortcut on desktop with a few launch options
• hijacks steamwebhelper via IFEO and inserts couple CEF launch options that steam does not expose
  mainly --single-process and --enable-low-end-device-mode but doing it this way it works when steam asks for self-restarting to apply an update
• default preset uses -vgui mode i.e. the old interface, but there's an OVERLAY variable at the top of the script to easily switch to the new interface (if you want to use the improved in-game overlay at the expanse of extra ram usage)
• default preset uses --disable-background-networking and it generally helps, but you can fully disable networking for steamwebhelper (via fake localhost proxy) with the OFFLINE variable at the top of the script (then Friends, Store won't launch)
• code can be copy-pasted in a batch script but also works in ps1 and directly in powershell console, each time you run it it will install or remove itself

-no-browser will surely be missed, there's no easy way to replicate it now without multiple downsides to killing and physically deleting the files on disk or forcefully suspending threads & etc. My alternative is a bit more graceful at it, and managed to reduce idle ram usage to under 100MB, but it's certainly not a killer.

Your script breaks steam. Steam Client WebHelper now consumes 100 MB less memory. But when you start steam normally, the program windows are black. When I reinstalled steam, it stopped working at all. Luckily I had a restore point.

@sandr1x, the script has built-in undo - just had to run it again

@amitxv So, I just run the no browser bat and then run steam exe?

@refriedfood what was @Luckz's comment? could you please share your current working method?

Guys original "steam-no-browser.bat" still works, you just have to increase timeout /t 5 /nobreak to something like timeout /t 30 /nobreak

With the current 5 seconds steamwebhelper process gets killed and renamed too quickly and you get the "steamwebhelper is not responding" error. Increasing timeout will allow steam to properly initialize/login and you have a few seconds left to launch the game you want to play. After you're done playing and want to launch different game, you will have to kill steam.exe process(or right click tray icon and wait for error to appear, then select close steam) and launch it again with steam-no-browser.bat and start your game.

You don't even have to run "steam-normal.bat" anymore, as steam automatically restores steamwebhelper.exe on each launch if it detects that's missing(renamed).

If it worked at first and doesnt now, goto directory Steam\bin\cef and delete steamwebhelper.exee from both cef.win7 and cef.win7x64 folder and try again

Thanks to distino and Satyam838 for sharing this information, it actually works

Guys original "steam-no-browser.bat" still works, you just have to increase timeout /t 5 /nobreak to something like timeout /t 30 /nobreak

With the current 5 seconds steamwebhelper process gets killed and renamed too quickly and you get the "steamwebhelper is not responding" error. Increasing timeout will allow steam to properly initialize/login and you have a few seconds left to launch the game you want to play. After you're done playing and want to launch different game, you will have to kill steam.exe process(or right click tray icon and wait for error to appear, then select close steam) and launch it again with steam-no-browser.bat and start your game.

You don't even have to run "steam-normal.bat" anymore, as steam automatically restores steamwebhelper.exe on each launch if it detects that's missing(renamed).

If it worked at first and doesnt now, goto directory Steam\bin\cef and delete steamwebhelper.exee from both cef.win7 and cef.win7x64 folder and try again

https://youtu.be/mFGs484Y620?si=owvxYWpshJ6TRMuc
check this video guys. you get some progress

i made a edit to fix some little things & added code to detect if steam is installed

steam-no-browser.bat:

@echo off
setlocal EnableDelayedExpansion

title Steam No Browser

:: Check if steam.exe exists, if it doesn't in the specific route there will be an error
if exist "%SystemDrive%\Program Files (x86)\Steam\steam.exe" (
	set "steam_path=%SystemDrive%\Program Files (x86)\Steam"
    goto :StartScript
) else (
    goto :Error
)

:Error
cls

echo ========================================
echo "Steam.exe" wasn't detected, please edit
echo The script to solve it
echo ========================================
echo.

pause
exit

:StartScript
cls

:: kill steam if is running
tasklist | findstr /i "steam.exe" && taskkill /f /im "steam.exe"

:: rename binary back to .exe as steam requires it to initialize
for %%a in ("cef.win7", "cef.win7x64") do (
    set "bin=!steam_path!\bin\cef\%%~a\steamwebhelper.exee"
    if exist "!bin!" (
        ren "!bin!" "steamwebhelper.exe"
    )
)

:: open steam
start "" "!steam_path!\steam.exe" --disable-background-networking --enable-low-end-device-mode --single-process -cef-single-process -skipinitialbootstrap -quicklogin -oldtraymenu -silent

:: only continue if steamwebhelper is running in case steam is updating
:query_steamwebhelper
tasklist | findstr /i "steamwebhelper.exe" || goto :query_steamwebhelper

:: allow a few seconds for steam to initialize/login
timeout /t 15 /nobreak

:: rename binary and kill the process
for %%a in ("cef.win7", "cef.win7x64") do (
    set "bin=!steam_path!\bin\cef\%%~a\steamwebhelper.exe"
    if exist "!bin!" (
        ren "!bin!" "steamwebhelper.exee"
    )
)

:kill_process
taskkill /f /im "steamwebhelper.exe"
timeout /t 1 /nobreak
taskkill /f /im "steamwebhelper.exe"
timeout /t 1 /nobreak
taskkill /f /im "steamwebhelper.exe"
timeout /t 1 /nobreak

@sandr1x, the script has built-in undo - just had to run it again

I'm back at it again. Your script works well. It reduced the RAM consumption by 2 times ( default 1064 vs script 686 ), but I don’t need it anymore) I just bought more RAM

@OptiJuegos i made a edit to fix some little things & added code to detect if steam is installed

renames the .exe, errors out and crashes without renaming it back :|

@improvised-explosive-device try this new ver: https://cdn.discordapp.com/attachments/1069748073955348550/1159234052356849794/Steam_No_Browser.bat

@improvised-explosive-device try this new ver: https://cdn.discordapp.com/attachments/1069748073955348550/1159234052356849794/Steam_No_Browser.bat

Where is this from? Also, why does it open CS2:

:: open steam
start "" "!steam_path!\steam.exe" steam://rungameid/730 --disable-background-networking --enable-low-end-device-mode --single-process -cef-single-process -skipinitialbootstrap -quicklogin -oldtraymenu -silent

steam://rungameid/730

It has that in the command ^.

Opening CS 2, so just remove it to prevent it from opening.