Before you start
You need package-viewing access and the corresponding system-writing permission for changes. Establish authority for the intended software and its effect on hosted workloads before submitting an operation.
What to do
- Open Packages and review Installed packages and Available updates. Identify the exact package names involved.
- Use Refresh package index when you intend to refresh available package information, then inspect its operation result.
- For an authorised change, open Manage packages, choose install or upgrade and enter the intended package names separated by spaces as requested by the form.
- Review the selected operation and names before submitting. This selected-package control should not be treated as a general operating-system release upgrade.
- Read the final output, refresh the package information and check the affected applications. Review any restart or maintenance needs separately rather than assuming that an installed package means the running service already uses it.
What happens next
You can distinguish refreshed package information from a completed selected-package operation and its application-level checks.
If something goes wrong
Inspect the exact output for unavailable names, dependency or package-manager errors before another attempt. A timeout or browser disconnection is not proof that the package operation stopped. Ask the infrastructure administrator to reconcile the current operation and package state instead of starting overlapping work or broadening the change to unrelated packages.
