Skip to content

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

Merged
merged 4 commits into from
Jul 2, 2025

Conversation

DandelionSprout
Copy link
Contributor

@DandelionSprout DandelionSprout commented Jun 21, 2025

Checklist for Pull Requests

Manifests

  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • This PR only modifies one (1) manifest
  • Have you validated your manifest locally with winget validate --manifest <path>?
  • Have you tested your manifest locally with winget install --manifest <path>?
  • Does your manifest conform to the 1.10 schema?

Note: <path> is the directory's name containing the manifest you're submitting.


Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Collaborator

Service Badge  Service Badge  

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250621-1

@wingetbot wingetbot added New-Package Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jun 21, 2025
@DandelionSprout
Copy link
Contributor Author

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 https://pureinfotech.com/kb5034510-windows-printer-rename-fix/.

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250621-2

@microsoft-github-policy-service microsoft-github-policy-service bot removed Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error New-Package labels Jun 21, 2025
@wingetbot wingetbot added New-Package Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jun 21, 2025
@stephengillie
Copy link
Collaborator

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\Microsoft.PrintMetadataTroubleshooter__DefaultSource\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Packages\Microsoft.PrintMetadataTroubleshooter__DefaultSource\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\printmetadatatroubleshooter.exe returned exit code: -2135164161

Hex Dec Inverted Dec Symbol Description

(Automated response - build 1077.)

@ItzLevvie
Copy link
Contributor

@wingetbot run

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250629-1

@microsoft-github-policy-service microsoft-github-policy-service bot removed Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jun 29, 2025
@wingetbot wingetbot added Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jun 29, 2025
@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250630-1

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250630-3

@microsoft-github-policy-service microsoft-github-policy-service bot removed Internal-Error-Dynamic-Scan The test for Dynamic Scanning in the Installation Validation failed. Needs-Attention This work item needs to be reviewed by a member of the core team. labels Jun 30, 2025
@wingetbot wingetbot added New-Package Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jun 30, 2025
@ItzLevvie
Copy link
Contributor

@wingetbot run

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-65-267426-20250701-1

@microsoft-github-policy-service microsoft-github-policy-service bot removed Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jul 1, 2025
@wingetbot wingetbot added Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Executable-Error labels Jul 1, 2025
@stephengillie
Copy link
Collaborator

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\Microsoft.PrintMetadataTroubleshooter__DefaultSource\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Packages\Microsoft.PrintMetadataTroubleshooter__DefaultSource\printmetadatatroubleshooter.exe returned exit code: -2135164161 Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\printmetadatatroubleshooter.exe returned exit code: -2135164161

Hex Dec Inverted Dec Symbol Description

(Automated response - build 1078.)

Copy link
Contributor

@ItzLevvie ItzLevvie left a 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

@DandelionSprout
Copy link
Contributor Author

DandelionSprout commented Jul 2, 2025

  • "Troubleshooter not applicable since metadata package not found"

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.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels Jul 2, 2025
@ItzLevvie
Copy link
Contributor

[Policy] Needs-Manual-Merge

@microsoft-github-policy-service microsoft-github-policy-service bot added Moderator-Approved One of the Moderators has reviewed and approved this PR Needs-Manual-Merge The pull request requires a manual merge from a repository maintainer labels Jul 2, 2025
@stephengillie stephengillie merged commit 672797d into microsoft:master Jul 2, 2025
1 check passed
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Attention This work item needs to be reviewed by a member of the core team. label Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Changes-Requested Changes Requested Moderator-Approved One of the Moderators has reviewed and approved this PR Needs-Manual-Merge The pull request requires a manual merge from a repository maintainer New-Package Retry-1 flag to indicate retried Validation-Executable-Error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants