Adi

> The reason we've done it the way we have is to get as close as possible to a proper random sampling of users. Since it is a publicly reachable...

note: that the issue opened for WinGet was closed today with the reason "This issue has been identified as requiring a fix from a third party or external repository. Since...

i see that v7.4.3 is now published via Windows Update.... (published on July 22nd, 2024) and that version contains the pull request that *technically* fixes the inheritance of settings from...

**re-opening the issue:** i see that PowerShell version 7.4.4 was released yesterday https://github.com/PowerShell/PowerShell/releases/tag/v7.4.4 and it seems to not not preserve anymore the initial installation settings from the previous versions (and...

just noticed that pwsh 7.4.5 is now available and it supposedly now preserves the installation options from the previous version... https://github.com/PowerShell/PowerShell/pull/24143 unfortunately that is still not the case, i just...

winget started showing today that pwsh version 7.4.6 is available as upgrade from 7.4.5 before upgrade: ``` > $env:POWERSHELL_TELEMETRY_OPTOUT 1 > ``` after upgrade (and a full system reboot just...

> > Your last image showing two different installations, 7.4.3.0 and 7.4.4.0, this should not occur if both have the same UpgradeCode. So it would be worth getting to the...

wmic product list brief only contains a single entry for pwsh - the MSI one, with the same `31AB5147-9A97-4452-8443-D9709F0516E1` UpgradeCode for me too, but the one installed via the EXE...

i have uninstalled both MSI and EXE, decided to install just the EXE and check.. it has the same 31AB5147-9A97-4452-8443-D9709F0516E1 UpgradeCode but even if it has a DisplayName of x64...

> I would suggest use a single source for your installer and don't mix and match over time. Eg either download the MSI from here or use WinGet and leave...