I have experienced this issue as well. Several times. It never seemed to really have a solid fix for me aside from one approach. What Robert said is definitely something that had worked for me at times. Other times, sysprep would continue to through the same error just with a different app name until I reached the point it was throwing the error with an app name that I could not locate anywhere on the machine.
My go to fix was to recreate the image with a fresh ISO from Microsoft. Then when you get logged in enable the Built-in Administrator account immediately, log into it, delete the user you had to make during the OOBE (via Control Panel>System and Security>System>Advanced System Settings>User Profiles). Then make sure you do NOT run any Windows updates or anything of the sort. Just run sysprep right away set it to go into "Audit Mode", leave the "Generalize" button unticked. Then setup your custom image from there. (Always generalize when done, prior to capture)
From what I've found as soon as you manipulate any apps (Windows updates) you will likely break sysprep. Just get the most current ISO you can then you can run updates after you push the image if needed.