jordyvr

I ran into the same problem, it also seems to affect the Premium version. It started when my startup batch files started to generate this error after MBAE was already installed for a few weeks. I also happen to use Bitdefender as my AV and don't think simply disabling the AV is a proper solution. My workaround is using the 64-bit cmd.exe, which doesn't seem to generate the error. If you happen to be running a 64-bit version of Windows, you can set the 64-bit version of cmd.exe as default as follows: Go to Control Panel -> System -> Advanced system settingsClick on 'Environment variables'Under the 'system variables' pane, select 'ComSpec' and edit the value to read %SystemRoot%\SysWow64\cmd.exe This fixed it for me, but of course it's only a workaround for a problem that hopefully can be fixed in another way!