vscode: Welcome page not loading
Issue Type: Bug
- Attempt to open welcome page
- See error appear saying that a file was not found
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:44:30.902Z) OS version: Darwin x64 19.6.0
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i5-4570R CPU @ 2.70GHz (4 x 2700) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled |
Load (avg) | 3, 5, 5 |
Memory (System) | 16.00GB (2.14GB free) |
Process Argv | –crash-reporter-id 664964bd-d748-4598-b834-0db5f9508abf |
Screen Reader | yes |
VM | 0% |
Extensions (71)
Extension | Author (truncated) | Version |
---|---|---|
better-comments | aar | 2.1.0 |
emoji-log-vscode | ahm | 1.0.0 |
css-snippets | Aji | 1.0.1 |
arepl | alm | 2.0.2 |
sort-imports | ama | 6.2.6 |
electron-snippets | ant | 1.0.3 |
filewatcher | App | 1.0.3 |
vscode-linux-binary-preview | bet | 1.1.2 |
github-markdown-preview | bie | 0.0.2 |
markdown-checkbox | bie | 0.1.3 |
markdown-emoji | bie | 0.1.0 |
markdown-yaml-preamble | bie | 0.0.4 |
npm-intellisense | chr | 1.3.1 |
path-intellisense | chr | 2.3.0 |
codestream | Cod | 11.0.7 |
bracket-pair-colorizer-2 | Coe | 0.2.0 |
vscode-eslint | dba | 2.1.20 |
python-preview | don | 0.0.4 |
python-extension-pack | don | 1.6.0 |
es7-react-js-snippets | dsz | 3.1.1 |
gitlens | eam | 11.4.1 |
vscode-html-css | ecm | 1.10.2 |
vscode-npm-script | eg2 | 0.3.21 |
apacheconf-snippets | eim | 1.3.0 |
prettier-vscode | esb | 6.4.0 |
file-icons | fil | 1.0.29 |
auto-rename-tag | for | 0.1.6 |
vscode-pull-request-github | Git | 0.26.0 |
mdmath | goe | 2.5.1 |
vscode-test-explorer | hbe | 2.20.0 |
output-colorizer | IBM | 0.1.2 |
useful-react-snippets | igo | 3.0.0 |
search-node-modules | jas | 1.3.0 |
react-component | jer | 1.0.4 |
node-module-intellisense | lei | 1.5.0 |
vscode-python-test-adapter | lit | 0.6.8 |
vscode-regexp-preivew | Lul | 1.0.0 |
vscode-github-actions | me- | 3.0.1 |
python-path | mge | 0.0.11 |
pack-apache | mpt | 0.1.1 |
vscode-apache | mrm | 1.2.0 |
vscode-json5 | mrm | 1.0.0 |
python | ms- | 2021.5.842923320 |
vscode-pylance | ms- | 2021.5.3 |
jupyter | ms- | 2021.6.832593372 |
cpptools | ms- | 1.3.1 |
hexeditor | ms- | 1.6.0 |
vsliveshare | ms- | 1.0.4272 |
nextjs-snippets | Pul | 0.0.3 |
qub-xml-vscode | qub | 1.2.8 |
quicktype | qui | 12.0.46 |
new-file-by-type | Rec | 1.0.1 |
vscode-commons | red | 0.0.6 |
vscode-yaml | red | 0.19.2 |
nextjs-vscode-snippets | ret | 0.1.1 |
LiveServer | rit | 5.6.1 |
vscode-open | san | 0.1.0 |
js-jsx-snippets | sky | 10.1.0 |
snippets | tah | 1.2.0 |
markdown-links | tch | 0.8.0 |
vscode-gitmoji-snippets | thi | 3.2.0 |
highlight-matching-tag | vin | 0.10.0 |
vscodeintellicode | Vis | 1.2.14 |
vscode-svg-previewer | vit | 0.7.0 |
vscode-icons | vsc | 11.4.0 |
gitmoji-vscode | Vtr | 1.0.6 |
nodejs-extension-pack | wad | 0.1.9 |
caniuse-query | Wil | 0.0.1 |
vscode-import-cost | wix | 2.15.0 |
JavaScriptSnippets | xab | 1.8.0 |
html-css-class-completion | Zig | 1.20.0 |
(3 theme extensions excluded)
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551cf:30291415
vspre833cf:30267465
pythonptprofiler:30281270
vshan820:30294714
vscoreces:30290705
pythondataviewer:30285071
vscus158cf:30286554
vscgsv2ct:30301613
vscorehovct:30302760
bridgeflight:30302069
vscod805cf:30301675
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 15 (6 by maintainers)
This is exactly what you don’t want. If you delete that setting it should work.
I’ve added the workspace trust and walk through scheme to list of schemes which shouldn’t be overriden.
This is the error, I get on startup:
When I try to open Getting Started screen manually, I get the same error as follows:
And, When I try to open Welcome screen manually, I get the similar error as follows:
I tried to naviage to the mentioned resource and it is missing in the specified path. I guess either, the resource is not inculded in the latest update or the path pointing to this resouce is not right.