Windows 10 1709 failed restore point 0xc0000043

hexaae · 21 Oct 2017

Since I upgraded to Windows 10 1709 16299.19 from 1703 every new system restore point recovery fails with error:

System restore did not complete successfully. Your computer's system files and settings were not changed.

Details
System restore failed to restore a file. This could happen if an anti-virus program is protecting the file. If the failure persists switch off your anti-virus and retry the restore, or perform system restore from Windows Recovery Environment. System restore failed in delayed delete operation for the file \ ?? \ Volume{9d282722-a6f7-4867-bef2-dc00dcb23c58} \ WINDOWS \ bootstat.dat. (0xc0000043)

Just for testing I manually created some new restore points with 1709 and noticed it always fails on restore after reboot popping up this requester (ITA)

I don't have 3rd party antivirus installed or similar tools that might lock that file, I use just Defender + Malwarebytes Pro (disabled auto-start at every Windows login). Never had issues with Restore points before.
Since C:\Windows\bootstat.dat is a legit system boot status file (contains infos about latest successful boot etc.) generated at every boot I wonder if it can be a bug of the new OS.

IsaacFL · 22 Oct 2017

Were you booting to WinPE on recovery media?

Not sure if related your issue, but I just found out that Win10 1607, is the most recent WinPE version that Reflect currently supports.

In my case that means Storage Spaces aren't accessible now from WinPE. I guess there must have been a change to Storage Spaces in the 1709 update. Have not been able to find out what it was.

So something in the update to 1709 is incompatible with 1607 now.

hexaae · 23 Oct 2017

IsaacFL said:

Were you booting to WinPE on recovery media?

No, a notebook PC. Upgraded from 1703 to 1709.

axe0 · 23 Oct 2017

The restore fails, because whatever is accessing bootstat.dat doesn't have the right 'share access flags'.

Have you run sfc?

hexaae · 23 Oct 2017

Yes, SFC /scannow reports no integrity issues.

hexaae · 23 Oct 2017

Trying to rename C:\Windows\bootstat.dat it says "The action can't be completed because the file is open in System".
All advanced permissions and owner are correctly set compared with another PC with Windows 10 1703 (where I can rename the file).

hexaae · 30 Oct 2017

News
A friend of mine on a fresh install of Windows 10 x64 1709 reproduced the same problem: the bootstat.dat is forever locked by System task!
This makes the restore points fail on restore-reboot.

Generic Windows 1709 bug with restore points?

jimi · 11 Dec 2017

I too have the same issue, are there any solutions?

hexaae · 11 Dec 2017

This is a MAJOR issue in Win 10 CFU, but unfortunately Microsoft is ignoring this big problem.

Please, cast your vote +1 here: Feedback Hub - Windows Insider

jimi · 12 Dec 2017

Well i solved with a workaround, booted in a WinPE i used the Sergei Strelec one ( i think a linux live distro would work too) and deleted the bootstat.dat file form windows folder and rebooted the system. I finally manually created a new restore point and tried to restore the system to the restore point previously made and it worked no errors.

Windows 10 1709 failed restore point 0xc0000043

Windows 10 1709 failed restore point bootstat.dat 0xc0000043