QGIS Vector Tools Missing at Home: Installation or Profile?

Open the same QGIS project at home, find the Vector tools gone, and the tunnel looks guilty. It usually is not, even though the VPN is what put the two environments side by side. The project file carries layers, styles and project settings; it does not carry the algorithm catalog. Tools belong to the installation that runs the job and to the profile that installation loaded.

Decide which installation is running the job

An approved remote desktop showing office QGIS looks identical to a local install until you check what is executing. In that arrangement the algorithms come from the remote machine and its profile, while your home computer only draws pixels. Inspect the version and active profile inside the remote session, not the one on your own desktop.

When QGIS runs locally, the home installation supplies everything. The VPN then has one job: reaching the data.

Write down the actual build number, the active profile name and the plugin list on whichever machine is doing the work. Compare that against the combination your GIS owner supports rather than against an old screenshot. Rebuilding a Windows 7 laptop to match a historical menu layout solves nothing and creates a second unsupported environment. If the two machines genuinely differ, agreeing on one supported build is the decision, not a workaround.

The Vector menu reflects the Processing plugin

QGIS fills the Vector menu with shortcuts to algorithms from core providers, so an empty submenu usually means the Processing plugin is not enabled in that installation. Open the plugin manager and confirm the core plugin is switched on, then restart QGIS and look again. This is an application setting, and no amount of tunnel debugging will change it.

You can read the same state from a terminal, which is faster than clicking through menus on a slow link:

$ qgis_process plugins
$ qgis_process list | grep -i "native:buffer"
native:buffer  Buffer
$ qgis_process help native:buffer

Once the plugin answers, compare the provider of the operation you actually need. A native algorithm, an externally supplied provider and a model built in-house can have different prerequisites, and two menus that look alike may not contain the same entry. Note the provider name from the toolbox and check it by name, not by position in the list.

Profiles explain missing tools without a reinstall

A QGIS user profile holds preferences, enabled plugins and Processing configuration, which is exactly the set of things that makes one machine feel different from another. The profile manager opens a separate, clean instance, and that instance will legitimately lack tools your office profile has.

Use a clean profile as a comparison environment, not as a replacement. If the tool appears there, the difference lives in your existing profile's plugins or Processing settings; if it does not, the gap is in the installation and you are looking at the wrong layer entirely.

Copying a colleague's whole profile folder is the wrong shortcut. It drags in unrelated settings, database connection definitions and authentication configuration that were never meant for your account. Ask for the specific provider, model or setting instead, and add it through the supported interface.

That distinction also protects the office setup from your experiments, which matters more than saving ten minutes.

A data-source failure looks different from a missing algorithm

Once the algorithm exists, the next failure you meet will be about reaching the layer. A PostGIS connection, a WMS or WFS endpoint and a file on a mapped drive all fail in their own way, and a drive letter that resolves in the office usually means nothing at home. Use the intended private hostname and the service's own credentials and TLS requirements.

Test in two steps and the error message will tell you which owner to call. Run the operation on a small non-sensitive local sample of the right geometry type first; if that succeeds, the algorithm and profile are fine, so any failure on the private layer belongs to the network or the service. If the sample fails too, stop blaming the VPN and go back to the plugin and profile checks.

Finish by saving the output to the approved location and keeping a short record beside the project: QGIS build, profile, algorithm provider and data paths. The next upgrade or new laptop then starts from facts instead of another round of menu archaeology.