Unable to run instances on external dirs

Every time I try to launch an instance, with my instances folder being on a different drive, I get this error:

```
Minecraft has crashed!
net.fabricmc.loader.impl.FormattedException: java.lang.NoClassDefFoundError: Could not initialize class com.mojang.blaze3d.systems.RenderSystem
at Not Enough Crashes deobfuscated stack trace.(1.18.2+build.3)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:463)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:568)
at org.multimc.impl.OneSixLauncher.invokeMain(OneSixLauncher.java:104)
at org.multimc.impl.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:175)
at org.multimc.impl.OneSixLauncher.launch(OneSixLauncher.java:185)
at org.multimc.EntryPoint.listen(EntryPoint.java:127)
at org.multimc.EntryPoint.main(EntryPoint.java:57)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.mojang.blaze3d.systems.RenderSystem
at net.minecraft.util.SystemDetails.addSection(SystemDetails:65)
at net.minecraft.client.MinecraftClient.addSystemDetailsToCrashReport(MinecraftClient:2394)
at net.minecraft.client.MinecraftClient.addSystemDetailsToCrashReport(MinecraftClient:2389)
at net.minecraft.client.main.Main.main(Main:206)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:461)
... 11 more
```
um... UPDATE: Apparently this is only for one of my instances, but after leaving my system alone for about 9 hours, all of the other instances, fresh or not, suddenly work now.
Regardless, the instance causing this error is my most used and most critical to have running. Is there any way I can fix this in-place without spawning a new instance and manually copying everything over?