Solved Generic volume shadowcopy driver keeps installing

[kado897]

Hi All,

I have an issue where the Generic volume shadowcopy driver installs at least once every time I do a windows backup. This suddenly started happening last saturday but I just noticed it yesterday. I thought that it must be connected with the install of Malwarebytes (paid version) on Friday but I put in a service request and they say not. Also it continues to happen after I have completely uninstalled MBAM.

I really have no idea what is causing this or whether it is a problem I should be worried about. Apart from this backups appear to be operating normally.

 

[kado897]

Is there no-one out there who has any thoughts on this?

 

[ModZilla]

Not much to the drivers thing...anyway...they're just base

Nothing to worry about really, its like your base drivers. They may not be working or not present at all and the OS still presses on regardless...you can try slipstreaming with nLite, it is a way to control what processes and services that usually all run in the background regardless; making you the MASTER of your OS as they say, instead of MS. Much of what MS intalls is a crap-shoot, furthermore if you have a proprietary copy of a WIN OS -then all kinds of other crap will be installed to run a propriatary BIOS version controlled by the release of the OS in conjunction with the vendor release requirements under windoze. Here is an example: when I run a check on my Sony using Belarc, I find all kinds of crud in there that I wouldn't know about otherwise. If for eg I go to ebay and buy a copy of a resto disk for the same OS but using a HP or a COMPAQ version of Win7, Belarc reports a whole different set of services that run in different installs. You can use BART PE to make the different OS installs accessible and use different slipstreams yourself to experiment...good luck with Windoze -- have fun with other OSes out there too--but, don't get stuck in a windoze rut!

 

[kado897]

Thanks ModZilla and welcome to Seven Forums. Its so long ago I can't remember what the fix was. I was having hardware problems around then maybe that was the cause. Anyway its fixed now. I should have marked this closed.