Well ... Both PC's created restore points today and I'm out of ideas on how to stop it, other than disabling System Restore. I don't think this is a bug per say, just something they've added to CYA in updating/fixing something else and since it appears it has to do with WD ... they sure ain't gonna tell us anything about it ... Hopefully, they'll fix/undo it soon :)
FWIW ... I have noticed something else, that I haven't seen/noticed before this started. I think it's associated with the WD Cleanup Task, but don't quote me on that. In the C:\Windows\servicing\Sessions folder I've noticed that xxxx_xxxx.xml / xxxx_xxxx.back.xml files are being created with the same time stamps as the WD Task time stamps. AFAIK, this has to do with the Component Based Servicing and maybe why MS is creating these restore points now ???
Note: You'll also find reference to these session numbers (xxxx_xxxx) under the following reg key...
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending
This is a snippet of my CBS.log and I don't even pretend to understand all the stuff in it, but the following is all I see that appears to do with these restore points and the Component Based Servicing (i.e. 30684462_1698231930 which is the name as one of the xml files referenced above)
Code:
2018-08-16 02:57:28, Info CBS Exec: Processing started. Client: DISM Package Manager Provider, Session: 30684462_1698231930, Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17134.1, Identifier: Windows Foundation
2018-08-16 02:57:28, Info CBS Exec: Using execution sequence: 92
2018-08-16 02:57:28, Info CBS Reboot mark set
2018-08-16 02:57:28, Info CBS Winlogon: Registering for CreateSession notifications
2018-08-16 02:57:28, Info CBS Winlogon: Loading SysNotify DLL
2018-08-16 02:57:28, Info CBS Winlogon: Starting notify server
2018-08-16 02:57:28, Info CBS Disabling LKG boot option
2018-08-16 02:57:28, Info CBS Exec: Creating restore point: Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17134.1, current: Installed, targeted: Installed
2018-08-16 02:57:28, Info CBS Restore point type: Install
2018-08-16 02:57:28, Info CBS Perf: Begin: nested restore point - begin
2018-08-16 02:57:33, Info CBS Perf: Begin: nested restore point - complete
@Stitch194 .. I found the same in your CBS.log, just different session number.