This is on our office network, it appears to be happening on all of the computers, but one of them is used as a server for our in-office software, "Avimark."
It appears on Wednesdays every week the maintenance will continually try to run, and slow the computer down to a halt, and stops once the computer is in use again, perpetually trying to run the service all day and continually making everything not work over the network.
I've run sfc /scannow and it gave a few errors with amd files, one with something else I honestly didn't write down. I have the CBS logs for whatever was happening.
LONG STORY SHORT: I found a couple fixes for what seemed to be the problem, tried sfcfix and some of the steps in this thread here. I ran sfcfix again after and got the attached results.
Not sure if there's something I can try along the same lines of adding registry codes as the above thread, but it looks like a different line than what that person was dealing with.
I also saw another post on here suggesting there are issues similar to this that are not fixable currently, and Microsoft is working on something to fix it now.
If anyone can help, it'd be greatly appreciated!
It appears on Wednesdays every week the maintenance will continually try to run, and slow the computer down to a halt, and stops once the computer is in use again, perpetually trying to run the service all day and continually making everything not work over the network.
I've run sfc /scannow and it gave a few errors with amd files, one with something else I honestly didn't write down. I have the CBS logs for whatever was happening.
LONG STORY SHORT: I found a couple fixes for what seemed to be the problem, tried sfcfix and some of the steps in this thread here. I ran sfcfix again after and got the attached results.
Not sure if there's something I can try along the same lines of adding registry codes as the above thread, but it looks like a different line than what that person was dealing with.
I also saw another post on here suggesting there are issues similar to this that are not fixable currently, and Microsoft is working on something to fix it now.
If anyone can help, it'd be greatly appreciated!