New package: Autodesk.AutoCAD.2022 version 24.1.51.0

[rovabunw]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

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.9 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[Trenly]

[DuckDuckStudio]

The size of this package is over 1GB and I was UNABLE to download it. You can try other parameters based on the documentation (like --silent).

[wingetbot]

/AzurePipelines run

[rovabunw]

You can try other parameters based on the [documentation]

These type of Autodesk setups need a specific approach.

1. sfx extraction

First AutoCAD_2022_English_Win_64bit_dlm.sfx.exe needs to be extracted using:

-suppresslaunch -d

2. run setup.exe

Then in the extracted directory ..\AutoCAD_2022_English_Win_64bit_dlm\setup.exe needs to be run using -q

[rovabunw]

Hello @rovabunw,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

These type of Autodesk setups need a specific approach.

1. sfx extraction

First AutoCAD_2022_English_Win_64bit_dlm.sfx.exe needs to be extracted using:

-suppresslaunch -d

2. run setup.exe

Then in the extracted directory ..\AutoCAD_2022_English_Win_64bit_dlm\setup.exe needs to be run using -q

[ItzLevvie]

@wingetbot run

[ItzLevvie]

[Policy] Reset Feedback
[Policy] Reset Labels

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[microsoft-github-policy-service]

Hello @rovabunw,

The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case.

Example:
Path: manifests / m / Microsoft / WindowsTerminal / 1.6.10571.0 / WindowsTerminal.yaml

For details on the error, see the details link below in the build pipeline.

You may also try the Windows Package Manager Manifest Creator

Template: msftbot/validationError/pullRequest

[stephengillie]

The situation is unchanged.

[ItzLevvie]

[Policy] Blocking-Issue

[rovabunw]

The situation is unchanged.

Correct because this is not supported yet: #207759

[ItzLevvie]

@wingetbot run

[wingetbot]

/AzurePipelines run

[ItzLevvie]

[Policy] Blocking-Issue

[microsoft-github-policy-service]

Hello @rovabunw,

Please verify the manifest file is compliant with the package manager 1.9 manifest specification.

Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.

Note: The path and "PackageIdentifier" are case sensitive.

Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the winget validate command.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/content

[ItzLevvie]

[Policy] Reset Feedback