vscode: Unsupported OS warning banner will not go away

please have an option to disable it. very annoying

To remove unsupportedGlibcWarning.banner we need to make isUnsupportedGlibc to be false To do it we can replace isUnsupportedGlibc:k.isUnsupportedGlibc with isUnsupportedGlibc:0 in workbench.desktop.main.js

Mac OS command:

sed -i '' 's/:k\.isUnsupportedGlibc/:0/g' \
"/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js"

Please don’t post “+1” comments, as they produce low-value email notifications to everyone watching the issue. Instead, click a reaction button on the original comment:

this sucks.

I would also like an option for disabling the banner. The servers I connect to are managed by my organization, and there is nothing I can do to speedup the deployment of new OSes.

A similar command that can be used in Windows is: navigate to the file: C:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench OR C:\Users\<user>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench than run this command from Powershell

(Get-Content "workbench.desktop.main.js") -replace ':k\.isUnsupportedGlibc', ':0' | Set-Content "workbench.desktop.main.js"

(I recommended to make a backup to the file, just in case…) copy to backup…

Copy-Item "workbench.desktop.main.js" "workbench.desktop.main.js.bak"

this is absurd… it feels passive aggressive.

There’s a simple solution for all of this.

Give us the warning that it is unsupported, but allow us to continue working on legacy boxes indefinitely.

Let us dismiss this ridiculous banner forever.

Don’t fight developers, work with us.

Here’s a monkey patch workaround that I’ve tested on MacOS:

• Open the workbench desktop JS file. Eg, code /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js
• Search for return X.create("vs/workbench/contrib/remote/browser/remoteConnectionHealth",e), and replace it with return null.
• Restart VS Code.
• Feel that relief of not having a completely pointless (and TBH, a little bit petty) banner across the top of your screen.

There are two notable caveats with this fix:

• VS Code will complain when opening a new window that the install is corrupt. You can click the gear icon and hide that warning permanently. (Personally, I find it hilarious that you can permanently hide this substantially more important warning, but not the new unsupported OS banner.)
• The fix will be reset every time VS Code upgrades, but the steps for re-applying the fix should remain the same.

I don’t know what the process for monkey patching on Windows or Linux looks like, hopefully someone more familiar with VS Code on those platforms can weigh in!

I work for Microsoft and going to find those idiots who introduced this breaking change and ugly persistent banner on top of the window. If they don’t remove this banner in the next few days, the heads will roll. They will be fired.

@benibenj, @isidorn I have closed #204944 as this one was already opened for the same issue. 4. As the D-day nears, the message in the status bar could be made prominent (even blinking red) and optionally use some contrast background if there is a need.

No. Nothing should ever blink. Never, seriously!

I guess the ultimate question to ask here is why suddenly without any clear and strong precaution/warning/notice dropped the support for older OS, given the fact that for example centos7 hasn’t been officially EOL yet.

#203375 #203967 Don’t ask that. they will lock this issue too with “Too heated”…

@benibenj, @isidorn I have closed #204944 as this one was already opened for the same issue.

The new status bar at the top has multiple issues and appears to have been punted without much UX reviews,

1. Cannot dismiss and is jarring.
2. Does not gel in with the theme colors. On some light and dark themes, it horribly stands out and causes distraction.
3. On Windows pressing F11, it hampers the full screen mode in which the tabs used to reach the top of the screen. Now it shows an empty menu bar, then this new bar and then the tabs line (occupies extra screen real estate). Essentially, it seems to be blocking the full screen feature towards the top of the screen.

Like I mentioned in #20944, we know we are using old version of VS code, with purpose. Please consider following,

1. Moving this message to the status bar at the bottom (typical layout); the status bar is supposed to be used for such things (fundamental UX UI principle).
2. Not changing the background of the message. Should gel with other icons.
3. For now, just have it show the warning triangle and short message “Unsupported OS” with ALT text of full message on hovering, clicking it should take to the full documentation.
4. As the D-day nears, the message in the status bar could be made prominent (even blinking red) and optionally use some contrast background if there is a need.

Thanks, WinCPP

+1 Need option to remove the banner.

Love the persistent blue banner reminding me of my “unsupported” life choices every time I dare to connect with an OS from the past. Any chance we can get a “Thanks, I get it!” button to dismiss it? Seeking to focus on code, not reminders of my adventurous tech choices. Some of us thrive in the unsupported wilds and prefer our adventures sans banner.

Does the 1.86.2 fix the warning banner?

got 1.87 today and the banner is still there and cannot be disabled…

+1 please add an option to close the banner.

VS Code updated itself, which I didn’t ask for… and now it doesn’t like the underlying OS version which I can’t update. YOUR CONCERNS HAVE BEEN NOTED, now let me disable the banner.

+1 , it is very annoying

+1

Closed by https://github.com/microsoft/vscode/pull/208392

The banner will be dismissible once per minor version.

+1

I guess the ultimate question to ask here is why suddenly without any clear and strong precaution/warning/notice dropped the support for older OS, given the fact that for example centos7 hasn’t been officially EOL yet.

+1 Option to remove it

+1 Option to remove it

+1

There is a workaround, you can make the banner background/message invisible although the banner will still remain. In your vscode settings.json file you can add this:

"workbench.colorCustomizations": {

    "banner.background": "#ffffff00",
    "banner.foreground": "#ffffff00",
    "banner.iconForeground": "#ffffff00"
    
},

You can also use this to change the color of the banner to better match whatever theme you have if you still want a constant reminder of the problem.

By info from @pento, i do the same but for Windows, and it works too like this:

• Open C:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\workbench.desktop.main.js

• Search for return X.create("vs/workbench/contrib/remote/browser/remoteConnectionHealth",e), and replace it with return null;

• Restart VS Code;

• After reboot you will see another bunner, about your version is broken, but you can just press on settings and click Don't show again

Microsoft, this not only for Windows, with every day updates, stop make anything to waste time of everywone!)

+1 please add option to remove the banner

To remove unsupportedGlibcWarning.banner we need to make isUnsupportedGlibc to be false To do it we can replace isUnsupportedGlibc:k.isUnsupportedGlibc with isUnsupportedGlibc:0 in workbench.desktop.main.js

Mac OS command:

sed -i '' 's/:k\.isUnsupportedGlibc/:0/g' \
"/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js"

Thank you, @apivovarov

A similar command that can be used in Linux is

sudo sed -i 's/:k\.isUnsupportedGlibc/:0/g' "/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js"

VSCode is open-source project. BUT… If you build VSCode from source (with your modifications) the application will not have the same functionality as officially distributed VSCode. For example, all Extensions will not be available.

+1 Option to remove it

+1 Option to remove it

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

I work for Microsoft and going to find those idiots who introduced this breaking change and ugly persistent banner on top of the window. If they don’t remove this banner in the next few days, the heads will roll. They will be fired.

Now I don’t care about the issue, I care about the firing

Node.js 18 requires a minimum glibc version of 2.28. Ubuntu 18.04 - 2.27 Amazon Linux 2 - 2.26

@apivovarov Thanks for taking the time to respond. It turned out that the issue was macOs SIP. Temporarily disabling SIP (requires booting into recovery mode) allowed me to change the application file.

Works but VSCode is complaining about that the installation is corrupt. https://code.visualstudio.com/docs/supporting/faq#_installation-appears-to-be-corrupt-unsupported

Click the cog (gear wheel) icon on that notification, and click “Don’t show again”.

How come features this basic are often straight up not implemented…

+1, would be nice to have possibility to remove the banner

+1 Option to remove it

Right click on Visual Studio Code.app in Finder in Applications and select “Get Info” in drop down menu - Sharing & Permissions section (at the bottom) should show <your_user> (Me) | Read & Write

@geertj