Ok so the past 2 days I couldn't update Minecraft and I've been searching for a fix and came across nothing that has worked so far.. I've tried numerous things and am becoming desperate for a solution.
Things I've tried:
Deleting .Minecraft folder
Redownloading the Minecraft client
Updating/Reinstalling Java (32 bit and 64)
Disabling Firewalls (I have BitDefender if that helps)
Scanned Laptop for viruses (None found)
Waiting a day
Force update
Run Minecraft as Administrator
Tried updating through browser
Even looking for a program called "Relevant Knowledge" in task manager/uninstall programs because apparently it's quite a common issue for this
And among other things
Please I really want to play 1.4.2 I tried downloading the .jar file manually, Minecraft worked and accepted it but would still say there was an update available and rather not go through that screen every time I want to play. I've searched around these forums and Google a lot to find all these solutions but none have worked yet. Also I (ONCE) got a little different error, it was "Fatal error occured (4): s3.amazonaws.com" and a few other times I got "Fatal error occured (4): lwjgl.jar 14%" (it would always get to 14% and stop and never show anything between 0-14" so could this be s3.amazonaws.com fault and I should just wait longer? Or is there another solution I can try?
More Info: I have no mods, I do have TechnicLlauncher installed although since it uses it's own folders I don't see how it can be the problem. I also tried Advanced Minecraft error test V1.0 if you want to see the log then I can post it (just give me directions on how to copy and paste it from cmd ) OH also my skin does not load when I play at all, SMP or SSP. Also I have no texture packs.
THANK YOU! If you hadn't had told me to do this, I would have never updated my BitDefender!
I Didn't have that feature on mine since I was using BitDefender Total Security 2011 and so I searched and found a (free upgrade for existing users) to BitDefender Total Security 2013 and sure enough, Minecraft somehow worked! I'm updated, cheers! (I don't know how this fixed the problem though as I've tried turning BitDefender's firewall off before, BUT WHO CARES NOW!)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Things I've tried:
- Deleting .Minecraft folder
- Redownloading the Minecraft client
- Updating/Reinstalling Java (32 bit and 64)
- Disabling Firewalls (I have BitDefender if that helps)
- Scanned Laptop for viruses (None found)
- Waiting a day
- Force update
- Run Minecraft as Administrator
- Tried updating through browser
- Even looking for a program called "Relevant Knowledge" in task manager/uninstall programs because apparently it's quite a common issue for this
- And among other things
Please I really want to play 1.4.2 I tried downloading the .jar file manually, Minecraft worked and accepted it but would still say there was an update available and rather not go through that screen every time I want to play. I've searched around these forums and Google a lot to find all these solutions but none have worked yet. Also I (ONCE) got a little different error, it was "Fatal error occured (4): s3.amazonaws.com" and a few other times I got "Fatal error occured (4): lwjgl.jar 14%" (it would always get to 14% and stop and never show anything between 0-14" so could this be s3.amazonaws.com fault and I should just wait longer? Or is there another solution I can try?More Info: I have no mods, I do have TechnicLlauncher installed although since it uses it's own folders I don't see how it can be the problem. I also tried Advanced Minecraft error test V1.0 if you want to see the log then I can post it (just give me directions on how to copy and paste it from cmd
THANK YOU! If you hadn't had told me to do this, I would have never updated my BitDefender!
I Didn't have that feature on mine since I was using BitDefender Total Security 2011 and so I searched and found a (free upgrade for existing users) to BitDefender Total Security 2013 and sure enough, Minecraft somehow worked! I'm updated, cheers! (I don't know how this fixed the problem though as I've tried turning BitDefender's firewall off before, BUT WHO CARES NOW!)