-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New package: Microsoft.PrintMetadataTroubleshooter version 1.0.0.1 #267426
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
Conversation
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250621-1 |
Regarding the "Validation-Executable-Error" label: The .exe seemingly only consistently works when being run from command line (e.g. PowerShell 7), in which case 2 outcomes are apparently possible. Some 99.9% of PCs will show "Troubleshooter not applicable since metadata package not found", with "Metadata" almost certainly meaning an HP printer glitch that the .exe was designed to fix. The remaining few ones will show "Troubleshooter completed successfully" according to |
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250621-2 |
Automatic Validation ended with:
(Automated response - build 1077.) |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250629-1 |
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250630-1 |
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250630-3 |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-65-267426-20250701-1 |
Automatic Validation ended with:
(Automated response - build 1078.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
C:\Users\AMD-EPYC-9655\Downloads>printmetadatatroubleshooter
Troubleshooter not applicable since metadata package not found
C:\Users\AMD-EPYC-9655\Downloads>echo %ERRORLEVEL%
-2135164161
From what info is out there on the internet about the tool, that text is apparently the fully intended outcome for almost all PCs, especially after the fixes that are handled by the tool were supposedly rolled out to all Windows 10 and possibly Windows 11 users later in more or less normal Windows updates in the spring of 2024. |
[Policy] Needs-Manual-Merge |
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.Microsoft Reviewers: Open in CodeFlow