BUG: 38 Character Path Recognized As Over 250, Unable To Install Engine.

Summary

Attempting to install Unreal 5.5 on the path “C:\Users\Workstation\Epic Games” causes the launcher to block the install on the basis that the path is longer than 250 characters.

I already have another Unreal install on this exact same folder location (5.3) and it works just fine. So something must have gone wrong between the release of 5.3 and now.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. Attempt to install Unreal 5.5 on a path shorter than 250 characters
  2. See warning

Expected Result

The launcher lets me install the engine

Observed Result

The launcher blocks the install

Platform(s)

Windows 10

Additional Notes

I think an image upload option would be pretty great for bug reports. I had to wait until the report was created to then upload an image.

Any fixes?

I fear not.

For now just stick to other engine versions I guess.

hi,
the loader for 5.4 onward needs to be on the path
C:\Program Files\Epic Games
This is due to licensing acceptance .
the only other place is by making directory
D:\Program Files\Epic Games
the install will only work for another drive
with \Program Files\Epic Games
created manually

Also still having this issue. Can’t put it on my C: drive so kind of wild that the newer versions just can’t be installed, bumping for visibility. It does work if you change it to not the x86 version, but should be fixed regardless

Here is the trick, if I recall properly, you need to start the process and then click the “install” button faster than it can check if the path is valid. Just be very quick. If you fail, just try again and be quicker.
If you do that, it will all work perfectly.

I know, it’s ■■■■■■■ stupid. That’s just the way things are.

As additional context: I can't install engine versions above 5.3 | The default file path is "too long" except I have long file paths enabled!

The status of FORT-911405 changed to ‘Needs Triage’. We’ve confirmed the issue and it’s waiting to be assigned to someone to fix it.