New PDF Viewer Enabled by Default in Microsoft Edge Starting October 2025

Updated May 18, 2026: We have updated the opt-out timeline. Thank you for your patience.  Introduction Starting in October 2025, Microsoft Edge version 141 will introduce the Adobe-powered PDF viewer as the default experience for enterprise users on Windows. This change enhances performance, accessibility, and compatibility, and introduces exclusive enterprise features. It follows our earlier public announcement and aligns with Roadmap ID 489231 and MC post MC1072406. General Availability: Migration will occur on a phased rollout. Rollout will begin October 2025 and will complete March 2026.  How this affects your organization: Who is affected: All enterprise users on Windows using Microsoft Edge. What will happen: The Adobe-powered PDF viewer will replace the legacy viewer as the default experience. User interface and controls will remain unchanged. The new viewer offers improved performance, accessibility, compatibility, and exclusive enterprise features. Admins can manage the experience using two policies: NewPDFReaderEnabled: Controls the default viewer in Edge for Windows.  NewPDFReaderWebView2List: Controls viewer behavior in WebView2 apps.  Policy behavior: Policy State Before Enablement by Default After Enablement by Default Default Old PDF Viewer New PDF Viewer Enabled New PDF Viewer New PDF Viewer Disabled Old PDF Viewer Old PDF Viewer What you can do to prepare: No action is required if your organization is ready to adopt the new viewer. If you wish to manage the experience: Enable the new viewer early using the NewPDFReaderEnabled policy. Opt-out by disabling the same policy. Opt-out will be supported until September 2026, at which time the policy will be deprecated and any remaining organizations will be moved to the new viewer.  Review and update internal documentation if needed. Communicate this change to helpdesk or support teams. Learn more: Microsoft Edge and Adobe partner to improve the PDF experience. For support, contact your Microsoft CSAM or CSS representative. Compliance considerations: No compliance considerations identified, review as appropriate for your organization.