microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.73k stars 29.09k forks source link

VS Code keeps asking to Update #205409

Open lilibethocando opened 8 months ago

lilibethocando commented 8 months ago

Type: Bug

VS Code keeps asking to update How can I fix it? I click on "Update now" but the prompt pops up again once it is restarted asking me to update it again. It seems to be stuck on the January update 1.86. How can I fix this without losing all my extensions?

VS Code version: Code 1.85.2 (Universal) (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:32.531Z) OS version: Darwin x64 23.2.0 Modes:

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|2, 3, 3| |Memory (System)|16.00GB (0.31GB free)| |Process Argv|--crash-reporter-id dfe9419c-64a4-42dc-9ef9-dc469e753c58| |Screen Reader|no| |VM|0%|
Extensions (33) Extension|Author (truncated)|Version ---|---|--- path-intellisense|chr|2.8.5 emulate|Die|1.6.0 vscode-html-css|ecm|2.0.9 prettier-vscode|esb|10.1.0 auto-close-tag|for|0.5.15 code-runner|for|0.12.1 copilot|Git|1.162.0 copilot-chat|Git|0.11.1 rainbow-csv|mec|3.11.0 vscode-docker|ms-|1.29.0 vscode-postgresql|ms-|0.3.0 debugpy|ms-|2024.0.0 pylint|ms-|2023.10.1 python|ms-|2024.0.1 vscode-pylance|ms-|2024.2.2 jupyter|ms-|2023.11.1100101639 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.17 vscode-jupyter-cell-tags|ms-|0.1.8 vscode-jupyter-slideshow|ms-|0.1.5 js-debug-nightly|ms-|2024.2.817 live-server|ms-|0.4.13 vsliveshare|ms-|1.0.5905 sqltools|mtx|0.28.1 material-icon-theme|PKi|4.33.0 heroku-command|pko|0.0.8 postman-for-vscode|Pos|0.18.0 sqlite-viewer|qwt|0.3.13 LiveServer|rit|5.7.9 markdown-preview-enhanced|shd|0.8.11 vscode-pets|ton|1.25.1 vscode-icons|vsc|12.7.0 html-css-class-completion|Zig|1.20.0
A/B Experiments ``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vscorecescf:30445987 vscod805cf:30301675 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:30899288 c4g48928:30535728 azure-dev_surveyone:30548225 962ge761:30959799 pythongtdpath:30769146 welcomedialogc:30910334 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 pythontestfixt:30902429 pythonregdiag2:30936856 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 pythontbext0:30879054 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 pydisww2:30959801 3ef8e399:30964150 ```
vscodenpa commented 8 months ago

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

matsui-p commented 7 months ago

possibly related: https://github.com/microsoft/vscode/issues/203903 and https://github.com/microsoft/vscode/issues/202437 (having the same issue on a m1 mac @ 1.85.2)

i-Krypt commented 4 months ago

Anyone still getting this issue on May 2024 (version 1.90) update

hkim-fda commented 4 months ago

Anyone still getting this issue on May 2024 (version 1.90) update

I have got the same issue every time since I installed the VScode on Windows 10. (the current version 1.90.1 on PC) Is this supposedly resolved if I install it at the user level (installation under AppData)?

vijjusri14 commented 1 month ago

I faced the same issue, this is happening when there is a vscode instance running in the background as admin/sudo user and you try to update vscode from non privileged user through update dialog/menu.

This might happen when you try to start the vscode from terminal as admin/sudo user and the vscode is not properly closed and keep running in the background.

I resolved it by killing the vscode instance which was running in the background through task manager/activity monitor and update vscode as non privileged user