SSE Can't install Creation Kit SE, 244GB isn't enough disk space -_-

[DrxVL]

https://imgur.com/a/MaHX9

 

Please help. Bethesda's launcher is garbage. Is there a place I can download the SE creation kit without this? It won't even let me change the installation directory. The option is disabled as if the launcher knows better where I should install things. >_<

It's worth mentioning that the drive it's TRYING to install to just a folder on my local machine mapped as a network drive. It should work, but the launcher is from Bugthesda. If I could just change the location I could tell it the proper path to install to. I even tried installing the launcher using the network path it seems intent on using, but it won't let me do that either. Even though every other application on my computer can read that drive properly the Beth launcher can only read the local C: drive, which again is fine by me if it would just let me install the SE there... -_-

The reason this S drive even exists in the first place is because Skyrim needs to be installed outside of Program Files for some mods to work properly. Well, Steam won't let you create multiple libraries on the same drive so I had to trick it by mapping a network drive. The solution would seem to be completely uninstalling Skyrim SE, all my mods, and then re-installing in program files (or editing the text file in the steam directory manually that defines library directories so I can add another one on the same drive), re-installing NMM and then rebuilding my entire load order from scratch. That's madness. Please someone tell me I can install this another way because I'm not doing that.

[JonathanOstrus]

You could try editing the install path registry key at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bethesda Softworks\Skyrim Special Edition. Just change it to wherever it really is, then load the beth launcher, install CK, then change the key back.That should be sufficient.

 

Alternatively getting a bit more complicated would be:

1. Unmount your faux network mapping
2. make a virtual disk in the windows disk manager and mount it under the letter you were using
3. Create a dummy path as if the game was there
4. install CK
5. copy the files out to the real folder
6. detach the virtual disk from the disk manager
7. remap your faux network drive

[DrxVL]

 

You could try editing the install path registry key at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bethesda Softworks\Skyrim Special Edition. Just change it to wherever it really is, then load the beth launcher, install CK, then change the key back.That should be sufficient.

 

Alternatively getting a bit more complicated would be:

1. Unmount your faux network mapping
2. make a virtual disk in the windows disk manager and mount it under the letter you were using
3. Create a dummy path as if the game was there
4. install CK
5. copy the files out to the real folder
6. detach the virtual disk from the disk manager
7. remap your faux network drive

 

Excellent suggestion. I'll give that a shot when I get home. Thank you.

[JonathanOstrus]

I just looked at the screenshots you posted (I missed the link the first time). It looks like you're either running the beth launcher as admin, but mapping the path as a non admin, or vice-versa. Network mappings on windows are done in a funky user space mode. So assuming you have the UAC enabled (which you should) if you're logged in as "MasterLogin" but without default admin rights and then map as MasterLogin with admin rights, no applications will be able to see that mapping unless run with the elevated admin rights. The same is said the other way around, if you map normally it will have limited user rights where all apps not specifically run as admin will see it, but then any apps run as admin cannot. You could open a command prompt and manually map with and without admin rights and likely resolve the issue.

[DrxVL]

I just looked at the screenshots you posted (I missed the link the first time). It looks like you're either running the beth launcher as admin, but mapping the path as a non admin, or vice-versa. Network mappings on windows are done in a funky user space mode. So assuming you have the UAC enabled (which you should) if you're logged in as "MasterLogin" but without default admin rights and then map as MasterLogin with admin rights, no applications will be able to see that mapping unless run with the elevated admin rights. The same is said the other way around, if you map normally it will have limited user rights where all apps not specifically run as admin will see it, but then any apps run as admin cannot. You could open a command prompt and manually map with and without admin rights and likely resolve the issue.

Well every other application seems to read it just fine. NMM for example which isn't running as admin on my installation. Regardless the registry edit worked. Thanks for the idea. It was an obvious solution in hind-sight, but I hadn't even considered it. :D