# Unable to build C++ Project in Offline Unreal Engine 5.7

**URL:** <https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910>\
**Category:** Getting Started & Setup\
**Tags:** offline, unreal-engine, question\
**Created:** [January 9, 2026, 4:35pm UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910 "2026-01-09T16:35:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![PackRat2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@PackRat2](https://forums.unrealengine.com/u/PackRat2)\
**Post date:** [January 9, 2026, 4:35pm UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910/1 "2026-01-09T16:35:53Z")

</div>

I’ve created an SCCM package using the .msi for the Unreal Editor Offline version, which works great. However, attempting to create a blank C++ project with Visual Studio 2022 Community installed results with an error about unauthorized access to the whole Engine folder and sub-folders.

Error:

```auto
Unhandled exception: UnauthorizedAccessException: Access to the path 'C:\Program Files\Epic Games\5.7\Engine\Intermediate\ProjectFiles' is denied.

```

I can get around this by accessing the folder’s security properties and giving Users Modify access. A C++ project can then be created.

What is a better fix for this since this is deployed to over 60 computers? Standard users need to be able to create a project without special access.

Thank you 🙂

---

<div class="post-metadata">

**Author:** ![Gulli\_Gullile](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Gulli\_Gullile](https://forums.unrealengine.com/u/Gulli_Gullile)\
**Post date:** [January 10, 2026, 10:10am UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910/2 "2026-01-10T10:10:49Z")

</div>

On all windows versions, writing to any folder in Program Files is for users of privileg access only. You can either write a powershell script that publishes the engine and sets the rights, or you install it do a different path.

This is nothing unreal specific.

---

<div class="post-metadata">

**Author:** ![Svegn2](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/svegn2/32/924220_2.png) [@Svegn2](https://forums.unrealengine.com/u/Svegn2)\
**Post date:** [January 22, 2026, 3:28pm UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910/3 "2026-01-22T15:28:20Z")

</div>

Hello!

The installer should normally set the folder access during the installation. Please make sure that the installer runs with Administrator privilege.

Regards,

Martin

---

<div class="post-metadata">

**Author:** ![jalopy3333](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jalopy3333](https://forums.unrealengine.com/u/jalopy3333)\
**Post date:** [March 20, 2026, 11:37pm UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910/4 "2026-03-20T23:37:50Z")

</div>

“should”? Well, it doesn’t. Also, why is that only the installers job? You know this could be fixed for the cases where the installer doesn’t do it, right?

---

<div class="post-metadata">

**Author:** ![MakiPJATK](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@MakiPJATK](https://forums.unrealengine.com/u/MakiPJATK)\
**Post date:** [April 15, 2026, 2:50pm UTC](https://forums.unrealengine.com/t/unable-to-build-c-project-in-offline-unreal-engine-5-7/2690910/5 "2026-04-15T14:50:59Z")

</div>

We’ve run into this issue too. This isn’t just an Unreal-specific problem. If I install UE from the Epic Games Launcher, it configures everything correctly; the issue lies specifically with the offline installer. And no, installing it via EGL is not a solution (doing this manually on 200+ machines is simply not an option).
