Microsoft is preparing to remove the 3D Viewer application from the Microsoft Store on July 1, 2026, according to a newly surfaced community advisory. The move will cut off easy access to the built-in tool that millions of Windows users have relied on to open and inspect 3D models without installing specialized software. While the app itself may continue to function on devices where it is already installed, its absence from the Store means fresh Windows installs, resets, and new devices will ship without it—forcing organizations to find alternatives or face broken workflows.

For enterprises, the deadline is particularly urgent. IT departments must inventory every machine, identify which business processes still depend on 3D Viewer, and decide on replacements long before the removal date. Failing to plan could leave employees unable to view product mockups, engineering files, or 3D scans precisely when they’re needed most.

What’s actually changing on July 1, 2026

Microsoft has not published an official deprecation notice for 3D Viewer on its service-health dashboard or admin center as of this writing. But the community report, which surfaced on WindowsForum.com on Thursday, aligns with the company’s broader retreat from consumer 3D and mixed-reality software that began with the sunset of Paint 3D in late 2024.

Once the deadline passes, the change will be straightforward: the 3D Viewer app will no longer appear in searches inside the Microsoft Store, and its product page will return an error or state that it is “no longer available.” Users who already have the app installed will retain it, but they won’t receive updates—security or otherwise. More critically, any fresh Windows deployment—whether from a clean installation, an in‑place upgrade, a wipe‑and‑load refresh, or a replacement device—will come without 3D Viewer. System administrators who rely on images or provisioning packages that assume the app is present will need to adjust their deployment scripts.

The advisory does not mention whether Microsoft will block sideloading of the app’s .appx package, but the company’s recent practices with other deprecated Store apps suggest the package might be pulled entirely from the Microsoft Store’s content delivery networks, making it hard to obtain through official channels.

What it means for you—by audience

For home users and hobbyists

If you occasionally open a .glb or .stl file that arrives in an email, you’ll be forced to find another tool. Many casual users turned to 3D Viewer because it was preinstalled and worked without effort. After July 1, 2026, you’ll need to reach for a third‑party viewer, such as Autodesk’s free Online Viewer, Blender (which is overkill for simple previews), or a browser‑based option like Babylon.js Sandbox. The loss is an annoyance, not a crisis—but it’s one more piece of Windows’ once‑rich built‑in utility set stripped away.

For IT administrators

Here’s where the pain concentrates. Over the years, 3D Viewer found its way into line‑of‑business tasks: a procurement manager reviewing a 3D scan of a warehouse layout, a technician examining a CAD model embedded in a SharePoint library, or a training module that launched a .fbx file directly. Because the app was always there, nobody documented its role in these processes.

Now, admins need to inventory every endpoint. Microsoft Endpoint Manager (Intune) can query installed store apps; a simple PowerShell script using Get-AppxPackage can dump the presence of Microsoft.Microsoft3DViewer (the package family name) across a fleet. The results should be cross‑referenced with any known workflows that involve 3D files. For each workflow, assign an owner and a migration decision: switch to a supported Store app, move to a web‑based viewer, or explicitly accept the risk of keeping the app beyond its end‑of‑life.

Crucially, don’t wait for the July 2026 cutoff. Windows device recovery cycles—when laptops are reimaged or replaced—could strip 3D Viewer months earlier if you refresh machines on a schedule. Planning must start now.

For developers and ISVs

If your application or web service relies on 3D Viewer as a handler for 3D file types, you have a deprecation dependency. The microsoft-edge:? protocol or shell‑execute commands that open 3D files will break on systems that don’t have the app. You should plan to bundle a lightweight viewer component, steer users to a PWA‑based solution, or embed a rendering library directly. The Babylon.js sandbox (https://sandbox.babylonjs.com) is one ready‑made web alternative that handles many common formats, but you may need something more tailored.

How we got here: Microsoft’s long goodbye to 3D

3D Viewer first appeared in Windows 10 as “Mixed Reality Viewer,” part of a lofty vision that tied together HoloLens, Windows Mixed Reality headsets, and 3D content. Users could paint in 3D with Paint 3D and then view or pose their creations in the viewer. But the mixed‑reality ecosystem never reached critical mass. In 2024, Microsoft stopped accepting new Mixed Reality apps to the Store and deprecated the Windows Mixed Reality platform. Paint 3D was removed from the Store in November 2024, and its inclusion in clean Windows installs ended with Windows 11, version 23H2.

3D Viewer, surprisingly, survived those earlier cuts. It remained available in the Store, though Microsoft stopped preinstalling it on new Windows 11 devices after version 22H2. The July 2026 removal date marks the final stage: pulling the app from the Store entirely.

No public statement from Microsoft explains why it waited until 2026. One plausible reading is that the company wanted to give businesses one last migration cycle—two full years from the Paint 3D removal—to find alternatives. Another possibility is contractual: some OEM or enterprise agreements might have guaranteed Store availability through mid‑2026. Whatever the reason, the clock is now ticking.

What to do now: a 3‑step preparedness plan

1. Inventory and classify

Run a fleet‑wide inventory of 3D Viewer installations. Use Intune custom compliance policies or a simple PowerShell script pushed via RMM tools. The app’s package name is Microsoft.Microsoft3DViewer. Any machine that reports it installed should be flagged.

Then, interview department heads and power users: what 3D files are they opening regularly, and how? Map each usage to a business process. Classify each as critical, low‑impact, or obsolete.

2. Test alternatives before the deadline

For every critical workflow, pick a replacement and pilot it with a subset of users. Consider these four paths:

  • Web‑based viewers – The Babylon.js Sandbox runs in any modern browser and supports glTF, GLB, OBJ, STL, and more. It requires no installation and can be set as the default opener for 3D file types via a simple script. Microsoft’s own 3D Viewer for Microsoft Teams (a web control) may also be an option for files stored in Teams.
  • Third‑party Store apps – Several free 3D viewers exist in the Microsoft Store, such as “3D Viewer for Windows” by AMC Bridge or “F3D.” Vet them for security and long‑term support before deployment.
  • Desktop applications – Applications like Autodesk Viewer (online), Blender, or MeshLab provide rich functionality but are heavier. Bundle them only where needed.
  • Keep a local copy – As a stopgap, IT can extract the .appx package from an existing installation and deploy it via sideloading. Be aware that this bypasses update channels and may violate Microsoft’s terms if the app is no longer licensed for distribution. Seek legal guidance.

Run side‑by‑side tests for a few weeks. Ensure the replacement can handle file size limits, network paths, and any proprietary metadata that your workflows depend on.

3. Update deployment images and scripts

If you use Windows Autopilot, custom .wim images, or task sequences in Configuration Manager, strip out any references to 3D Viewer now. Replace them with the chosen alternative. For immediate relief, you can also push a “remove 3D Viewer” script to all managed devices after July 1, 2026, to avoid users clicking on a dead tile—but this is lower priority than ensuring the new tool is already in place.

Set a calendar reminder for May 2026 to run a final audit. No new machines should leave your build bench with 3D Viewer after the removal date.

Outlook: Microsoft’s 3D retreat is nearly complete

The 3D Viewer removal is part of a larger pattern. Microsoft has been steadily pruning niche features—WordPad, Cortana, Steps Recorder, and most recently the Tips app—to slim Windows and focus on core productivity. Enterprises that still carry decade‑old dependencies learned from the WordPad removal that early action matters. The same lesson applies here.

Watch for one more twist: the community advisory warns that enterprise Windows 10 LTSC and certain IoT editions might retain the app longer, but no assurance has been given. If you depend on those channels, press your Microsoft account team for a written statement of support.

Also keep an eye on the Microsoft Store on July 2, 2026. Sometimes these removals are delayed or replaced with a notice that directs users to a new tool. But betting on a reprieve is not a strategy.

The message from IT peers on WindowsForum is blunt: “Enterprises should inventory Microsoft 3D Viewer, classify the workflows that still depend on it, and make each workflow owner decide before reimage, reset, replacement, or wipe‑and‑load cycles expose.” It’s sound advice that deserves a meeting invite—this week, not next quarter.