[BUG] - File Explorer error: Microsoft Visual C++ Runtime Library

[astarivi]

Before continuing...

• I agree to follow Atlas' Code of Conduct
• I have searched our issue tracker to verify that the issue hasn't been reported already
• I have searched the Atlas documentation beforehand for a solution
• I am on the latest version of Atlas, and didn't do an unsupported upgrade

Description

When I open a new File Explorer window, an error window may appear instead: "Microsoft Visual C++ Runtime Library" with no content:

It also seems to trigger when interacting with an existing File Explorer window, where the same error window will appear and may close on its own, unlike the error windows created from opening a new file explorer window; they always have to be closed by the user.

No other system behaviors are affected. Other than being a constant nuisance, it doesn't affect system stability.

Steps to reproduce

1. Clean install Windows 11 Pro 24H2 from a known-good ISO (checksum checked)
2. Disable Windows Update driver installs
3. Install all available Windows updates (except Preview)
4. Update all Microsoft Store apps
5. Install the Playbook (Microsoft Edge & Core Isolation active)
6. Restart system
7. Open 4 file explorer windows

Expected behavior

No errors when opening or using the file explorer.

Actual behavior

About 1 out of the 4 file explorer windows will be a "Microsoft Visual C++ Runtime Library" error window instead.

Atlas Version

Atlas v0.4.1 for Windows 11 24H2

Desktop information

CPU: i5 10400
Chipset: B560
GPU(s): RX 7800 XT, RX 6600M and UHD 630
RAM: 64 GB DDR4 3200MHz
Storage: Installed on 256 GB SSD (OEM Samsung NVME PM9A1). About 12 TB of storage available system wide through multiple hard drives, all Western Digital brand.

Additional content

Installing drivers and reinstalling Visual C++ Runtimes didn't help.

[notriyazkhan]

With my setup, I have been able to trigger the error window every time by opening File Explorer from my taskbar. Opening multiple instances from the taskbar creates a new error window each time.

Opening File Explorer from the pinned Start Menu does not seem to reproduce this issue.

Could it be related to https://github.com/orgs/Atlas-OS/discussions/1436 ?

Windows 11 Version 24H2. 10.0.26100 Build 26100. Atlas Playbook v0.4.1. Fresh install 2 days ago.

[TheyCreeper]

I don't have this issue personally, and I haven't heard more than you three have it, but since it's not a single person having the issue I'll keep it in mind if it ever comes up more.

[unclebearr]

Nilesoft Shell caused the issue for me, after uninstalling it the error is gone. Are you using this software? @astarivi

[astarivi]

No @unclebearr , system was stock at the time.

I have been trying to track the source of the issue to no avail. ProcMon doesn't seem to register anything related, and there's no irregular event anywhere in any of the Windows analytics/logging facilities.

Nevertheless, I have a feeling this issue might be related to bundled explorer.exe extensions (like Copilot, OneDrive or Office 365) and/or context menu items.