Post reply

Name
Email
Subject
Message icon

Other options

Return to this topic
Don't use smileys

Verification:

Please leave this box empty:

Shortcuts: ALT+S post or ALT+P preview

Topic summary

Posted by Bill Maxwell

- October 21, 2024, 07:21:38

I have a NUC with an i7 CPU and updated to 24H2. After the update I disabled recall and it had no effect on File Explorer.
I used the DISM command: Open Terminal (Admin) - dism /online /disable-feature /featurename:recall

It stayed disable even after updates and restarts.
To check status: dism /online /get-featureinfo /featurename:recall

Posted by snn47

- October 15, 2024, 11:22:19

How about alternatives to the µ$-explorer, e.g. Q-Dir or 7zTm, are they also affected or do they rely on their own modules?

Posted by julian.vdm

- October 12, 2024, 06:04:42

Quote from: Julian Xhokaxhiu on October 11, 2024, 23:19:03There's a typo in the subtitle: 22H4 -> 24H2

Thanks for pointing that out. I've corrected it. Strange world we live in, that a year can have four halves...

Posted by Julian Xhokaxhiu

- October 11, 2024, 23:19:03

There's a typo in the subtitle: 22H4 -> 24H2

Posted by Redaktion

- October 11, 2024, 18:43:15

It looks like Microsoft's Recall push is back in full swing with Windows 22H4. A recent technical analysis revealed that disabling Recall also disables the modern File Explorer interface. Currently, it is unclear whether this is a bug or intended behaviour, but it's indicative of Microsoft's AI-encrusted future.

https://www.notebookcheck.net/Removing-Windows-Recall-breaks-File-Explorer-in-latest-24H2-update.899991.0.html