anyone seen this before? I've got this with a runonce script at the end of imaging on some devices and obviously the error does not make any sense whatsoever.
so far I've seen it with windows 8.1 devices only and have some other exe failing to run properly as well.
it's like win 8.1 is not a real windows NT but a re-branded win 98.
anyways, this error occurs after the script has been running good 10 seconds and only happens randomly. and no, the code has no call lines, so this error should not appear in the first place.
