This is an update to what I previously posted here. (I’m a Mac user, but I write such things out of concern for friends still suffering the handicap known as Windows.)
Microsoft has recently gotten downright mean, and certainly unethical. The latest “popup” windows about upgrading now interpret clicking the “X” as “upgrade” instead of “close” — both the “X” and the “OK” button function the same as choosing “upgrade.”
According to a WND article here:
To avoid the forced “upgrade,” a user has to go into the fine print. Inside a logo box in the ad is a scheduled date for a mandatory upgrade. The user must look in the tiny type just below that line and find where it says “here” and click on that to avoid the upgrade.
Read more on their site.
Many of you are frustrated at Micro$oft forcing Windows 10 on you against your will. This is no exaggeration. They are silently downloading 3 gigabytes of Windows 10 installer files without consent (which is practically theft since it robs you of bandwidth and storage space you pay for), and they are insisting (via pop-ups that leave you no way out) that people with Windows 7, Windows 8.1, etc, upgrade to Windows 10. This new OS drags many PCs to a crawl. If you were forced into an “upgrade,” there is a way to downgrade, going back to your earlier version, but you must do so within 30 days of the upgrade. Settings –> Restore –> (Google is your friend here). There is also a freeware program that will delete the unwanted Windows 10 installer files and stop the merciless pop-ups. Again, Google is your friend. I am not a Windows user (I use Mac), but again, I am your friend. The freeware I installed on a church computer to stop the madness, is called GWX Control Panel from Ultimate Outsider (link below). http://ultimateoutsider.com/downloads/
So, I was trying to use to use VMWare Fusion 3.1.2 to import my existing Windows XP Pro SP3 machine over as a virtual machine for use on my Macbook Pro (OS X 10.6.7). I kept getting a dead stop with this error: “unable to create a VSS snapshot of the source volume(s).” It was usually accompanied with an error code, which at one point I copied as: “2147754767 (0x8004230F).” After hours of searching the Web and trying all kinds of things, I finally found this that worked:
Just in case the above link is dead by the time you read this, below is a copy of the post by Ztruker. (Kudos to Ztruker, by the way!) When I checked the GUID in my system, it did not match. When I edited it in my Regedit app on the XP unit, the MS Software Shadow Copy Provider Service finally became functional. I manually started it, and then the VMWare Fusion Migration Agent finally was able to do its job. Thanks, Ztruker, whoever you are!
Definitely not a space problem then.
More searching found this. A remote possibility but worth taking a few minutes to look at:
This may not be applicable to your situation, however might be worth a look. I have had similar problems with VSS on XP machines that turned out to be caused by the MS Software Shadow Copy Provider Service (SwPrv). You should be able to manually start and stop both VSS and SwPrv (net start vss) (net start SwPrv). If VSS manually starts OK, but you get an error when trying to start SwPrV, then you could have a permissions problem with it (account used to start it? should be system account), or a registry error with the services command line. I have run across several situations with XP machines where the command line for the SwPrv service is incorrect.
Possible Solution (these instructions are for XP):
Open Control Panel, Administrative Tools, COMPONENT Services
Inside the Console Root folder, goto COMPONENT Services -> Computers -> My Computer -> Com+ Applications.
On the top toolbar, click on View, Status (or click the Status button on the toolbar).
You will see all Com+ applications and their statuses including the Application ID and the PID (if currently running).
Make a note of the Application ID for the MS Software Shadow Copy Provider entry.
Next check the command line used for the SwPrv service. Navigate back to the top root folder. Inside the Console Root folder, goto Services (local). Note, you can also get here from Control Panel, Administrative Tools, Services.
Find the MS Software Shadow Copy Provider Service and double click on it. Notice the Path to Executable field. It will have an entry similar to the following:
Check to make sure that the GUID inside the curly brackets is the exact same as what you found in the Application ID in the first step. If it isn’t, then this is what is preventing the service from starting.
To correct, open regedit and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSwPrv
Double click on the ImagePath value and make the necessary correction.
It is obviously a good idea to export a backup reg file of the above key in case you make a mistake or need to restore the original settings.
This is from Post #15 here: http://www.computing.net/answers/windows-2…rror-/5105.html
I checked this on my XP system and the GUID matched.