fabric "Uncaught exception in thread 'main'"

[strikeknight57]

trying to launch fabric or any other version (forge or what ever else) and I get the following error...

Uncaught exception in thread "main"
net.fabricmc.loader.impl.util.ExceptionUtil$WrappedException: java.io.IOException: error opening C:\Users\logan\AppData\Roaming.minecraft.fabric\remappedJars\minecraft-1.18.2-0.14.6\client-intermediary.jar: java.util.zip.ZipException: zip END header not found
at net.fabricmc.loader.impl.util.ExceptionUtil.wrap(ExceptionUtil.java:51)
at net.fabricmc.loader.impl.game.patch.GameTransformer.lambda$locateEntrypoints$0(GameTransformer.java:87)
at net.fabricmc.loader.impl.game.minecraft.patch.EntrypointPatch.process(EntrypointPatch.java:62)
at net.fabricmc.loader.impl.game.patch.GameTransformer.locateEntrypoints(GameTransformer.java:92)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.initialize(MinecraftGameProvider.java:339)
at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:142)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Caused by: java.io.IOException: error opening C:\Users\logan\AppData\Roaming.minecraft.fabric\remappedJars\minecraft-1.18.2-0.14.6\client-intermediary.jar: java.util.zip.ZipException: zip END header not found
at net.fabricmc.loader.impl.util.SimpleClassPath.getEntry(SimpleClassPath.java:80)
at net.fabricmc.loader.impl.game.patch.GameTransformer.lambda$locateEntrypoints$0(GameTransformer.java:78)
... 6 more
Caused by: java.util.zip.ZipException: zip END header not found
at java.base/java.util.zip.ZipFile$Source.findEND(ZipFile.java:1469)
at java.base/java.util.zip.ZipFile$Source.initCEN(ZipFile.java:1477)
at java.base/java.util.zip.ZipFile$Source.(ZipFile.java:1315)
at java.base/java.util.zip.ZipFile$Source.get(ZipFile.java:1277)
at java.base/java.util.zip.ZipFile$CleanableResource.(ZipFile.java:709)
at java.base/java.util.zip.ZipFile.(ZipFile.java:243)
at java.base/java.util.zip.ZipFile.(ZipFile.java:172)
at java.base/java.util.zip.ZipFile.(ZipFile.java:186)
at net.fabricmc.loader.impl.util.SimpleClassPath.getEntry(SimpleClassPath.java:78)
... 7 more

I have no idea what is going on here... can anyone help me out here?

I'm worried it might be something with my system (I'm running on the bleeding edge of 12th gen intel and ddr5) as I've been getting a lot of BSODs any time that I try and launch the normal version of minecraft. (code clock_Watchdog_timeout) I updated all of the drivers needed for my mother board chipset and what not else and the normal version works now. Now I just get this error above any time I try to launch fabric or forge. I'm at a loss...

I am running on the newest fabric loader 0.14.6 already (that was a suggestion I saw in a few other posts) and I've made it a point to update all of the mods that I have on my setup.

[Linguardium]

Caused by: java.io.IOException: error opening C:\Users\logan\AppData\Roaming.minecraft.fabric\remappedJars\minecraft-1.18.2-0.14.6\client-intermediary.jar: java.util.zip.ZipException: zip

This is telling you that you have a corrupt zip file in your folder. try deleting the .fabric folder from your .minecraft folder and running the game again

[strikeknight57]

K, I did that and ended up with a Hypervisor error BSOD... I'm starting to wonder if my OS is corrupted... the only problem there is this is only happening when I try to run anything minecraft related... I haven't had this issue with anything else...

[Linguardium]

definitely sounds like hard drive or ram is starting to go. If you know how and your computer has builtin diagnostic testing when you boot to bios, might be worth running them. A bad hard drive can cause issues with saving/loading jar files, but bad ram can too. bad ram can cause random BSOD for sure.

[strikeknight57]

trouble there is it is all brand new stuff... I guess I will have to go through New Egg's RMA system... that's gonna suck... I actually Build PCs for a living... and at this point I'm pretty sure it's the ram. Less likely it's the ssd... Had to go bleeding edge with my showpiece build lol... guess that's DDR5 for you...

[jan-Sanku]

Hi, I'm having a very similar issue. I've tried sfc, MdSched, chkdsk, and updating GPU drivers, but nothing helps. I'm not getting a BSOD though, just an instant reboot (Kernel-Power event ID 41).
Does anyone have any suggestions what kind of test to run or drivers to update? I'm at my wit's end...
It was all literally working fine yesterday, and I've done nothing but watch YT and play MC in the meantime (yes yes I know)

[jan-Sanku]

Using a different user account still crashes. Using a VM doesn't, not surprising but worth a shot I guess. Like I said, I'll check hardware to the best of my knowledge tomorrow, any help on the BIOS thing would be appreciated in the meantime.

[warjort]

any help on the BIOS thing would be appreciated in the meantime.

Typically:
You will need to search for whoever manufactures your bios.
They will let you download a file that you can copy/unzip onto a usb stick.
Then during boot, you press a key to enter bios setup and install the new bios.

Make sure the bios is actually an update/later version.
And make sure you have a backup of the old bios in case the update fails or causes problems.

Again asking your PC supplier is probably the best way to go.

[warjort]

Using a different user account still crashes. Using a VM doesn't

That's weird because presumably both are just using different parts of the same disk?

Maybe your downgrade to Windows 10 left some rubbish lying around (registry setting, wrong driver, etc.) that is the cause the problem?
Something that is not present for a fresh OS install in a VM.

[jan-Sanku]

Again asking your PC supplier is probably the best way to go.

I'll try that.

That's weird because presumably both are just using different parts of the same disk?

Yes, and everything else disk related is working just fine.

Maybe your downgrade to Windows 10 left some rubbish lying around (registry setting, wrong driver, etc.) that is the cause the problem?

No I wiped the entire thing because I wanted to get rid of the preinstalled bloatware. Reformatted the C: drive and then did a fully clean Win10 install. It's been working flawlessly for months now, installing and running big games without issue. The only weird thing that happened was MC crashing with shaders active, which at 1 point also prompted a windows error about some DLL being broken which was detected and successfully fixed by sfc /scannow so that seems unrelated. That was before I upgraded to 1.19, meaning that Fabric has been able to build its jars after that short incident.

[jan-Sanku]

Now I don't know if there were any underlying issues that will cause more trouble down the road, but it seems that Riot Vanguard is the reason for the crashes. How? Not the slightest clue, but deactivating it mysteriously allowed me to run Fabric without issue, and doing a clean reinstall of Valorant seems to be a permanent fix so far. It kinda makes sense since Vanguard has kernel level access, but I don't know why it crashed when Fabric tried to install itself. Regardless, thank you all for your help!