SMS EXECUTIVE starting SMS OFFLINE SERVICING MANAGER automatically

Last days there is something really strange going on with Offline Servicing in ConfigMgr. The task "SMS EXECUTIVE started SMS OFFLINE SERVICING MANAGER" is running multiple times a day normally, with "This Schedule with ID does not have a next run time" as a result. Last days however I saw at two different environments that Offline Servicing is kicking off automatically on multiple images, leaving them in an error message, not cleaning up the ConfigMgr OfflineImageServicing folder afterwards. Let's have a look at some screenshots created.

It's all starting with the following messages in the ConfigMgr console! (Failed to apply one or more updates)

Looking in OfflineServicingMgr.log you see that multiple tasks are scheduled with dates from many months ago. The schedule with ID will be run now. It's run time is at (some date in past).

In another environment you see the same behavior, where schedules are running multiple times on the same image too. When you look closely you see a task running six times on the same image.

Because of multiple errors during the process, files and folders are not removed, leaving them in a unwanted state afterwards. Where this folder has (in my case) around 73.000 files in 14.000 folders, with almost 12GB in size. (with wrong ownership too)

Some of the error messages are:
-Image UnMount failed with error 31
-Deleting file \\?\D:\ConfigMgr_OfflineImageServicing\<ID>\ImageMountDir\Program Files\Common Files\microsoft shared\DAO\dao360.dll, FAILED, Win32 Error = 5
-Failed to remove previously existing staging folder -D:\ConfigMgr_OfflineImageServicing\<ID>, GLE = 5
-Initialization of schedule processing failed
-Schedule processing failed

Hope someone can explain why this is happening on almost same time in totally different environments, where there's no schedule set on OS images? Both environments are running on ConfigMgr Current Branch, version 1606 with all hotfixes available installed. Will be continued.. (and posted at Microsoft bugs or suggestions too)

Update: Both tasks mentioned started at Sunday October 30th. One at 5:00 AM, the other at 23:00 AM (both UTC+01:00). Still nothing heard about other issues so far..