Updating via the UI failing in Windows 11

[SirClickALot]

I have the stack running fine in Window 11 but when I try to update using the UI…

I am seeing the following error message…

Error message
Your site cannot be automatically updated until further action is performed.
Failed to run process: The command "<local-location>drupal\vendor\composer/./composer/bin/composer --format=json" failed. Exit Code: 1(General error) Working directory: <local-location>drupal\web Output: ================ Error Output: ================ '<local-location>drupal\vendor\composer/./composer/bin/composer' is not recognized as an internal or external command, operable program or batch file.
Failed to run process: The command "<local-location>drupal\vendor\composer/./composer/bin/composer --format=json" failed. Exit Code: 1(General error) Working directory: <local-location>drupal\web Output: ================ Error Output: ================ '<local-location>drupal\vendor\composer/./composer/bin/composer' is not recognized as an internal or external command, operable program or batch file.

I suspect the /./ perhaps…

[phenaproxima]

My guess: you are probably using a more recent version of the launcher app, but you're using it to run a site you spun up with an older version. :) This is why the launcher is not yet stable -- each new version is allowed to break backwards compatibility. Things will be more stable when the launcher reaches its 1.0.0-beta1 version, but I don't know when that will be.

The easiest way to fix this is to delete the Drupal site (<your documents directory>\drupal) and re-launch the launcher. Start clean.

But if that's not an option, I can try to figure out a sequence of commands you could run to install Composer locally into the existing project.

[SirClickALot]

Actually that is not so in my case; the site was set up fresh with THE CURRENT version of the launcher.

[phenaproxima]

I think I might know what's going on here. There's good news and bad news...

The suspected problem: the launcher is configured to use Composer's PHP binary (this is a good thing)...but Drupal core itself isn't passing it to the PHP interpreter.

The good news: that is fixed in core! I wrote the patch myself.

The bad news: the fix hasn't been released yet. It should be there in the next 11.2.x version -- 11.2.3, which is due to be released in early August.

So, what I would suggest here (and I know this answer sucks) is to wait until 11.2.3 is out -- I'll comment here when it is -- then delete the drupal directory and try relaunching it.

[SirClickALot]

OK, NP, I am happy to wait for then.

[phenaproxima]

Good news here: the patch that would always run Composer through the PHP interpreter is now released in Drupal core as of 11.2.3: https://git.drupalcode.org/project/drupal/-/blob/11.2.3/core/modules/package_manager/src/ComposerRunner.php?ref_type=tags#L42 (that's the line in question).

So, if you're willing -- and thanks for being so patient! -- I'd love to know if this particular problem persists for you (I don't doubt there are other issues, but I'm curious about this specific one) if you delete the entire drupal directory and re-spin up Drupal CMS with the latest version of the launcher.