Windows 10: Backups, sys restore, chkdsk /scan do no work; VSS error 12289

Hello,

I have been struggling with this problem for about 2 years, ever since I upgraded Win 7 to Win 10. I was using Macrium Reflect for backups on Win 7 without any problems. After the upgrade it stopped working. Also, I can't create System restore point. I'm getting the following errors:

VSS error 12289
System Restore Error 8211

Also, chkdsk /scan doesn't work (I can do offline scan, but it doesn't find any errors).

I was also getting CAPI2 513, which I was able to resolve following the instructions given here:
https://answers.microsoft.com/en-us/...1bda112?page=8
However, solving CAPI2 513 did not help me with backup/restore problems. *

Any help will be greatly appreciated!

Here are the logs of the errors:

__________________________________________________
When I try to do chkdsk scan I get this message:

Checking file system on C: The shadow copy provider had an error. Check the System and Application event logs for more information. A snapshot error occured while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.
____________________________________________________________________________


_________________
VSS Error 12289:

Log Name: Application
Source: VSS
Date: 3/11/2017 2:12:37 PM
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Asus-Desktop
Description:
Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\,0x80000000,0x00000003,...). hr = 0x80070001, Incorrect function.
.

Operation:
Processing PreFinalCommitSnapshots

Context:
Execution Context: System Provider
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12289</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-11T19:12:37.907652700Z" />
<EventRecordID>31001</EventRecordID>
<Channel>Application</Channel>
<Computer>Asus-Desktop</Computer>
<Security />
</System>
<EventData>
<Data>CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\,0x80000000,0x00000003,...)</Data>
<Data>0x80070001, Incorrect function.
</Data>
<Data>

Operation:
Processing PreFinalCommitSnapshots

Context:
Execution Context: System Provider</Data>
<Binary>2D20436F64653A20494E434943484C4830303030303237302D2043616C6C3A2053505251534E5043303030303033 30382D205049443A202030303030353235322D205449443A202030303030393232302D20434D443A2020433A5C57494E444F 57535C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E542041 5554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
__________


____________________________
System Restore Error 8211
Log Name: Application
Source: System Restore
Date: 3/10/2017 11:03:55 PM
Event ID: 8211
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Asus-Desktop
Description:
The scheduled restore point could not be created. Additional information: (0x80042306).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="System Restore" />
<EventID Qualifiers="0">8211</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-11T04:03:55.484274000Z" />
<EventRecordID>30585</EventRecordID>
<Channel>Application</Channel>
<Computer>Asus-Desktop</Computer>
<Security />
</System>
<EventData>
<Data>0x80042306</Data>
<Binary>00000000000000009F01000000000000574C29CE5843BE27E26C1C000000000000000000</Binary>
</EventData>
</Event>
_________

:)

 

VSS Error 12289; Backups don't work; Chkdsk doesn't work

I posted it in TechNet.

Thank you,

 

VSS Error 12289; Backups don't work; Chkdsk doesn't work

Hi,

For better assistance, we recommend you post your query in Technet by clicking this link.

Thank you.

 

It rather sounds like you have a problem with VSS.

Macrium offers a possible VSS repair, and see
Macrium Reflect Backup Failures
Cannot make system image - VSS error 12289

However, if I recall, in some cases the solution is an in-place upgrade repair install which keeps all programs and data and most settings.

If you take a little time to search the forum for the error messages you've usefully reported, you will find more threads similar to the above, where your problem has, I think, been discussed a number of times, where you may find sthg helpful.

 

I did search this forum and did not found a solution that would help my problem. I did VSS repair with Macrium and that did not help. Also, their tech support was not able to provide a solution. Since I cannot use Macrium I have uninstalled, but I'm still getting the same error with creating system restore point. I have tried many things, including:
chkdsk c: /f — no errors
sfc /scannow — no errors
vssadmin list writers — no errors

I have not tried in-place upgrade repair. Let's see if it will help.

Thanks,

 

Yep- there's at least one extensive thread where Macrium's repair didn't help and an in-place upgrade repair install did.

 

Use option in task scheduler to create a macrium boot option. Then when you restart pc, it loads macrium into winpe environment, and then you will bypass vss issue and can backup with no issues assuming vss is the issue.

 

Yes, I am aware of this, and I did it for some time. It's a workaround that doesn't solve the problem, but it does allow to clone or image. I'm looking to fix the errors. I still didn't get to do the repair install. I'm on it.

Thanks

 

It did not work. I tried repair install of Windows 10 with Media Creation Tool. Everything starts nicely, installation files get downloaded, updates get downloaded, and then it restarts but it doesn't continue the process. It just restarts immediately after passing BIOS boot screen.
Does anybody know if this process should work if motherboard has a BIOS chipset? The instructions do say to disable Secure Boot in your UEFI firmware settings. But my motherboard doesn't have UEFI. It has a legacy BIOS mode.

Thanks!