Brief description of your issue
I would like to bootstrap WinGet and several WinGet packages on new Win10 systems.
What is the correct approach that handles dependencies appropriately and does not require user interaction?
This is what I'm using and it will break as soon as the dependency versions change. It's also not possible to install MS Store applications because of a interactive license acceptance prompt that does not honor the --accept-source-agreements argument.
Brief description of your issue
I would like to bootstrap WinGet and several WinGet packages on new Win10 systems.
What is the correct approach that handles dependencies appropriately and does not require user interaction?
This is what I'm using and it will break as soon as the dependency versions change.
It's also not possible to install MS Store applications because of a interactive license acceptance prompt that does not honor the--accept-source-agreementsargument.