Windows 10: Windows 10 1709 failed restore point bootstat.dat 0xc0000043

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) *Eek





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.

:)

 

Widnows 10 bootup stuck after update

Hi,

Have been through something similar previously by going into appwiz.cpl and uninstalling updates back to 3rd January and trying a system restore. Given that I've already covered this ground, I think it was the same process although accessed from a different
routine, I found only one restore point listed, Windows Installer on 28 January, I think it was.

After a few minutes system stopped and produced this failure notice: "System restore did not complete successfully. If the failure persists, switch off anti virus and try again, or perform system restore from Windows Recovery Environment. System Restore
failed in delayed delete op for the file \??\volume{57a5adba-18a6-11e0-a04a-806e6f6963}\windows\bootstat.dat (0xc0000043)"

The system then went into a 3.5 hour operation to recover the old operating system, I presume, as the PC was completely occupied and unusable. Then turned itself off.

Tried rebooting in Normal mode but still freezes at the final stage. Back to only useable condition, with all its constraints, is Safe Mode. In short, no progress.

Thanks for your patience. Very frustrating for everyone.

 

Win 10, no boot, no safe mode, no system restore, Status_Wait_3 error, 0x80070003 , bootrec commands successful, but still no boot, what else?

After thinking about the system restore failing on restoring the registry, I searched a bit and found this How to restore Registry from its secret backup on Windows 10 • Pureinfotech Following
those instructions allowed me to boot into safe mode! From there I ran system restore which completed, but when it reboots I get a message "We couldn't complete the features, undoing changes don't turn off your computer" . The computer then reboots to safe
mode with the error message system restore did not complete successfully, failed to restore a file...windows\bootstat.dat. Making headway, but not quite there yet.

 

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.

 

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

 

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

Have you run sfc?

 

Yes, SFC /scannow reports no integrity issues.

 

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).

 

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?

 

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

 

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

 

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.

 

AFAIK Windows recreate bootstat.dat at every next reboot storing data about last successful boot etc.
Did it recreate a new file on your system and restore point is still working?

 

Yes it did recreate a new non locked bootstat.dat, and the restore point i created after this operation works flawlessly. I did a couple of tests and no issues for now.

 

Ok, I did the same deleting C:\Windows\bootstat.dat using Macrium Reflect (WinPE) boot disk. Let's hope it won't happen again.