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
{{ message }}
Repository navigation
WindowsInstaller.Tests.ps1 test WMF link invoke tests failing... #13478
Name Value
---- -----
PSVersion 7.0.3
PSEdition Core
GitCommitId 7.0.3
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
This test checks for expected links in Product.wxs file, but then invokes the links to see if they are alive. Many times they are not and there is a retry loop. In this case WMF 4.0 link is not working. Don't know if the link was pulled on purpose.
However, this does not seem like a good test for PowerShell, as PowerShell has nothing to do whether these links work and if they don't should not cause PowerShell build to fail. I will mark the link invocation test as 'pending'.
I guess .Net 6.0 will support Windows 7. And question is will we support the next LTS version PowerShell 7.2 on Windows 7? If yes, maybe MSFT approve distributing WMF 4 in PowerShell 7.2 packages as an optional unsupported update?
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
Activity
daxian-dbw commentedon Aug 19, 2020
Travis Plunk (@TravisEz13), if the that WMF 4 link is not coming back, then we potentially need to change the link in the installer script.
TravisEz13 commentedon Aug 19, 2020
Sounds right, I think anyone can change the link.
iSazonov commentedon Aug 20, 2020
I found short link http://go.microsoft.com/fwlink/?LinkId=293881 - does not work too.
daxian-dbw commentedon Aug 20, 2020
Joey Aiello (@joeyaiello) and Sean Wheeler (@sdwheeler), can you please check with someone from the download center to see if it's intentional to remove the WMF 4 download link?
joeyaiello commentedon Aug 20, 2020
Yeah, we're following up.
joeyaiello commentedon Dec 14, 2020
Still looking into seeing what can be done here, would love to know if this is impacting anyone today out in the real world.
iSazonov commentedon Dec 15, 2020
Is it all about Windows 7 support? If intention is to support Windows 7 in .Net 6.0 I think we still need WMF 4.0 with updates.
iSazonov commentedon Jan 18, 2021
I guess .Net 6.0 will support Windows 7. And question is will we support the next LTS version PowerShell 7.2 on Windows 7? If yes, maybe MSFT approve distributing WMF 4 in PowerShell 7.2 packages as an optional unsupported update?
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.