New PC. Moved drive from old PC. Issues

[chajapa]

So I got a new PC. On my old one I had already moved my whole Skyrim install to B:\Games\Steam\...etc and it was working fine.

I use MO2.

When I installed the drive in the new computer, It didn't see my MO2 instances. I had to redo an instance and then all of my profiles showed up. I can play the game, but I can no longer get Creation Kit to start.

I went from Windows 10 to Windows 11 and I have a strong suspicion that a lot of stuff got left behind. 

Is there a way to fix this short of uninstalling everything and starting over?

I'm on 1.5.97

I remember it took quite a bit of standing on my head and jumping through hoops to get Creation Kit working in the first place.

If I can't get this working again, then I guess I'm done writing mods, but I'll miss it.

 

Thanks for any insights.

 

ChaJaPa

[traison]

1 hour ago, chajapa said:

moved my whole Skyrim install to B:\Games\Steam\...

 

I'm not sure if any of the old legacy from pre-NT kernels are still around but A and B drives used to be reserved for floppy drives and such. It's entirely possible the reason why Windows installs on C by default is just because its always been like that, but it could also mean that A and B still carry some special meaning. Like how you can't name a file "COM1" (and various others) because these used to be reserved in DOS.

 

1 hour ago, chajapa said:

Is there a way to fix this short of uninstalling everything and starting over?

 

I would use Process Monitor from Sysinternals (Microsoft). Pay close attention to file and registry paths being wrong or missing.

[Roggvir]

I would say A/B has nothing to do with that.

Those DOS times are long gone, now its just a letter like any other.

[Grey Cloud]

9 minutes ago, Roggvir said:

I would say A/B has nothing to do with that.

Those DOS times are long gone, now its just a letter like any other.

DOS and how Microsoft assigns drive letters are two different things. Indexing seems to be a thing with drive letters.

[traison]

7 minutes ago, Roggvir said:

I would say A/B has nothing to do with that.

Those DOS times are long gone, now its just a letter like any other.

 

Oh it most definitely has nothing to do with the issues chajapa is seeing, my point was mean for the future. For instance, I wouldn't with 100% confidence say they're not going to run into some silly issue a year down the line. A folder browser dialog not including A and B. A dropdown box. Whatever it may be.

 

It would be odd for Microsoft to keep this logic in for this long, but then again, like I said, you can't create a file named "COM1" either. How many people are still pushing files over com ports in 2025? While that sounds like something I'd be doing, I'm not one of them in this case.

[chajapa]

9 minutes ago, Roggvir said:

I would say A/B has nothing to do with that.

Those DOS times are long gone, now its just a letter like any other.

Correct. It was running fine this way under windows 10.

I have a real strange feeling that I'm going to have to reinstall everything. I get error messages about missing dll files that I can see in the directory that I'm trying to launch CK from.

[Grey Cloud]

1 hour ago, chajapa said:

I'm on 1.5.97

I remember it took quite a bit of standing on my head and jumping through hoops to get Creation Kit working in the first place.

I'm on 1.5.97 too.

I don't use the CK for anything fancy but I don't have any trouble with it working.

Do you use this:

CK Platform Extended

Absolute sanity saver.

[PippinTom]

1. Download proper version of CK if you rely on steam as download provider (I myself did by accident got LE version via Steam without realizing it).
2. Move(merge) CK to(with) Skyrim root directory, if you are getting any DLL missing issues.
3. Add or remove steamAppID override (whichever will help in your case) to/from MO2 CK launch options (for some reason Mo2 adds "1946180" there in case of "bundled/built-in" launch preset - one of those that get recreated after user deletes them ...)
4. ... since you just migrated to win11 from win10 (and you didn't specify which exactly dlls are reported as missing...) then maybe you are missing some MSVC/.NET redistributables? Bare windows does not come with those.

Edited April 22, 2025 by PippinTom
added #4

[chajapa]

yeah.

I broke it. For some reason, when I uninstalled and reinstalled CK, it deleted all of the SkyrimSE files. I still have all my mods in the MO2 directory structure, but I think I have to uninstall, reinstall, and basically start over. I tried reinstalling SkyrimSE and got the 1.6.1170 build. Downloaded the SKSE for that build and it won't even start using the SKSE loader.

If I just start SkyrimSE from MO2, it starts. But without SKSE, nothing is going to work.

I'll have to spend some time on this and see where it's going.

 

[chajapa]

Apparently it was a need for some libraries. I've downloaded them and have both Skyrim AE and Creation Kit starting. I had to install a new SexLab Framework, Papyrus Utils and a couple other things. Not sure if Schlongs of Skyrim will be working when I have time to get into it. Appeared to be a few errors when starting CK, I'll have to see if it broke my mod. Should have time to scope things out a bit better tomorrow.

 

Appreciate the input. It got me looking at the right things at least.

[chajapa]

So... lotta stuff just wan't working right so I downgraded my SE install back to 1.5.97.

Now I just have to see about getting the Creation Kit downgraded, but at least I can play the game again.

I think my biggest problem is that I don't remember what CK version I was on before, but I know I was using the CK Fixes and it was all working wonderfully.

*sigh*

 

[Grey Cloud]

26 minutes ago, chajapa said:

I think my biggest problem is that I don't remember what CK version I was on before,

I have CK v1.5.73 for SE v1.5.97.

[chajapa]

On 4/23/2025 at 7:47 AM, Grey Cloud said:

I have CK v1.5.73 for SE v1.5.97.

Thanks. Yep, that's the one I needed. I was able to get CK using download_depot commands, downgrade it, and then run a patcher on it to bring it back to 1.5.73.

 

Before I did all the downgrading of both the game and the CK, I copied the entire folder to a backup. Makes me wonder if I can create a new instance in MO2 and point it at that 1.6.1170 mess. I *think* I could still do my modding in 1.5.97 and use the resulting mods in 1.6.1170.  Time will tell. And I appreciate you confirming the CK version.