Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
I don't know if you didn't read the above comments or just failed to absorb them, but we have been over this. Uplay is on the C: drive and has been on every other drive in every conceivable way several different times with no change in progress. Literally nothing changes when uplay is on a different drive. Everything that works when it is on the C: drive also works on the E:, F:, and any other drive. I even installed it on my network drive for ♥♥♥♥♥ and giggles and the games worked perfectly fine as long as they were on the C: drive. The problem is that the GAMES seem to HAVE to be installed on the C: drive alone in order for them to work properly or at all. It has nothing to do with Uplay at all, whatsoever. And back to the 'we've been over this' part, I have already done the administrator permission stuff. It was literally the first thing I did. I gave administrator permissions to everything (Uplay included). It did not solve the problem.
Thanks for trying though.
Thanks for the answer! I'll try it ASAP
Partition Table type(GPT) -> Partition Table -> Partition -> File System(NTFS) -> ... -> UPlay.
How did they manage that this chain fails when it doesn't start with MBR but GPT. This is beyond anything I have seen.
I have tried it on other drives and while it seems to work at first, run into problems later down the road.
Steam Client and the Ubi games themseleves can be installed on any drive letter though.
Best bet is to uninstall Uplay properly and then install it to C drive.
Shouldn't have an issue doing that in order to fix the games, even while the games are already installed elsewhere; as that shouldn't matter cause each game install location is noted somewhere in the registry. So just make sure Uplay Client is installed to C and that there are not multiples of it on the system.
For example I had installed Far Cry 3 on E drive and at the time it installed Uplay, which I also put on E drive. Later on I installed Assassins Creed 4 and for some reason it went and installed Uplay on C drive and then was always running it from C; then when I'd load up Far Cry 3, my saved games were missing, cause they were in the Uplay folder on E still.
So yea just install Uplay to C and it'll work without major issues.
Do not let a game install Uplay Client; get the latest version from Ubisoft.com or Uplay.com
Again, where u installed the game too doesn't matter. It matters where the Uplay Client is installed to, which is why people end up having problems.
Maybe because, it uses the MBR Partitioning Scheme?
Ditto.
If I was bored more, I would Boot into Windows and test it myself, althugh, on another thought, I can't probably test it, because I avoid Ubi/UPlay games like the church.
My D: drive is a software RAID formatted with GPT. It must be GPT since it's 8TB in size. Of course that 8 TB is kind of useless since almost all AAA games don't work if installed there. None of the Ubi games other than Rayman and Child of Light work, None of the Saint's Row games work, Call of Duty: Ghosts doesn't work, pretty much every game that is a small indie game does work but any game that is a big AAA game doesn't work.
I have no solution but I've tested this over and over again across Windows 8.1 and Windows 10 and this isn't an issue if you have a regular drive formatted with MBR but if you are using Microsoft Storage Spaces software raid formatted with GPT then forget about installing or running your games on that volume.
I haven't had this problem for a while now. I think windows 10 fixed it.....
I'm on Windows 10 and just last night I tried to play Call of Duty: Ghosts for the first time and it failed. I also installed Assassin's Creed Unity last week and on my D: drive. The game just loads an infinite black screen loop. Oddly, reinstalling it on C makes the game work flawlessly.
Yea, I'm on a clean installation of Windows 10 Pro and nothing has changed for me. I was shocked when Call of Duty: Ghosts booted up correctly from my D:\ volume! But then I tried to play it and the audio is messed up and and the game glitches out during the first mission.
Every game I've tried since installing Windows 10 does this: Hyperdimension Neptunia, Assassin's Creed: Unity, Far Cry 4, all of them.
That hasn't stopped me trying though. My 256 GB SSD is completely full so I always install to D: and try it. Most games though, just crash with a not responding error or just load a black screen.
I have 118gb on my "C:" and only have 200mb left atm since AC:Unity is installed on that hard drive.
Every other game or game client (steam / gog / battle.net) works perfectly on my gaming "E:" drive. Haven't tried ea's origin though