New
#11
Make the volume shadow copy service start type to disabled and restart your computer.
Make the volume shadow copy service start type to disabled and restart your computer.
OK, will do. Have to wait until later as I can't restart now, but I'll try it and let you know.
What does that service do? Will I be losing out in any way? I did a search, but the results mostly seemed to assume you know what volume copying is, which I don't! I use the Windows File History / Backup feature. Will that be affected?
Thanks again.
Hi, I wasn't planning on doing anything with it, I just wondered what it was and why it was using so much CPU. The name is a bit vague, could be anything!
Thanks
zinou - been a few hours since I restarted, and so far everything is working great. Looks like you might have hit the nail on the head.
Thanks again. I'll see how it goes over the next few days :)
There some applications that uses shadow copy, like backup applications, Hyper-v ...
To delete orphaned Volume Shadow Copies, you can use this command "vssadmin delete shadows /all".
Hi zinou,
I can't run that command as I disabled VSS! I'd need to re-enable it, run the command and then disable it again.
However, looks like if I disable VSS, then restore points won't be created. Is that right? How about windows backup, does that require VSS? Don't want to lose either of those.
You say that VSS is used by Hyper-V. I only started seeing these problems after I installed Hyper-V. I wonder if VSS on its own wasn't the problem, it was Hyper-V's usage of it that caused the problem. If so, enabling VSS without re-installing Hyper-V might be OK.
Any thoughts? Thanks again
Hi
Enable vss then run the command to remove orphane Volumes. It may solve your problem . Then let the service startup type manual and see if the problem will occur.
Thanks, I've done that. Let's see what happens now :)
Thanks again for all the help.