Change:
private readonly _onDidProgressStep = new Emitter<IResolvedWalkthroughStep>(); readonly onDidProgressStep: Event<IResolvedWalkthroughStep> = this._onDidProgressStep.event; <ins> private readonly _onDidAddBuiltInWalkthrough = new Emitter<void>(); readonly onDidAddBuiltInWalkthrough: Event<void> = this._onDidAddBuiltInWalkthrough.event; </ins> private memento: Memento; private stepProgress: Record<string, StepProgress | undefined>;

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.77.0 OS Version: Xubuntu 22.04.2 Steps to Reproduce: the Welcome page ( -if it doesn't open by default) any suggestions (note, I haven't tested how this looks with suggestions) the unusual welcome page layout with a lot of empty space on the right: ! This is a regression. The previous version had a different layout, with recent files on the right, and everything else on the left. The layout seen on the screenshot was only used when you had active suggestions, which occupied the space on the right.
I can confirm, on vscode 1.77.0 Win10 x64.
Inconvenient design decision, or just a glitch. I can confirm, on vscode 1.77.0 Debian 11.
Timing issue between walkthroughs being compiled and walkthroughs rendering. Currently, Walkthroughs show up if you have an extension installed which contributes a walkthrough. If you don't have an extension which contributes walkthroughs installed, then the built in walkthroughs are also missing -You can test this by switching to a new empty profile and reloading the welcome page.
Related on Stack Overflow:
closing since was merged.
I just installed 1.77.3 and see the following: ! Is it supposed to be like this? I was under the impression that the fix would make the recent listing be in its own column.
I can confirm that layout is still incorrect. <img width="451" alt="image" src="https://user-"
Seems that this is related to a new (?)

section on the welcome page for recommended extensions (which I can't find a way to turn off, will file an issue for that). <img width="1024" alt="CleanShot 2023-04-18 at 08 49 42 src="https://user-"Even after dismissing it, the layout stays the same so I don't think this was fixed: <img width="1024" alt="CleanShot 2023-04-18 at 08 52 42 src="https://user-"
Designers are back in their repertoire, let's give the user a function they don't need (seriously, VSCode starts to slow down a lot if there are too many extensions and they are not optimal), while they drop support for the older but up-to-date versions. How nice, IT every year more and more suffers from garbage.
This should be reopened. The ticket is in the milestone, but as of 1.77.3 it's still not fixed. (And neither in the Insiders.)
Any updates Seems like this is the same on Insiders (1.78) as well, so I am wondering if this is by design or not (cc <img width="1024" alt="CleanShot 2023-05-01 at 08 36 18 src="https://user-"
This was by design so as to not clutter page on addition of the featured extension entry. But given the user input, we can consider a better approach for this. Proposal: Recent list stays on the left side of the welcome page when either walkthroughs/featured extension tile is displayed. Recent item count limited to 5 Recent list moves to the right side of the welcome page when no walkthrough/featured extension tile is displayed. Recent item count is also increased to 10. thoughts?
Sounds good