Thought I'd share this - stuck on loading with Win 10

[Cavscout74]

I just got a new laptop after a small disaster with my old one.  Luckily, my old hard drive survived and with the help of a drive enclosure, I copied my KSP files onto the new computer.  And promptly got stuck on "Loading Asset Bundle Definitions"   There is some old advice to delete the KSPedia folder, and I tried that but it wasn't my problem.  I downloaded Steam onto my new computer, and downloaded a fresh copy of KSP.  That ran great, so I thought there was some problem with the copied versions - I keep my Steam install untouched and make copies for different mod setups.  So I copied my fresh Steam install to a new directory, reinstalled mods and got stuck on "loading asset bundle definitions."   Hmm, very strange.  So I tried loading a pure stock copy and got stuck at the same point.  After some thinking, I tried setting compatibility to always run as admin and poof, it worked.  So apparently - and I don't know if this is a Windows 10 issue or KSP 1.9.1 issue or new laptop issue - you can run fine from the Steam folder but any copied versions may need to be set to run as admin to be able to load.

Edit: After I posted, I remembered it was doing it on my 1.8.1 version as well, so it's either some setting on my new laptop or a windows 10 issue.

Edited April 15, 2020 by Cavscout74

[bewing]

Yeah, it depends on where you install KSP to. The game tries to write fairly extensively to folders inside/below its install directory. So if you leave your steam installation in your Programs(x86) folder (the default), then you get these stupid errors, because of windoze protection violations.

Best solution is to change your default SteamLibrary install dir to someplace unprotected.

 

[Cavscout74]

13 hours ago, bewing said:

Yeah, it depends on where you install KSP to. The game tries to write fairly extensively to folders inside/below its install directory. So if you leave your steam installation in your Programs(x86) folder (the default), then you get these stupid errors, because of windoze protection violations.

Best solution is to change your default SteamLibrary install dir to someplace unprotected.

 

That makes sense.  My old laptop had the HD partitioned and the alternate KSP copies were on the D:.  My new laptop didn't come already partitioned and I was more concerned with getting everything important copied over and/or downloaded than worrying about a partition.  So the KSP alternates went into C:Program Files and I didn't think about it till I realized another program I had to set to Run as Admin for it to work.   Man I miss XP.  Actually scratch that, I miss DOS.

Edited April 15, 2020 by Cavscout74