88GB sounds like a lot but might not be. How big is an image backup when completed? Go ahead with the in-place upgrade, it won't hurt but if you have a system writer that is bad you could fix it SFC /SCANNOW.
You could run vssadmin list writers to see what status all installed writers are on your machine. Any showing as having errors?
Bertie11 said in #1
Oh yes, I did a chkdsk c: /f and that went OK, and I did an sfc /scannow now which found nothing.
Exactly my point, nothing found so what is the magic in an in-place upgrade then? Better to troubleshoot VSS first and see if any errors show. Most of the time VSS issues can be fixed by a Restart of the machine. In Windows 10 I suggest a hard shutdown (admin command prompt shutdown /s) followed by cold start power on.
1. That fixed it in that very long thread I quoted where major effort was made, otherwise unsuccessfully. = Evidence QED.
2. An in-place upgrade repair is not the same thing as SFC /Scannow.
That said, of course if there is a specific fix that solves this, so much the better.
We've tried one- any more please?
Otherwise., sorry, you've missed the point.
The user could try this:
In Windows 10 Search box type Services and look for a gear icon with a Desktop app reference.
Click on that entry to open the Services app.
Scroll through the list and locate the following services. It will be necessary to restart each one individually.
COM+ Event System
COM+ System Application
Microsoft Software Shadow Copy Provider
Volume Shadow Copy
To restart the COM+ Event System left mouse click on the entry in the Services window to select it then, right click on that entry and select Restart.
To restart the remaining services is a bit different as these services should all be set to start manually. The procedure here is to proceed as described above except for these services you will select Start from the right click menu then after the service starts right click again and select Stop.
If you you encounter any of the last 3 services that are already running or are paused Stop the service first, then start the service and after it has started again then stop that service again.
This should fix most VSS writer errors and solve 90%+ of such issues where VSS writers are at issue.
That indicates that the Volume Shadow copy Service is in a hung state and unable to run this the error. Restart the services outlined in my post number 25 and see if that solves the issue.
I would suggest you open an elevated command prompt and type this in the prompt before pressing enter.
Then you'd be able to see the results.Code:vssadmin list writers
You might also try
But I'm not sure whether or not they'd be helpfulCode:vssadmin list shadowstorage vssadmin list shadows vssadmin list providers
That's better, thanks. All I get is Microsoft Software Shadow Copy Provider, but like I've been saying in the thread it is hidden in the registry and I cannot see a way to make it visible.
Quote