PVANet Moodle Updates to 4.5: What Changes at UFV

The PVANet Moodle, the virtual learning environment of the Federal University of Viçosa (UFV), was updated to Moodle 4.5 in February 2026 — and the main motivation was not aesthetic, it was security. The migration places one of the largest public institutions in Minas Gerais on an LTS version, with a new interface and extended security support. I have gathered here what changed, with official sources, and what this teaches any institution running Moodle in Brazil.

TL;DR

• The PVANet Moodle is UFV's official VLE, used to support face-to-face and distance learning across its three campuses (Viçosa, Florestal, and Rio Paranaíba).
• On 6 February 2026, the environment was updated to Moodle 4.5 LTS, focusing on security, a more modern layout, and new icons — without losing content from previous courses.
• Version 4.5 is LTS (Long Term Support): it receives security fixes until October 2027, compared to ~18 months for standard versions.
• Moodle 4.5 introduced the AI subsystem and consolidated multi-factor authentication (MFA), available since 4.3.
• The lesson for those managing distance learning: running an unsupported version (like Moodle 3.x) is a cybersecurity risk, not a saving.

What is UFV's PVANet Moodle

PVANet Moodle is the virtual learning platform that UFV uses to support both face-to-face courses and distance learning. In practice, it is where students and teachers meet outside the classroom: handouts and texts, videos and audiovisual content, external links, discussion forums, assignment submissions, and online assessments are all concentrated there.

Access is via CPF or institutional email as identification, and the password is the same as that used for other university systems — the famous single sign-on. Administration and support are handled by the Coordination of Open and Distance Education (CEAD), reachable at [email protected]. This design — Moodle as the core of institutional distance learning, with integrated identity and a dedicated team — is the same model I see in dozens of Brazilian institutions, from large federal universities to corporate training centres.

What changed in the PVANet Moodle update to 4.5

CEAD communicated the new version and listed what changes in practice. The changes focus on three fronts:

• Security: the stated reason for the update. Version 4.5 brings system protection and stability improvements, which is crucial in an environment that stores grades, personal data of thousands of students, and teachers' copyrighted material.
• Interface: a more intuitive, modern, and pleasant layout, with a new set of icons. Those who used PVANet Moodle will notice the revamped navigation on first access.
• New features: the update incorporates functionalities that improve the user experience for teachers, tutors, and students.

A point worth highlighting, and often the biggest headache for any administrator: all content and structures from previous semesters' courses were retained, with no loss of information. The migration preserved the history. Before go-live, there was scheduled maintenance — the system was unavailable on Tuesday, 3 February 2026, between 8am and 8pm — a typical window for a database and file upgrade of this size.

Why UFV chose an LTS version

The decision to go to Moodle 4.5 (and not an intermediate version) is not trivial. 4.5 is an LTS — Long Term Support release, and that completely changes the risk calculation. LTS versions receive security fixes for about three years, while standard versions drop security support after around 18 months.

Translating the official Moodle project calendar: general bug fixes for 4.5 ended in October 2025, but security fixes continue until October 2027. For a public institution that does not change versions every semester, choosing LTS means skipping upgrade cycles while still receiving security patches. It is the most conservative choice — and the most sensible — for critical environments.

The table below summarises why version position matters so much:

Moodle Version	Type	Security Support	Recommendation
3.x	Old	Ended since 2023	Migrate urgently
4.1 / 4.3	Standard / Old LTS	Expired or ending	Plan upgrade
4.5	LTS	Until October 2027	Recommended target today
5.x	Recent standard	~18 months	Only with active team

Running Moodle 3.x today is not a saving: it is a cybersecurity liability. Without patches, each publicly disclosed vulnerability becomes a map for anyone wanting to invade the environment.

The AI subsystem and other 4.5 novelties

Beyond security, Moodle 4.5 brought the most talked-about feature of the cycle: a native Artificial Intelligence subsystem. It allows connecting Moodle to an AI provider (such as OpenAI or Azure) to offer text and image generation within the environment itself. It is not a loose chatbot — it is a layer that teachers and administrators can enable and control.

Another important front is multi-factor authentication (MFA), available in Moodle core since version 4.3 and fully supported in 4.5. MFA requires more than one verification method at login (e.g., password + code) and is one of the cheapest and most effective defences against credential theft — something especially valuable in an academic environment where weak and reused passwords are common. In an environment the size of PVANet Moodle, with thousands of active accounts and single sign-on shared with other systems, MFA ceases to be optional and becomes basic security hygiene.

The revamped interface also has a practical effect that many underestimate: clearer navigation reduces support tickets. When students find the assignment, forum, and grade without needing a tutorial, the CEAD team spends less time answering "where do I click" and more time on what matters. Usability, in this sense, is also operational efficiency.

It is worth noting that enabling the AI subsystem is an institutional decision. Connecting generative AI to an environment with minors' data and sensitive academic information requires a usage policy, anonymisation, and attention to LGPD (Brazil's General Data Protection Law). The technology is ready; responsible use depends on governance.

What the PVANet Moodle update teaches other institutions

UFV's case is a good mirror because it did its homework: it communicated the maintenance in advance, chose an LTS version, preserved data, and even published support material for users. It is the roadmap every school, college, or training department should follow. Three lessons stand out:

• Updating is security, not a whim. Most institutions only think about an upgrade when something breaks. UFV's move shows the opposite: updating before support ends is what prevents a crisis.
• LTS is the way for those who don't live and breathe Moodle. If your team doesn't follow the project month by month, stick with LTS. You reduce upgrade frequency without sacrificing security patches.
• Communication is part of the migration. Announced maintenance window, support material, and a support channel ([email protected]) reduce friction with students and teachers as much as the technical work itself.

I am Moodle certified and have managed critical distance learning environments for educational institutions. The technical part of the upgrade is almost never the bottleneck — what derails projects is lack of planning: incompatible plugins discovered mid-way, custom theme that won't load, grade integration that stops. That's why the work starts long before the update button.

How to update your Moodle to 4.5 without losing data

If your institution still runs an old version, here is a summary of the process I apply in real migrations. It's not a recipe — each environment has its particularities — but the order matters.

Before the upgrade

1. Inventory of plugins and theme. List everything installed and check compatibility with 4.5. Abandoned plugins are the number one reason for a stalled upgrade.
2. Full backup. Database, moodledata directory, and code. Without a tested backup, there is no migration — there is a gamble.
3. Staging environment. Set up an identical copy and update there first. That's where problems appear without affecting anyone.
4. Version path. Very long jumps (3.x straight to 4.5) may require intermediate versions. Plan the route.

During and after

1. Communicated maintenance window, as UFV did — outside peak hours, with prior notice.
2. Update code, then database, in the order Moodle requires, with maintenance mode on.
3. Smoke tests: login, access a course, submit an assignment, enter a grade, mobile app.
4. Post-upgrade: review logs, validate emails and notifications, and only then release to users.

The most common trap I see is updating directly in production "because it's quick." When it goes wrong at 9am on a Monday during term, the damage is institutional, not technical.

Mobile and engagement: the next step after the update

Updating Moodle solves security and technological foundation, but it does not alone solve student engagement. A modern environment like PVANet Moodle opens space for what really moves the needle: mobile experience and active communication. Here, Moodle 4.5 works well with app strategies.

For institutions that want to go beyond the browser, it is worth understanding the advantages of a custom Moodle app over the official app and how push notifications in the Moodle app work as an engagement multiplier. If the doubt is still between using the standard app or investing in a custom one, this comparison between the Moodle Mobile App and the custom app helps decide. And for those following the distance learning landscape, I recommend the overview of Google Classroom's 2026 novelties, which shows how AI is reorganising teaching environments.

Conclusion: updating is maintenance, not an event

The update of PVANet Moodle to version 4.5 is the kind of news that seems small but says a lot: UFV treated the upgrade as preventive security maintenance, not a heroic event. This is the standard every institution should copy — LTS version, preserved data, clear communication, and a technical team in charge.

If your institution runs an old Moodle version, or is unsure how to migrate without bringing down the environment mid-semester, this is exactly the kind of project Agathas Web handles: hosting, updating, performance optimisation, and custom apps for distance learning. The first step is simple — find out which version you are on and your level of exposure. From there, you can plan the path to 4.5 calmly, not in a panic.