Change:
const rerender = () => { this.gettingStartedCategories = this.gettingStartedService.getWalkthroughs(); this.featuredExtensions = this.featuredExtensionService.getExtensions(); <del> this.buildSlideThrottle.queue(async () => await this.buildCategoriesSlide()); </del> <ins> if (this.currentWalkthrough) { const existingSteps = this.currentWalkthrough.steps.map(step => step.id); const newCategory = this.gettingStartedCategories.find(category => this.currentWalkthrough?.id === category.id); if (newCategory) { const newSteps = newCategory.steps.map(step => step.id); if (!equals(newSteps, existingSteps)) { this.buildSlideThrottle.queue(() => this.buildCategoriesSlide()); } } } else { this.buildSlideThrottle.queue(() => this.buildCategoriesSlide()); } </ins> }; this._register(this.extensionManagementService.onDidInstallExtensions(async (result) => {

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?: No <!-- 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.80.1 OS Version: Windows 10 The C++ extension would like to redirect our users to our walkthrough if they pick an option in one of our quick picks: "help me install a compiler". To achieve this, we've been trying to invoke the command with a link to the correct step in the walkthrough similar to how python does it. The problem I'm seeing is that if we run this command before the Welcome page is loaded, it does not navigate to the walkthrough at all. It just displays the Welcome page and the following error appears in the Developer Console: . If we run the command after the Welcome page loads (or just run the command twice in a row), it will work. To work around it, I was going to try to detect whether the Weclome page or my walkthrough loaded after the first command attempt, but it doesn't look like the Welcome page's tab shows up in the list of so I'm not sure how to detect it. The safest thing for now seems to be to run the command twice every time, but it would be nice if it could be fixed to work on the first attempt.
I can't get this to work, even after opening the welcome window first - it only ever opens the generic welcome page for me. I tried with the c++ walkthrough steps and one in jupyter ext Am I doing something wrong?
Fixed by
This still doesn't work properly. The welcome page opens on the correct page, but then immediately switches back to the main welcome page. !

I'm unable to repro Here are my repro steps: a sample extension a command in the sample extension to open a walkthrough coming from an extension using and installed test extension and invoked the above command. Other things to try: Invoke command before opening welcome page and after.
repro's when debugging the extension with the command at least (I didn't try packaging into a visx) a command to the helloworld-sample extension in the and registered during activation install 5 to run, run the command :bug: similar to though it also sort of tries to shift away from the main walkthrough page, then it works correctly the second time !