Marquette Windows 11 Upgrade Ahead of Windows 10 End of Support Oct 14 2025

Microsoft’s official end-of-support clock for Windows 10 hits a hard stop on October 14, 2025, and that calendar event has prompted Marquette University IT Services to require every Marquette-owned Windows PC to be running Windows 11 before the deadline — a last-mile migration push that the university says still leaves several hundred machines to be upgraded or replaced.

Background / Overview​

Microsoft’s lifecycle policy is unambiguous: routine security updates, feature and quality patches, and standard technical support for mainstream Windows 10 editions end on October 14, 2025. After that date, devices that remain on Windows 10 will continue to boot and run, but they will no longer receive vendor-supplied OS fixes for newly discovered vulnerabilities unless they are enrolled in a limited Extended Security Updates (ESU) path.
For organizations — especially universities that handle regulated student and research data — running unpatched endpoints isn’t a hypothetical risk. Unsupported systems become easy pivot points for attackers, and an unpatched Windows kernel or driver is precisely the kind of entry vector exploited in ransomware and targeted intrusions. Universities therefore treat the vendor end-of-support date not as an optional target but as an operational deadline for upgrades, replacements, or sanctioned exceptions.
Microsoft does offer a short-term consumer ESU program that provides security-only updates through October 13, 2026, for eligible Windows 10 devices; there are free and paid enrollment paths depending on account configuration and region. ESU is explicitly a temporary bridge, not a long-term replacement for migration to a supported OS.

---

What Marquette is telling faculty and staff​

Marquette’s IT Services has reiterated the university-wide mandate: all Marquette-owned Windows computers must be on Windows 11 by the Microsoft deadline to remain supported on the campus network. In prior communications the university laid out an in-place upgrade window and a replacement path for devices that fail Windows 11’s hardware baseline; Marquette is coordinating upgrades via the Microsoft Software Center and the campus TechSquad help channels.
The university’s notice indicates that the IT Services team has been triaging upgrade anomalies since the February migration window, yet a subset of machines remains on Windows 10. The posted staff reminder includes a headcount of machines still running Windows 10; that number is reported by Marquette as 304 devices. That figure appears in the internal/messaging text provided to the campus community; independent public verification of the precise headcount was not available at the time of reporting and should be treated as the university’s internal inventory snapshot. Treat the 304 figure as the university’s reported count rather than a third‑party verified audit.
What Marquette asks faculty and staff to do, in short:

• Check — confirm whether your assigned or department machine is still on Windows 10.
• Upgrade — use Microsoft Software Center to initiate the in-place upgrade to Windows 11 at a time that minimizes disruption.
• Replace — if your device does not meet the Windows 11 hardware requirements, it must be replaced; CRP‑eligible machines will be handled via the Computer Replacement Program and non‑CRP replacements are the department’s responsibility.
• Back up — save important files to OneDrive before upgrading (the in-place upgrade should preserve data, but backups are best practice).
• Seek help — open a TechSquad ticket or email TechSquad@marquette.edu for assistance.

---

Why October 14 matters — the security and compliance implications​

The end-of-support date is not a cosmetic deadline. Microsoft’s monthly cumulative updates and out-of-band security fixes are the primary mechanism for mitigating newly discovered vulnerabilities in the OS kernel, drivers, and system services. Once those updates stop for an OS version, the attack surface that security controls must cover grows over time. For environments that process regulated data — financial records, student records (FERPA), or health information (HIPAA) — continuing to run unsupported endpoints increases regulatory and contractual risk.
Security teams also face operational headwinds after EoS:

• New vulnerabilities that affect the Windows kernel or core subsystems will remain unpatched, leaving endpoints exposed to remote code execution or privilege escalation exploits.
• ISVs and hardware vendors will de-prioritize Windows 10 testing; driver updates and compatibility patches become rarer.
• Third-party EDR/AV products cannot substitute for vendor patches; while they reduce risk, they are not a complete mitigation for unpatched OS-level flaws.

Universities typically respond by enforcing a combination of migration, replacement and compensating controls (network segmentation, NAC, or isolating legacy machines). Several campuses have set internal enforcement dates that pre‑date Microsoft’s EoS to give departments time to complete procurement and user training without risking service interruption.

---

Windows 11 minimum requirements — the upgrade eligibility checklist​

Upgrading in place is the simplest route when the hardware supports it, but Windows 11 enforces a stricter baseline than Windows 10. Marquette IT and other enterprise teams have relied on these requirements when auditing fleets. The key minimums are:

• Processor: 1 GHz or faster, 2 or more cores, and must appear on Microsoft’s supported CPU list (64‑bit required).
• RAM: 4 GB minimum.
• Storage: 64 GB or larger.
• System firmware: UEFI with Secure Boot capability.
• TPM: Trusted Platform Module (TPM) version 2.0 (discrete TPM or firmware-based fTPM).
• Graphics: DirectX 12 / WDDM 2.x compatible GPU.

Devices often manufactured since roughly 2018 can meet these requirements by enabling TPM and Secure Boot in UEFI; older machines or niche hardware may be incompatible and require replacement. Use the Microsoft PC Health Check or OEM tooling to confirm eligibility before attempting an in-place upgrade.

---

The Extended Security Updates (ESU) lifeline — rules, costs and regional nuance​

ESU is a deliberate, time-limited bridge: security-only fixes, no new features, and no general technical support. For consumers, Microsoft published three enrollment paths: signing into a Microsoft account and syncing PC settings (free path), redeeming Microsoft Rewards points, or a one-time paid purchase that has been widely documented at around $30 (local taxes may apply). For enterprises, ESU is available via volume licensing for up to three years with progressively higher per-device pricing.
Important operational notes:

• ESU only covers Critical and Important categories of fixes as defined by Microsoft’s security response center.
• Consumer ESU enrollment requires Windows 10 version 22H2 and certain servicing prerequisites to be installed.
• ESU is explicitly a bridge — organizations should plan to migrate off Windows 10 entirely rather than extend ESU year after year.

A recent regional twist: regulators and consumer groups in Europe pressed Microsoft on the $30 consumer fee, and Microsoft announced a concession for the European Economic Area (EEA) that allows free ESU access under certain conditions (for example, a Microsoft account check-in policy). That regional exception does not automatically apply in other markets such as the U.S., where the paid or data-sharing enrollment paths remain in effect. This regulatory nuance is significant for multinational campuses that host devices across regions or for faculty who travel internationally with university machines. Check the specific enrollment rules that apply to your region and account type before relying on ESU as a fallback.

---

Practical, step-by-step actions for Marquette faculty and staff​

• Confirm OS and eligibility now
• Check your assigned machine (Start > Settings > System > About) to confirm whether it’s running Windows 10 and which build.
• Run the PC Health Check or consult Marquette’s inventory/IT contacts if you’re unsure whether firmware changes (enable TPM/Secure Boot) can make your machine eligible for Windows 11.
• Back up first
• Save documents and essential data to OneDrive (university-recommended) or another reliable backup before upgrading. The in-place upgrade normally preserves files and apps, but backups mitigate risk.
• Attempt the in-place upgrade
• If your device is eligible, use the Microsoft Software Center as Marquette IT suggests to initiate the upgrade at a convenient time. Expect the process to take up to two hours and to include automatic restarts.
• If your device is incompatible
• Determine whether the device is CRP-eligible (Computer Replacement Program). CRP devices will be replaced through the university’s replacement pipeline; departments are responsible for non‑CRP assets. Begin procurement or replacement planning now to avoid last-minute disruption.
• If you need more time
• Confirm ESU eligibility and enrollment options for your device and region, but treat ESU as a one-year stopgap. Coordinate with TechSquad if you need help enrolling or if your device is managed by the university’s IT systems.
• Get help early
• Open a TechSquad ticket or email TechSquad@marquette.edu; don’t wait until mid‑October. Marquette’s IT support pages and the TechSquad portal are the official first stop for troubleshooting and scheduling.

---

Institutional logistics and risk management — how universities balance speed with continuity​

Large organizations must balance rapid migration against disruption. The common pattern in higher education is:

• Early auditing and compatibility testing of critical software stacks.
• Staged rollouts (pilot groups, broader pilot rings, mass deployment).
• Hardware replacement waves for non-upgradeable devices using central replacement funds or departmental budgets.
• Contingency plans that include ESU enrollment for a limited subset of devices when replacing hardware is not immediately feasible.

Marquette’s prior upgrade windows (a campus update window in February and earlier staging activity) reflect that process. Even with staged deployment, anomalies and remediation tasks remain — which is why IT teams often continue to work with departments months after the initial upgrade wave to resolve edge cases. Where hospitals, research labs, or other specialized facilities use legacy software or instruments that link to old OS versions, departments typically create exception workflows that limit network exposure and document compensating controls.

---

Strengths and risks of Marquette’s current approach​

Strengths​

• Clear deadline-driven policy: Requiring Windows 11 by Microsoft’s EoS date aligns university posture with industry best practice and reduces long-term compliance and security exposure.
• Multiple upgrade paths: Using Microsoft Software Center for in-place upgrades and a Computer Replacement Program for ineligible hardware provides both convenience and procurement clarity.
• Centralized support: A staffed TechSquad and a public knowledge base help standardize procedures and reduce ad-hoc departmental divergence.

Risks and operational friction​

• Unverified inventory delta: The reported headcount of remaining Windows 10 machines (reported by Marquette as 304) should be treated as a snapshot; inventory reconciliation remains a risk area because assets move between departments and off-campus use complicates tracking. Independent public verification of that specific count was not available at the time of reporting, so departments should confirm counts with IT.
• Late replacements pressure: Departments responsible for non‑CRP devices face constrained procurement windows and potential budget stress. Last-minute purchasing amplifies cost and logistical risk.
• Niche application compatibility: Departments with specialized software may find some legacy apps untested on Windows 11; testing and vendor coordination remain necessary to avoid research or instructional disruption.

---

What to watch — late-breaking, policy and regional updates​

• Microsoft’s ESU terms have seen regulatory scrutiny and localized adjustments. Notably, the EEA gained an accommodation that eases consumer ESU access under certain conditions; that regulatory decision may affect how institutions manage internationally used devices or faculty travel. Confirm the ESU terms that apply to Marquette-owned devices, particularly for machines used by employees overseas or by visiting researchers.
• Watch for OEM firmware updates. Some devices require updated UEFI or firmware to support Secure Boot or TPM 2.0 properly; ensure that firmware updates are staged into the upgrade process to avoid bricked or non‑booting devices during mass upgrades. Firmware and driver readiness are as important as OS compatibility.
• Maintain documentation of exceptions. If a device must remain on Windows 10 temporarily due to specialized instrumentation or contractual constraints, document compensating controls (isolation, segmented VLAN, limited user access) and a concrete replacement timeline approved by IT security.

---

Quick FAQ for Marquette users (short answers)​

• Will my computer stop working on Oct. 14, 2025?
• No. Windows 10 will continue to run, but it will no longer receive routine security updates or vendor support unless enrolled in ESU. Running unpatched systems increases risk.
• What if my device can’t run Windows 11?
• Devices that don’t meet Windows 11 requirements must be replaced. CRP‑eligible units are centrally managed; non‑CRP replacements are the department’s responsibility. Consider ESU only as a short-term bridge.
• Will the upgrade delete my files?
• The in-place upgrade is designed to preserve files and installed applications, but you should back up important documents to OneDrive or another trusted location before upgrading.
• Who do I contact for help?
• Contact Marquette’s TechSquad via the self-service portal, by phone, or at TechSquad@marquette.edu for scheduling, troubleshooting, and replacement questions.

---

Conclusion​

The October 14, 2025 end-of-support milestone is now a firm operational reality. For Marquette, the pathway is clear: eligible machines must move to Windows 11, incompatible units must be replaced, and the limited ESU bridge is only temporary. The university’s reported remaining inventory of Windows 10 devices (the number published in the campus reminder) underscores the logistical final mile that many institutions face when a vendor lifecycle event coincides with academic calendars and constrained procurement cycles. Departments and individual faculty and staff should confirm device status immediately, back up data, and engage TechSquad early to avoid last-minute disruption. The transition is manageable if it’s treated as a project with clear milestones — but inactivity after the deadline carries real security, compliance, and operational risks.

---

---

Source: Marquette Today Reminder: Windows 10 support ends Oct. 14 | Marquette Today