-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Microsoft.Sysinternals.Suite version 2025-05-05 #268323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Sysinternals.Suite version 2025-05-05 #268323
Conversation
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250625-1 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250625-2 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250625-3 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250625-4 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250625-5 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-268323-20250626-1 |
Is the pipeline timing out due to how many files are being extracted? |
Automatic Validation ended with:
(Automated response - build 1078.) |
Does the validation include starting the extracted programs? If that's the case it may be getting stuck at the EULA screen that every Sysinternals utility displays on first launch. I should also mention that I tried to install this manifest on a fresh Windows 10 VM and successfully started all the installed executables, so I'm thinking that this is probably not a problem with the manifest. Anyway, I think this should be manually approved if that's even a possibility as this manifest contains software that not only is digitally signed by Microsoft and passes a security scan from Windows Defender but also, as evidenced in #267741, a manifest pretty much identical to this one with only a less consistent identifier used to be present in this repository |
@gandbg These kind of packages are never passed the automated pipeline for some reason, just like mine before (#256838). But this one can be manually merged after
Validation-Completed
|
fe50b80
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the directory's name containing the manifest you're submitting.Supersedes #267741
Microsoft Reviewers: Open in CodeFlow