I have trouble with the installation of UE5.
It might have somerhing todo with my dual boot set up. One half got a linux, the other half got Windows 10 64 bit. The Windows OS uses the C:
I tried to download the msi file and run it on my windows. But it says somerhing like “D: is faulty” before the launcher start, but then the launcher say it can not find the exe-file.
Is there anything I can do, or do I need to get a computer with only Windows?
Hey there @fredand44! Welcome to the community! So I’ve seen a couple of issues before for dual booted systems before. I believe the installer is attempting to populate it’s “choose install directory” and trying to recognize the D: drive and failing. This however should be a safe operation and not take down the entire installer. Did you previously have an installation of the launcher anywhere else? When it first installs it makes a registry entry on what drive and where, and when the installer spins up again it checks for it. Say if you changed the names of your drives or swapped them, that could have caused this.
I’ve heard of people taking the source and having to build it from their linux side to be able to use it on both, however the windows side installer should be able to install on it’s side alone anyway.
First,thanks alot for your reply.
No I have not changed the names of the drives and I have not installed it before on this or at any other PC either. I guess if I had I could have copied those registry entries and add them to this PC, right ?
As you said , the error about the D: drive do not crash everything completly. Aftetwards I found a shortcut to the installer/launcher, but when I start that it says it can not find the exe-file that is needed. I guess that exe-file do not exist because of the error about the D: drive .
Regarding linux, do you mean that I might compile it from source but I tweak the code about finding the drives so it do not look for any other drive then for eg C:?
(seems a bit complicated)
Or as last option get a suitable PC with out dual boot?
In this c
Most of the places where I’ve seen this error discussed are dual booting issues, but there are also many who haven’t so I don’t really have a definitive on if it’s because you’re dual booted Linux, or if it’s just a side-effect. If windows is the primary drive anyway it shouldn’t have an issue in my experience but that was wrong here. I’m going to check back with my team on this side to see if there’s a common workaround for these issues before I give any concrete advice. Definitely going to have to get back to you on this one!
Thanks again, in this case the primary OS is actually Linux.
Really hard to say if it would work if it was the opposite.
I haven’t received an answer on my side yet, still going to be doing some digging. I personally think I’d have a fix but I won’t have anyone digging around in their registry until I know how it will effect things! Once I find the true cause I can pinpoint a safer means but this is definitely a fun one to say the least!