Does anyone know what this is.
- Thread starter carlos726811
- Start date
TonyCarter
VALUED CONTRIBUTOR
It looks like the system (as both apps are Windows system components) are trying to access a protected area on your HDD (D:\).
One of them looks to be part of the Window’s system restore function (SrTasks.exe), so may have been trying to make a restore point before the update…and the second (msiexec.exe) is the Windows component that runs the installations. Both of which are normal processes.
Don’t know why they’d come up as errors though (even if only ‘low” risk ones)…but both of those should have access to that sort of folder anyway, so I’d be quite happy to allow them…although I don’t think I’ve got Controlled Folder Access enabled at all on my PC.
One of them looks to be part of the Window’s system restore function (SrTasks.exe), so may have been trying to make a restore point before the update…and the second (msiexec.exe) is the Windows component that runs the installations. Both of which are normal processes.
Don’t know why they’d come up as errors though (even if only ‘low” risk ones)…but both of those should have access to that sort of folder anyway, so I’d be quite happy to allow them…although I don’t think I’ve got Controlled Folder Access enabled at all on my PC.
carlos726811
Bright Spark
Yh. No idea how it got enabled. last time i had a virus. I did a full reset and clean install. never touched anything.. I updated Elgato stream deck last month. no issues. Updated last night and then that showed up. So no idea, what happened
I remember switching it on a while back and getting similar warnings etc. They were all false positives. I looked into configuring it but it was far too much hassle to be worth my time in honesty. I just switched it off and forgot all about it.
It is a great idea in principle, if it worked as per the description without calling out Windows own signed processes then I think it would be a winner.
The update is likely causing the issue as it's expecting a particular version of the file/process to be running, but it's an updated version. Likely down to it requiring an update itself. This is just a guess though as I genuinely don't know the ins and outs of how it operates.
It is a great idea in principle, if it worked as per the description without calling out Windows own signed processes then I think it would be a winner.
The update is likely causing the issue as it's expecting a particular version of the file/process to be running, but it's an updated version. Likely down to it requiring an update itself. This is just a guess though as I genuinely don't know the ins and outs of how it operates.
SpyderTracks
We love you Ukraine
It’s a bug, needs to be flagged to microsoft