Is this just me? M$ AV not reacting to ExplorerPatcher being installed #4129
Replies: 5 comments 1 reply
-
do you have a third party antivirus program installed? did you add the exclusions to windows defender already? |
Beta Was this translation helpful? Give feedback.
-
As I said, it was a clean install of 24H2 using Rufus with all options taken except the 1st one which disables stuff. First thing I did was to disable the screen recording spyware m$ have graciously given us. The second thing was running update and after getting everything available I installed explorerpatcher. Then I ran the scan. The AV is windows own - no 3rd party. No exclusions added - the scans where the first things I did after installing explorerpatcher so that I could add the exclusions but the antimalware/defender didn't flag up anything in regards to explorerpatcher. |
Beta Was this translation helpful? Give feedback.
-
can you show a screen shot of that 1st option in rufus that disables stuff? and when you disabled the spyware that MS included, how did you disable them? Was it through settings? you could add the exclusions to windows defender without EP being installed. It doesn't require the files exist in order to add them to the exclusion list. |
Beta Was this translation helpful? Give feedback.
-
The first option I disabled. To disable the spyware that records everything you do in screen shots, see below: Dism /Online /Disable-Feature /Featurename:Recall This command outputs the following if the Recall spyware is installed: Deployment Image Servicing and Management tool Image Version: 10.0.26100.2161 Disabling feature(s) As far as pre-adding exclusions prior to installing EP, I didn't do that because I didn't know you could/how to do it. EDIT: I have found that this maybe temporary - as I did this earlier today. After a forced reboot by software installation and writing this post, I decided to run the command again - it completed again - hence my assumption that it maybe a temporary removal and reinstall after a reboot.. But I am unsure of this. |
Beta Was this translation helpful? Give feedback.
-
After doing a little bit of research I have found that this is a false positive. Unless your machine has Copilot+ installed and has Neural Process chips installed this doesn't apply. Basically any PC bought after November 2024 (I stand to be corrected) have these and will install Recall and Copilot+. So running the above DISM command is pointless because it'll do absolutely nothing. |
Beta Was this translation helpful? Give feedback.
-
I recently upgrade (for my sins) to Win 11 24H2 with a clean install and NOT using my micro$oft account but a local one (facility provided by Rufus USB installer as m$ in their wisdom have stopped people creating local accounts!)....
Anyway.. after installing I expected the anti-malware to flag up the program as malware or whatever - but on a quick scan, it didn't.
I thought this odd so I ran a full scan and the same result occurred.
Have m$ rethought their (stupid) way of dealing with explorerpatcher or has there been a technological break through that allows us (full?) access to the bits that need to be changed to allow the program to work?
Beta Was this translation helpful? Give feedback.
All reactions