You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, interesting. This is going to need setting up and testing, which may take some time for me to get to.
I suspect that OpenSSH isn't running in a native Windows shell (cmd/PowerShell) on the remote system - though I could be wrong - and whatever shell it's using doesn't support app execution aliases (e.g. Cygwin didn't support it until a couple years ago, and still has bugs, and most Bash shells for Windows are based on Cygwin's so they have the same bugs).
The easiest workaround should be to use the MSI installer for this case. But there may be something else going on, since I don't actually know how OpenSSH works.
did you choos the Install Python for 'all users' during installation , also you can also attempt to call the actual executable directly if you can locate its installation path in C:\Program Files\WindowsApps, though this is difficult due to permissions
I uninstalled the install manager from that server and went back to the old installers.
If I recall correctly, I think the issue has something to do with the mechanism requiring a graphical environment. I noticed a window being created briefly when running python through the install manager. That seemed to happen even when I ran python over SSH.
My presumption is that without the graphical environment it just doesn't operate properly (note if you are logged in to the graphical environment this DOES/did work). I don't know how fixable that is.
I'm not much of a Windows guy; this was largely a courtesy bug report. I unfortunately don't have time currently to try again and troubleshoot.
Okay, thanks for the notification. If I get a chance to set up a repro environment, I'll have a look, but if anyone else has one and has the time to try a few things, that'd be really helpful too.
Ran into this trying to use Python install manager for a Jenkins build agent (running Windows Server 2025). In this use case, Jenkins runs a script that calls python via SSH which subsequently fails.
Need to revert to MSI installer for now...
I can reproduce the issue and run some tests if you want.
@wrightsg That would be really helpful. I think the main things I'd like to confirm are:
how was the install manager installed?
does it make a difference to install it with Add-AppxProvisionedPackage -Online -PackagePath python-manager-<version>.msix (and possibly reconnecting/rebooting after, though it shouldn't be necessary)
assuming you set it up interactively and add the global commands directory to PATH, do those commands work? (typically %LocalAppData%\Python\bin, but you'll have to have installed a version first)
Tried reproducing on a different Windows 11 machine as I currently cannot remove the MSI installed python version from the Windows Server 2025 machine - it seems to be working on this setup.
Installed from the MISX downloaded from python.org
Welcome to the Python installation manager configuration helper.
********************************************************************************
The global shortcuts directory is not configured.
Configuring this enables commands like python3.14.exe to run from your
terminal, but is not needed for the python or py commands (for example, py
-V:3.14).
We can add the directory (C:\Users\swright\AppData\Local\Python\bin) to PATH
now, but you will need to restart your terminal to use it. The entry will be
removed if you run py uninstall --purge, or else you can remove it manually when
uninstalling Python.
Add commands directory to your PATH now? [y/N] y
PATH has been updated, and will take effect after opening a new terminal.
********************************************************************************
You do not have the latest Python runtime.
Install the current latest version of CPython? If not, you can use 'py install
default' later to install.
Install CPython now? [Y/n] y
Python install manager was successfully updated to 26.0.
This update adds global shortcuts for installed scripts such as pip.exe.
Use py install --refresh to update all shortcuts.
This will be needed after installing new scripts, as it is not run automatically.
********************************************************************************
Installing Python 3.14.3.
Extracting: ...................................................................✅
To see all available commands, run 'py help'
********************************************************************************
********************************************************************************
Configuration checks completed.
To run these checks again, launch Python install manager from your Start menu,
or py install --configure from the terminal.
********************************************************************************
Usage:
py <regular Python options>
Launch the default runtime with specified options. This
is the equivalent of the python command.
py -V:<TAG> Launch runtime identified by <TAG>, which should
include the company name if not PythonCore. Regular
Python options may follow this option.
py -3<VERSION> Equivalent to -V:PythonCore\3<VERSION>. The version
must begin with the digit 3, platform overrides are
permitted, and regular Python options may follow. py -3
is the equivalent of the python3 command.
py exec <any of the above>
Equivalent to any of the above launch options, and the
requested runtime will be installed if needed.
py help [<CMD>] Show help for Python installation manager commands
py install <TAG> Download new Python runtimes, or pass --update to
update existing installs.
py list [<FILTER>] Show installed Python runtimes, optionally filtering by
<FILTER>.
py uninstall <TAG> Remove one or more runtimes from your machine. Pass
--purge to clean up all runtimes and cached files.
Find additional information at https://docs.python.org/dev/using/windows.
View online help? [y/N]
Then logging in via SSH
Microsoft Windows [Version 10.0.22621.4317]
(c) Microsoft Corporation. All rights reserved.
swright@xxx C:\Users\swright>python --version
Python 3.14.3
Will try reproducing on the Windows Server 2025 machine again once it is not being used.
So I went back to the Windows Server 2025 setup, uninstalled the "Python Launcher" (from the Python 3.12 MSI installer) and reinstalled the Python Install Manager, again using the MISX installer from python.org.
When logged in via remote desktop, I can do the following:
Microsoft Windows [Version 10.0.26100.32522]
(c) Microsoft Corporation. All rights reserved.
C:\Users\jenkins>python --version
Python 3.14.3
C:\Users\jenkins>SET PYTHON_MANAGER_DEFAULT=3.12
C:\Users\jenkins>python --version
Python 3.12.10
C:\Users\jenkins>
Something I noticed is that everytime I run python from the command line (cmd) the Windows "App-Installer" window will briefly pop-up before the command is executed (as shown here: https://www.youtube.com/watch?v=Aqlwk3py5s8)
When logged in via SSH:
Microsoft Windows [Version 10.0.26100.32522]
(c) Microsoft Corporation. All rights reserved.
jenkins@VM-MT-WINDOWS C:\Users\jenkins>python --version
The system cannot execute the specified program.
Furthermore, if I log in via remote desktop, keep the session open and then also log in via SSH, it suddenly works
Microsoft Windows [Version 10.0.26100.32522]
(c) Microsoft Corporation. All rights reserved.
jenkins@VM-MT-WINDOWS C:\Users\jenkins>python --version
Python 3.14.3
Regarding using Add-AppxProvisionedPackage, how do I run this correctly? I'm currently trying the following from an elevated PowerShell but getting an error
Something I noticed is that everytime I run python from the command line (cmd) the Windows "App-Installer" window will briefly pop-up before the command is executed
This is known (#219) and fixed in the OS, just need to wait for the updates to roll out.
But I wonder if it's related...? Setting the network profile to unmetered should fix the popup, and it's possible that this app isn't supported under OpenSSH and could be the part causing the break? If not, it's possible the cause is just the app execution alias, which would be annoying, but I think in this kind of context (remote server) using the MSI installer is appropriate anyway. Knowing for sure will help us update the docs clearly though.
Regarding using Add-AppxProvisionedPackage, how do I run this correctly?
As far as I'm aware, this is correct, so the error would seem to be unrelated to SSH. Could you run a Get-AppxLog -All or dive into the Microsoft\Windows\AppXDeployment-Server and Microsoft\Windows\AppxPackagingOM event logs and see if there's more info? I'll have to take this one to the MSIX team, and I know that's the first thing they're going to ask for. I might need to try and repro this one myself though, so thanks for flushing it out.
Interesting - I am actually not on a metered connection and the Ethernet interface is not configured as metered connection. I'm trying to find out why this is the case so I can disable it and see if it changes the behavior.
Regarding using Add-AppxProvisionedPackage (executed after 11:00):
PS C:\Users\jenkins\Downloads> Add-AppxProvisionedPackage -Online -PackagePath .\python-manager-26.0.msix
Add-AppxProvisionedPackage : Add-AppxProvisionedPackage failed. Error code = 0xc1570104
At line:1 char:1
+ Add-AppxProvisionedPackage -Online -PackagePath .\python-manager-26.0 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Add-AppxProvisionedPackage], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.AddAppxProvisionedPackageCommand
PS C:\Users\jenkins\Downloads> Get-AppxLog -All
Time ID Message
---- -- -------
25.03.2026 10:48:55 821 During-logon registration of package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe for user S-1-5-21-4116067536-236379865-2870566812-1005 finished with
result: 0x0; updating registry...
25.03.2026 10:48:55 822 Updating registry for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe completed with result: 0x0.
25.03.2026 10:48:55 603 Started deployment Register operation on a package with main parameter AppxManifest.xml and Options
ForceTargetApplicationShutdownOption,SkipReregisterIfPackageStatusOk,NormalPriorityRequest,ImmediatePriorityRequest,FirstLogonInstall and
SkipDeploymentOperationRpcCallerIsAdminCheck. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
25.03.2026 10:48:55 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\23abcdbc-933c-42d9-99ee-df45620f35a2_S-1-5-21-4116067536-236379865-2870566812-1005_2.rslc for Register
Operation on Package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 607 Deployment Register operation on package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe has been de-queued and is running for user SID
S-1-5-21-4116067536-236379865-2870566812-1005.
25.03.2026 10:48:55 854 Successfully added the following uri(s) to be processed: C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\AppxManifest.xml.
25.03.2026 10:48:55 855 Finished resolving action lists. DeploymentRequest action lists: updateList: Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe is updating to
Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 626 Deployment Register operation on package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe has been requeued for user SID
S-1-5-21-4116067536-236379865-2870566812-1005.
25.03.2026 10:48:55 607 Deployment Register operation on package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe has been de-queued and is running for user SID
S-1-5-21-4116067536-236379865-2870566812-1005.
25.03.2026 10:48:55 854 Successfully added the following uri(s) to be processed: C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\AppxManifest.xml.
25.03.2026 10:48:55 855 Finished resolving action lists. DeploymentRequest action lists: updateList: Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe is updating to
Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x0,
Set=0x20).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x0,
Set=0x20).
25.03.2026 10:48:55 647 Removing registrations for DownlevelInstalled package Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x0,
Set=0x10000820).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005
(Clear=0xFFFFFFFF, Set=0x0).
25.03.2026 10:48:55 5507 Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\microsoft.syst
em.package.metadata\S-1-5-21-4116067536-236379865-2870566812-1005-MergedResources-*.pri : No user-specific merged files found
25.03.2026 10:48:55 5507 Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe : C:\Program
Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\microsoft.system.package.metadata\Resources.????????.pri : No shared merged files found
25.03.2026 10:48:55 5507 Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\microsoft.syst
em.package.metadata\S-1-5-21-4116067536-236379865-2870566812-1005-MergedResources-*.pri : No user-specific merged files found
25.03.2026 10:48:55 5507 Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe : C:\Program
Files\WindowsApps\Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe\microsoft.system.package.metadata\Resources.????????.pri : No shared merged files found
25.03.2026 10:48:55 813 Successfully updated all user store with package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x20,
Set=0x0).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x20,
Set=0x0).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x20,
Set=0x0).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005
(Clear=0x10000C00, Set=0x0).
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x300,
Set=0x0).
25.03.2026 10:48:55 400 Deployment Register operation with target volume C: on Package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe from: (AppxManifest.xml) finished successfully.
25.03.2026 10:48:55 613 Performance summary of Deployment Register operation on Package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe:
Overall time: 719 ms
Gap: 109 ms
Enqueue cost: 78 ms
Dequeue delay: 94 ms
Bundle processing cost: 0 ms
Indexing cost: 16 ms
Resolve dependency cost: 62 ms
Check approval cost: 16 ms
Evaluation cost: 0 ms
Hardlinking evaluation cost: 0 ms
Stage required cost: 0 ms
Flushing and closing files cost: 0 ms
Gap: 31 ms
Machine register cost: 31 ms
Stage user data cost: 0 ms
Registration cost: 172 ms
Repository commit transaction cost: 32 ms
Gap: 31 ms
Data flush cost: 0 ms
Post DeStage repository commit transaction cost: 31 ms
Remaining cost: 16 ms
25.03.2026 10:48:55 821 During-logon registration of package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe for user S-1-5-21-927429425-606537799-860360866-8721 finished with result:
0x0; updating registry...
25.03.2026 10:48:55 822 Updating registry for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe completed with result: 0x0.
25.03.2026 10:48:55 821 During-logon registration of package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe for user S-1-5-21-927429425-606537799-860360866-19102 finished with result:
0x0; updating registry...
25.03.2026 10:48:55 822 Updating registry for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe completed with result: 0x0.
25.03.2026 10:48:55 821 During-logon registration of package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe for user S-1-5-21-4116067536-236379865-2870566812-500 finished with result:
0x0; updating registry...
25.03.2026 10:48:55 822 Updating registry for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe completed with result: 0x0.
25.03.2026 10:48:55 821 During-logon registration of package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe for user S-1-5-21-4116067536-236379865-2870566812-1005 finished with
result: 0x0; updating registry...
25.03.2026 10:48:55 822 Updating registry for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe completed with result: 0x0.
25.03.2026 10:48:54 604 Started deployment OnDemandRegisterOperation operation on a package with main parameter , dependency parameters Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe
and Options ImmediatePriorityRequest and 0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
25.03.2026 10:48:55 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\23abcdbc-933c-42d9-99ee-df45620f35a2_S-1-5-21-4116067536-236379865-2870566812-1005_1.rslc for
OnDemandRegisterOperation Operation on Package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe.
25.03.2026 10:48:55 607 Deployment OnDemandRegisterOperation operation on package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe has been de-queued and is running for user SID
S-1-5-21-4116067536-236379865-2870566812-1005.
25.03.2026 10:48:55 679 OnDemandRegisterPackageList Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe .
25.03.2026 10:48:55 617 Successfully updated the status for package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe and user S-1-5-21-4116067536-236379865-2870566812-1005 (Clear=0x400,
Set=0x10000800).
25.03.2026 10:48:55 642 OnDemandRegisterPackage found existing package Microsoft.MicrosoftEdge.Stable_146.0.3856.59_neutral__8wekyb3d8bbwe, set PACKAGE_STATUS_REGISTRATION_REQUIRED_BLOCKING
25.03.2026 10:48:55 400 Deployment OnDemandRegisterOperation operation with target volume C: on Package Microsoft.MicrosoftEdge.Stable_146.0.3856.78_neutral__8wekyb3d8bbwe from: finished successfully.
25.03.2026 10:48:54 819 The following packages will be installed: . The following packages will be removed:
25.03.2026 10:48:53 819 The following packages will be installed: . The following packages will be removed:
<...>
So there seem to be no messages regarding the failed call to Add-AppxProvisionedPackage.
Regarding event logs:
Nothing in Microsoft\Windows\AppXDeployment-Server (latest event from 10:48:55, prior to calling Add-AppxProvisionedPackage)
There is an event in Microsoft\Windows\AppxPackagingOM at 11:04:41 stating "The reader was created successfully for app package PythonSoftwareFoundation.PythonManager_26.0.240.0_x64__3847v3x7pw1km."
As mentioned previously, I was unable to reproduce the issue on a different Windows 11 host.
I can reproduce the issue on this host if I configure the Ethernet interface as "metered connection".
After changing this, I also start getting the "App Installer" popup each time when running python (logged in via remote desktop).
When logging in via SSH, I now get the same error as on the Windows Server 2025 host when trying to run python.
If I disable the "metered connection", the error goes away.
When logging in via SSH, I now get the same error as on the Windows Server 2025 host when trying to run python.
If I disable the "metered connection", the error goes away.
Okay, that's great to hear. Hopefully the updates roll out nice and soon, though it's possible that Windows Server will get them slower. My understanding is that the fix is in the App Installer app, not the OS itself, so normally it would be the Store that runs the updates. Not entirely sure how that works on Server.
I am actually not on a metered connection and the Ethernet interface is not configured as metered connection.
I vaguely recall someone saying something about Windows Server having a (non-UI) third state by default for connections that was being misinterpreted as metered, so it's possible there isn't a workaround here, or maybe switching into metered and then out of it will get you to a working place.
Activity
zooba commentedon Jan 15, 2026
Hmm, interesting. This is going to need setting up and testing, which may take some time for me to get to.
I suspect that OpenSSH isn't running in a native Windows shell (cmd/PowerShell) on the remote system - though I could be wrong - and whatever shell it's using doesn't support app execution aliases (e.g. Cygwin didn't support it until a couple years ago, and still has bugs, and most Bash shells for Windows are based on Cygwin's so they have the same bugs).
The easiest workaround should be to use the MSI installer for this case. But there may be something else going on, since I don't actually know how OpenSSH works.
iBz-04 commentedon Jan 21, 2026
did you choos the Install Python for 'all users' during installation , also you can also attempt to call the actual executable directly if you can locate its installation path in C:\Program Files\WindowsApps, though this is difficult due to permissions
DarkArc commentedon Jan 22, 2026
I uninstalled the install manager from that server and went back to the old installers.
If I recall correctly, I think the issue has something to do with the mechanism requiring a graphical environment. I noticed a window being created briefly when running python through the install manager. That seemed to happen even when I ran python over SSH.
My presumption is that without the graphical environment it just doesn't operate properly (note if you are logged in to the graphical environment this DOES/did work). I don't know how fixable that is.
I'm not much of a Windows guy; this was largely a courtesy bug report. I unfortunately don't have time currently to try again and troubleshoot.
zooba commentedon Jan 22, 2026
Okay, thanks for the notification. If I get a chance to set up a repro environment, I'll have a look, but if anyone else has one and has the time to try a few things, that'd be really helpful too.
wrightsg commentedon Mar 11, 2026
+1
Ran into this trying to use Python install manager for a Jenkins build agent (running Windows Server 2025). In this use case, Jenkins runs a script that calls
pythonvia SSH which subsequently fails.Need to revert to MSI installer for now...
I can reproduce the issue and run some tests if you want.
zooba commentedon Mar 17, 2026
@wrightsg That would be really helpful. I think the main things I'd like to confirm are:
Add-AppxProvisionedPackage -Online -PackagePath python-manager-<version>.msix(and possibly reconnecting/rebooting after, though it shouldn't be necessary)%LocalAppData%\Python\bin, but you'll have to have installed a version first)wrightsg commentedon Mar 19, 2026
Tried reproducing on a different Windows 11 machine as I currently cannot remove the MSI installed
pythonversion from the Windows Server 2025 machine - it seems to be working on this setup.Installed from the MISX downloaded from python.org
Then logging in via SSH
Will try reproducing on the Windows Server 2025 machine again once it is not being used.
wrightsg commentedon Mar 24, 2026
So I went back to the Windows Server 2025 setup, uninstalled the "Python Launcher" (from the Python 3.12 MSI installer) and reinstalled the Python Install Manager, again using the MISX installer from python.org.
When logged in via remote desktop, I can do the following:
Something I noticed is that everytime I run
pythonfrom the command line (cmd) the Windows "App-Installer" window will briefly pop-up before the command is executed (as shown here: https://www.youtube.com/watch?v=Aqlwk3py5s8)When logged in via SSH:
But the following works:
Furthermore, if I log in via remote desktop, keep the session open and then also log in via SSH, it suddenly works
Regarding using
Add-AppxProvisionedPackage, how do I run this correctly? I'm currently trying the following from an elevated PowerShell but getting an errorzooba commentedon Mar 25, 2026
This is known (#219) and fixed in the OS, just need to wait for the updates to roll out.
But I wonder if it's related...? Setting the network profile to unmetered should fix the popup, and it's possible that this app isn't supported under OpenSSH and could be the part causing the break? If not, it's possible the cause is just the app execution alias, which would be annoying, but I think in this kind of context (remote server) using the MSI installer is appropriate anyway. Knowing for sure will help us update the docs clearly though.
As far as I'm aware, this is correct, so the error would seem to be unrelated to SSH. Could you run a
Get-AppxLog -Allor dive into theMicrosoft\Windows\AppXDeployment-ServerandMicrosoft\Windows\AppxPackagingOMevent logs and see if there's more info? I'll have to take this one to the MSIX team, and I know that's the first thing they're going to ask for. I might need to try and repro this one myself though, so thanks for flushing it out.wrightsg commentedon Mar 25, 2026
Interesting - I am actually not on a metered connection and the Ethernet interface is not configured as metered connection. I'm trying to find out why this is the case so I can disable it and see if it changes the behavior.
Regarding using
Add-AppxProvisionedPackage(executed after 11:00):So there seem to be no messages regarding the failed call to
Add-AppxProvisionedPackage.Regarding event logs:
Microsoft\Windows\AppXDeployment-Server(latest event from 10:48:55, prior to callingAdd-AppxProvisionedPackage)Microsoft\Windows\AppxPackagingOMat 11:04:41 stating "The reader was created successfully for app package PythonSoftwareFoundation.PythonManager_26.0.240.0_x64__3847v3x7pw1km."wrightsg commentedon Mar 25, 2026
OK so the issue seems to be related to #219 .
As mentioned previously, I was unable to reproduce the issue on a different Windows 11 host.
I can reproduce the issue on this host if I configure the Ethernet interface as "metered connection".
After changing this, I also start getting the "App Installer" popup each time when running
python(logged in via remote desktop).When logging in via SSH, I now get the same error as on the Windows Server 2025 host when trying to run
python.If I disable the "metered connection", the error goes away.
zooba commentedon Mar 25, 2026
Okay, that's great to hear. Hopefully the updates roll out nice and soon, though it's possible that Windows Server will get them slower. My understanding is that the fix is in the App Installer app, not the OS itself, so normally it would be the Store that runs the updates. Not entirely sure how that works on Server.
I vaguely recall someone saying something about Windows Server having a (non-UI) third state by default for connections that was being misinterpreted as metered, so it's possible there isn't a workaround here, or maybe switching into metered and then out of it will get you to a working place.
wrightsg commentedon Mar 26, 2026
I was unable to resolve the Windows Server "metered connection" issue.
As a workaround, I installed the Python Install Manager using the MSI installer and performing a global installation.
This resolves the "App Installer" popup, even if Windows thinks its running on a "metered connection".