pakmopa.blogg.se

This isn’t as painful as it sounds, and I though I would post here just in case someone else runs into this issue. To fix this problem, I had to go in and manually add AutomationTool.exe to the list of trusted applications. For some reason, Windows was not giving me that alert. This was an issue, because I rely on these alerts to give access to applications that I know I can trust…like the AutomationTool.exe for UE. But, in the case of AutomationTool.exe, I didn’t get any alerts that Windows was blocking it from accessing files needed to be worked with during the process of packaging a game. This usually isn’t a problem, because Windows will alert you to an application attempting to access protected folders. These are some of the errors that will occur with Controlled Folder Access enabled. UATHelper: Packaging (Windows (64-bit)): LogFileManager: Error: Error flushing file: …/Saved/Config/Windows/Engine.ini (Access is denied.)īy the way, I’ve removed most of the file paths, but you get the idea. PackagingResults: Error: Error flushing file: …/Saved/Config/Windows/Engine.ini (Access is denied.) UATHelper: Packaging (Windows (64-bit)): LogAssetRegistry: Error: Failed to open file for write …/d859983c.binĪs well as file access denied errors like these: PackagingResults: Error: Failed to open file for write …/866581fd.bin

So, I knew what was causing errors like the following: I use the Windows 10 feature called Controlled Folder Access to (hopefully) safeguard my files from Ransomware (I am absolutely terrified of that happening). I have just spent the last half-hour troubleshooting a failed build.