We have several hundred units in the field with Automate on them. These computers are running Windows 10 IoT Enterprise and are utilizing the Unified Write Filter (UWF) feature of Windows 10. For the uninitiated, this feature locks drives and/or directories against changes. When the computer reboots, any changes made will revert to the state of things when the filter was applied. We have it applied to the C: drive (there is another partition unlocked for all the content and stuff that will need to be changed on a regular basis). I've created exceptions for Automate's directory in C: as well as some other locations that Automate requires so that it can update and receive and store information.
For about a year, this worked great. However, the 120.496 release broke something and will no longer function correctly with UWF. When UWF is enabled, LTSvc and LTSvcMon will start and then immediately stop again. LTSvc in particular just loops trying to start and never does. If I disable UWF, it works fine. If I reenable UWF again, it breaks again. The current 190.37 version also does this. I reported this back to Automate support but I'm hitting a wall because IoT Enterprise is not supported. However, IoT Enterprise is identical to Windows 10 Enterprise (which I'm working with them on).
Has anyone encountered this issue? UWF is a part of Windows 10 Pro, Enterprise, IoT Enterprise, and others, so it's not exclusive our OS. Any insight into what could be causing this would be quite helpful. The log files don't provide any helpful information either, it appears LTSvc is being quit before it can log anything.