Windows 10: Windows 10 Restore Point creation error 0x800423F4

Hello everybody,I found a question with this title dated 2015, and I just had the problem.SFC /scannow, and the unactivation of the firewal and the antivirus, gave nothing.I started in failless mode, observed that the SystemPropertiesProtection dialog box has no system protection tab in failless mode.After a normal restart and activation of the security software, this time the restoration point was created. I restored to that point, nothing was modified it is right that it could have been a good idea from me to modify for instance my desktop background, to observe a modification, but no erro

:)

 

Windows 10 Restore Point creation error 0x800423F4 and possible workarounds

I encountered this problem as well with error 0x800423F4 on June 18, 2016. System is Windows 10: 10586.420. Numerous tries with same reported error. Shut down. Restart. Tried again. Failure. Having read all the comments here, I did the SFC (Command
prompt (ADMIN) SFC /scannow but received no integrity violations. Hmmm? What to do!

I opened the dialog box for creating a Restore Point (All Settings -> (find a setting) tying in Restore Point. Opening the configuration selection tab I deleted all my cherished restore points (gulp!). Shut down. Restart. SFC again. Shut down. Restart.
I returned to the dialog box for creating a Restore Point and tried again. The Restore Point was successfully created. Later, I created another Restore Point attempt - and this was successfully created again.

Not sure why the error happened folks: indexing, log-glitch, program error et cetera. The error just abruptly appeared this morning. This protocol attempt worked for me. I offer my comments in hopes that it helps others.

 

Windows 10 Restore Point creation error 0x800423F4 and possible workarounds

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

• Close the command prompt and restart the PC and check if it works.

Please post back with the information asked and the results, we will be glad to assist you further.

Thanks to all who contributed to this post.

I encountered this problem after installing the Windows 10 Creators Update.

After deleting all previous restore points on my system and making sure the VSS service was enabled, I followed the above recommendations and successfully created a restore point.

None of the scans indicated the presence of a problem so I suggest that you NOT give up if your sfc and dism scans come back clean.

 

Windows 10 Restore Point creation error 0x800423F4 and possible workarounds

Does anyone have a definitive answer regarding the cause of this error? I contacted Microsoft Support and they don’t.

Recently I used Windows 10 Backup to back up my files and also to create a bootable disc and a complete system image. I configured Backup to use an external drive for the backups.



Today I tried to manually create a Restore Point. After working a short time the system gave error 0x800423F4, indicating the restore point could not be created because of a non-transient error that was likely to reoccur, but I should try again. It
failed three times.



In the forums, in the past, this error was associated with Windows Server, Vista, Windows 7 and Windows 8. The error was related to various parts of Backup/Restore/Recovery and to driver problems. In some error reports the error was related the being
on-line, to using an external drive, and to using antivirus software, all of which might be causing the error in my particular situation. I got off line and still got the error. I reattached my external backup drive and still got the error. I disabled my
anti-virus software, and successfully created a restore point! So I re-enabled my antivirus software and still successfully created a restore point, and detached my external drive and successfully created a restore point, and got back on line and successfully
created a restore point. I was back to where I started. Despite getting around the error, I had been completely unable to identify the cause.



It may be just a timing problem. Someone suggested the Volume Shadow Copy function can't keep up if the system is busy. My event log shows "The server {server ID} did not register with DCOM within the required timeout", which seems to support that
assumption. It sure would be nice if Microsoft fixed this.