New Update Typical Microsoft! Disabling Windows Recall is Breaking File Explorer

[lokamoka820]

Earlier this year, we were caught off-guard by Microsoft when they came up with a creepy move to spy on users with a new AI-powered feature called Recall.

When active, the feature takes snapshots of the screen a user is working on, to then catalog it, and serve for later fetching as a scrollable timeline. It was supposed to be disabled by default, but, it appears, Microsoft has gone back to enabling it by default.

The 24H2 release installs Recall on all PCs, not just Copilot+ PCs. But, that's not all. Recall also breaks an important Windows feature if someone tries to remove it.

Disabling Recall Breaks Important Functionality​

Source: InvisibleRasta

Even though there is now a way to uninstall Recall from Windows 11 PCs, Microsoft doesn't seem to have any plans to make the process an easy one.

Spotted by Chris Titus on a project he works on, a person posted their plight on the GitHub repo of Windows Utility (winutil). They explained how a Windows Pro 24H2 ISO created using MicroWin was downgrading the File Explorer to an older one.

If you didn't know, Windows Utility is a handy tool that helps people get rid of the unnecessary bloatware and features that a Windows release usually ships with. Similarly, MicroWin is used to create custom Windows images with tweaks according to one's preferences.

After some back and forth between the original poster and some contributors, it was found that Recall and Copilot were required to run the new File Explorer. Before you ask, the new one is the one that provides multi-tab functionality, and Copilot is an important component of Recall.

This was not the case with the 23H2 release, as Chris points out in his video. Microsoft has made this change in a very sneaky manner; the release blog for 24H2 (linked above) doesn't mention a single word about this.



To address the issue with File Explorer when using winutil or MicroWin, a contributor, CodingWonders, made some fixes, where the Recall components were kept intact and were disabled only after a user logged in.

But, for other users, this is something to be concerned about. If Microsoft is keeping Recall tied to an essential service like File Explorer, that too without talking about it anywhere, what else are they baking Recall into?

Typical Microsoft! Disabling Windows Recall is Breaking File Explorer

This is what some users have spotted and I am not surprised.

news.itsfoss.com

 

[Bot]

This is indeed concerning. Microsoft should be more transparent about the integration of features like Recall in essential services. For those who value privacy, the ability to disable such features without breaking other functionalities is crucial.

 

[Sorrento]

I tend to use a third party explorer function anyway which is Free Commander but from what I can see things look as they did before 24H2 - Unless I'm missing something??

 

[lokamoka820]

By the way, I'm still on 23H2 and my file explorer crash when I open tabs on it, I removed Copilot and some other Microsoft built it apps.

 

[bazang]

Microsoft removed Recall from 24H2, and it is no longer present on 23H2. It made an official announcement that it was permanently removing it. The Recall removal was done via Windows Updates. Since June 2024 Microsoft has made it possible for users to remove Recall via:

appwiz.cpl > Remove Windows Features > Recall

 

[SpiderWeb]

I think Recall was so deeply embedded into their plans, they did not foresee that people want to turn it off and now they have to untangle the mess. Ultimately Microsoft is to blame. But, it's also a big challenge for Microsoft to test every possible Windows configuration for bugs. There will be things they just could not have accounted for.

 

[lokamoka820]

What is the best alternative to file explorer?