Why is Blizzard dictating us where we are allowed to install our games?
As of various reasons I want to install Blizzard games onto my NAS but the Blizzard APP keeps telling me that my mapped networkdrive is an invalid installation directory. Any workaround or fix for that?
5 Likes
It’s ridiculous. I just got a NAS setup going after researching a lot about them and now I’m told that both Origin and Battle.net won’t work. Unbelievable.
3 Likes
There is no fix because Blizzard does not care. So far too few players are affected by this (I am one of them). I hate useless restrictions - especially since it is technically a minor task. Steam does it - so Blizzard could too. But as long as only few players complain, they won’t spare the resources.
2 Likes
I was just trying to set this up. Guess ill have to buy new SSD then what a shame.
I don’t think so, because I can’t seem to find the post at hand quickly, but those were basically the two points you are going to mentioned. More, they looked at pick/ban systems from other games before deciding to go the direction they chose.
Ridiculous… And an inconvenience (forum does not let me use the right word ) for trying to install (as I was trying) in a parallels windows VM. I don’t want the main disk to grow, but win sees the shared folder of my mac where I want to install games as a network map… so, I can install there Epic and Steam games… but NO BLIZZARD games (and the drive is, is fact, a local one)
Something like this would help me who is on a 5Mbps DSL line not have to leave my desktop computer (Not exactly power efficient) on for 12 hours to download D2R. Electricity isn’t free and allowing me to save their games wherever I like allows me to create workarounds to download on lower power devices and run them on higher powered devices.
It’s late 2022 and still no change
Ahhhh
(Btw for Origen there is a workaround/not nice but it works)
1 Like
Can you post the workaround please? Thank you!
For Origin games you can simply create a symbolic link from the networkshare to a folder on your drive.
First download the game to your local game folder.
After that move the game folder to your networkshare.
Then create a symbolic link in Powershell/CMD to the game folder u definded in your Origin launcher. You can just google " Symbolic Link Powershell".
My games start this way without any issues.
Perhaps this is still an attempt to force us to buy a certain product or a policy for protecting against viruses and other things.
So interestingly, Origin Games installed via Steam are a bit more cumbersome and I haven’t gotten that working but Overwatch 2 via Steam will not only install to a network drive but boot and work just fine. I guess we’ll have to wait for a Steam release of the games we play for this functionality to work again.
Games only from the Origin/EA app (at least when it was called Origin) are much easier to get working. Some games won’t work like psychonauts due to animations not loading in properly, some games like rainbow six siege require a weird elevated permission thing I’m still working out, similar to Steam/Origin. Something to do with Battle Eye. GOG requires some tweaking too, but it does work. Battle.net seems to be the only outlier.
I can’t link the help threads here, unfortunately.
- nothing changed. But workaround was always. Just create and mount virtual disk and place it vhd/vhdx file on your nas.
Or you can use iSCSI when you nas support it and you know how to use it
www windowscentral com/how-create-and-set-vhdx-or-vhd-windows-10