saret/winget-pkgs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Adjusting -m troubleshooting (#262)

Browse Source 
* Adjusting -m troubleshooting

* Minor adjustment

* hash help

* malware wording adjustment

* syntax ```
This commit is contained in:
denelon
2020-05-18 20:29:47 -07:00
committed by GitHub
parent d7abee7530
commit e045126787
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Troubleshoot.md
View File

@@ -1,9 +1,9 @@
# Troubleshooting Errors
Many of the issues can be caught before submitting your PR, if you follow these steps:
1) Validate the manifest file by running ```winget validate <manifest>```
2) Run the installer with the local installer. This will verify the Sha256 HASH. ```winget install -m <manifest>```
2) Run the installer with the manifest on your local machine. This will verify the Sha256 HASH. ```winget install --manifest <manifest>``` or ```winget install -m <manifest>```
Once those steps pass, here are some troubleshooting tips.
Once those steps pass, here are some troubleshooting tips:
## Manifest-Validation-Error
Manifest validation errors indicate that there is a problem with the manifest file. Many of the issues can be caught before submitting your PR, if you validated the manifest file before submission: ```winget validate <manifest>```
@@ -17,7 +17,7 @@ Here are some common mistakes not discovered by the winget validater.
```folder path: publisher\name```
2) Check for typos in the version. The file name of the manifest must match the Version in the manifest
2) Check for typos in the version. The file name of the manifest must match the ```Version``` in the manifest
```Version: 123.456```
@@ -28,9 +28,9 @@ Here are some common mistakes not discovered by the winget validater.
Binary validation errors indicate that the installer failed static analysis.
Here are some common causes for the Binary-Validation-Error label:
1) The Sha256 HASH in the manifest does not match the HASH of the installer.
2) The URL is not available. Make sure the URL to the installer is available.
3) The installer has triggered false positive. If your installer is detected wrongly as malware, you can submit the installer to the defender team for [analysis](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/antivirus-false-positives-negatives#submit-a-file-to-microsoft-for-analysis) for a false positive.
1) The Sha256 HASH in the manifest does not match the HASH of the installer. Run ```winget hash <installer>``` to generate the hash.
2) The URL is not valid. Make sure the URL to the installer is publicly available and valid.
3) The installer has been identified as malware. If the installer is detected as malware, you can submit the installer to the defender team for [analysis](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/antivirus-false-positives-negatives#submit-a-file-to-microsoft-for-analysis) as a potential false positive.
## SmartScreen-Validation-Error
SmartScreen validation errors indicate that the URL you provided has a bad reputation.