Yip, hardened config. Not there by default.Yes, it's a safe process.
But it's vulnerable. That's why it's included in AppGuard (I think the hardened one).
Yeah saw your setup in the other forum... probably going back to protected with hardened.xml and see how it goes.Try it. I'd be interested if you can determine from Activity Report what was needing to use bytecodegenerator.exe ...
TBH I always run in Protected mode as I have a layered setup, and am a low risk user.
Bytecodegenerator.exe is a part of Microsoft's AppX deployment. Since Windows 8 it has been associated with the Windows Store and Windows Apps.10/03/17 12:09:58 Prevented process <bytecodegenerator.exe | c:\windows\system32\svchost.exe> from launching from <c:\windows\system32>.
High probability that it is associated with a task. One associated with Windows Apps.TBH I never found out what was calling it.
As long as you use the hardened XML, processes are going to be blocked. Changing the mode from Locked Down to Protected Mode will enable the TPL and valid signed files to execute in User Space.Oh your right its included in the Hardened.xml... Was thinking of keeping it still set to yes "Yes" then just using Appguard in "Protected". What you guys think?!
It isn't going to give any more infos than what @Duotone posted here. A cmd-line logger will provide the run sequence.I'd be interested if you can determine from Activity Report what was needing to use bytecodegenerator.exe ...
It has to go through support.